Описание
In the Linux kernel, the following vulnerability has been resolved:
can: j1939: transport: j1939_session_fresh_new(): initialize receive buffer
Zero the allocated buffer in j1939_session_fresh_new() to ensure it
contains no residual data.
While there is a potential performance impact if users allocate maximum
sized ETP buffers, most real-world use cases are not noticeably affected
since the maximum known buffer size is typically around 65K.
[mkl: add Message-ID]
A flaw was found in the Linux kernel's J1939 CAN bus transport module. When a new session's receive buffer is allocated, it is not properly initialized, which can leave residual data from previous memory usage. A local attacker could potentially exploit this to read sensitive information from the kernel's memory.
Отчет
A Moderate information disclosure flaw was found in the Linux kernel's J1939 CAN bus transport module (net/can/j1939/transport.c), affecting the kernel and kernel-rt packages in Red Hat Enterprise Linux 9 and 10 and the kernel packages in Red Hat In-Vehicle OS 2. The receive buffer allocated in j1939_session_fresh_new() is not zero-initialized, so residual data from previous kernel memory use can remain in the session's socket buffer. A local attacker with access to the J1939 receive path could potentially exploit this to read sensitive information from the kernel's memory. Red Hat Enterprise Linux 6, 7, and 8 are not affected because the vulnerable code is not present in those releases. For the affected products, the fix has been deferred to a future update; because this is a moderate-severity information disclosure with limited practical exposure, the residual risk is limited to possible disclosure of residual kernel heap contents through the J1939 transport receive path, with no evidence of impact on integrity, availability, or privilege escalation. The upstream CVE record assigns a higher severity (CVSS 3.1 score 7.5, network attack vector) than Red Hat's rating of Moderate (CVSS 3.1 score 5.5, local attack vector) because exploitation requires local access to the system's CAN/J1939 interface rather than remote network access.
Меры по смягчению последствий
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Затронутые пакеты
| Платформа | Пакет | Состояние | Рекомендация | Релиз |
|---|---|---|---|---|
| Red Hat Enterprise Linux 10 | kernel | Fix deferred | ||
| Red Hat Enterprise Linux 6 | kernel | Not affected | ||
| Red Hat Enterprise Linux 7 | kernel | Not affected | ||
| Red Hat Enterprise Linux 7 | kernel-rt | Not affected | ||
| Red Hat Enterprise Linux 8 | kernel | Not affected | ||
| Red Hat Enterprise Linux 8 | kernel-rt | Not affected | ||
| Red Hat Enterprise Linux 9 | kernel | Fix deferred | ||
| Red Hat Enterprise Linux 9 | kernel-rt | Fix deferred |
Показывать по
Дополнительная информация
Статус:
EPSS
5.5 Medium
CVSS3
Связанные уязвимости
In the Linux kernel, the following vulnerability has been resolved: can: j1939: transport: j1939_session_fresh_new(): initialize receive buffer Zero the allocated buffer in j1939_session_fresh_new() to ensure it contains no residual data. While there is a potential performance impact if users allocate maximum sized ETP buffers, most real-world use cases are not noticeably affected since the maximum known buffer size is typically around 65K. [mkl: add Message-ID]
In the Linux kernel, the following vulnerability has been resolved: can: j1939: transport: j1939_session_fresh_new(): initialize receive buffer Zero the allocated buffer in j1939_session_fresh_new() to ensure it contains no residual data. While there is a potential performance impact if users allocate maximum sized ETP buffers, most real-world use cases are not noticeably affected since the maximum known buffer size is typically around 65K. [mkl: add Message-ID]
can: j1939: transport: j1939_session_fresh_new(): initialize receive buffer
In the Linux kernel, the following vulnerability has been resolved: c ...
In the Linux kernel, the following vulnerability has been resolved: can: j1939: transport: j1939_session_fresh_new(): initialize receive buffer Zero the allocated buffer in j1939_session_fresh_new() to ensure it contains no residual data. While there is a potential performance impact if users allocate maximum sized ETP buffers, most real-world use cases are not noticeably affected since the maximum known buffer size is typically around 65K. [mkl: add Message-ID]
EPSS
5.5 Medium
CVSS3