CVE-2026-80707
High · 7.5CVSS
7.5
EPSS
0.3%
Published
Aug 28, 2026
CISA due date
—
Cloudanix analysis
A Linux kernel bug in vehicle-style network handling could let attackers read leftover internal system data sent over the network.
- Exploitation
- Remote Unauthenticated
- Attacker needs
- None
- Complexity
- Low
- Impact
- Data Exposure
- Component
- OS kernel
- Class
- Information Disclosure
- Remediation
- Upgrade
- Effort
- Medium
- Patch risk
- Low
What it actually does
Failure to zero an allocated receive buffer in j1939_session_fresh_new() leaves residual kernel memory contents that can be transmitted over the J1939 protocol, resulting in disclosure of arbitrary kernel data to network peers.
Why it matters to the business
Organizations running affected Linux kernels in automotive, industrial, or embedded CAN networks face risk of sensitive kernel memory exposure, potentially aiding further attacks, though low exploit prevalence and no known campaigns limit immediate operational disruption.
How an attack unfolds
An attacker connected to the same J1939 bus sends protocol messages that trigger allocation of a fresh ETP session buffer; because the buffer is not cleared, previously used kernel memory is returned in subsequent frames, leaking data to the attacker.
How to fix it
Apply the upstream kernel patch that adds explicit zeroing of the buffer in j1939_session_fresh_new(); rebuild and deploy the fixed kernel to all affected systems. No configuration workaround exists.
How to confirm the fix worked
Verify the presence of the zero-initialization change in the j1939 transport source file or confirm the running kernel contains the commit referenced in the fix description.
Typical attack path
- Gain access to the CAN/J1939 network segment
- Craft and transmit J1939 transport protocol messages that cause j1939_session_fresh_new() allocation
- Receive frames containing uninitialized buffer contents
- Parse leaked kernel memory for credentials, addresses, or other sensitive values
How to detect it
Inspect kernel logs for unusual J1939 session creation patterns and review network captures for oversized or unexpected ETP data frames originating from the kernel; no public exploit artifacts are known.
What your security team should do
- Prioritize patching Linux kernels that expose J1939 sockets on any network-facing or multi-tenant systems
- Monitor upstream stable kernel releases for the merged fix and schedule rapid deployment
- Review CAN bus exposure and apply network segmentation where J1939 is used
The record
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]
Affected packages
| Ecosystem | Package | Introduced | Fixed |
|---|