CVE-2026-80707: can: j1939: transport: j1939_session_fresh_new(): initialize receive buffer
Published Aug 28, 2026
·Updated
can: j1939: transport: j1939sessionfreshnew(): initialize receive buffer
Affected Software
2 affected componentsFixes available
Linux Kernel
Microsoft azl3 kernel 6.6.150.1-1<6.6.152.1-1
6.6.152.1-1
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 6.6.152.1-1
Event History
Aug 28, 2026
CVE Published
via MITRE·06:53 AM
Data Sourced
via MITRE·06:53 AM
DescriptionSeverity
Data Sourced
via NVD·08:16 AM
DescriptionSeverity
Aug 29, 2026
Data Sourced
via Microsoft·08:04 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·08:04 AM
Affected Software
Updated
via Microsoft·08:04 AM
DescriptionSeverity
Frequently Asked Questions
1
Should the receive-buffer initialization cause a noticeable performance impact?
A performance impact is possible when maximum-sized ETP buffers are allocated. Most real-world use cases are not expected to be noticeably affected, because the maximum known buffer size is typically around 65 KB.
2
How can I identify the upstream fixes for this issue?
The provided references identify three stable kernel commits: 348818277a3646d5b9fa60c9d20c00dc4bc86832, f3e120a34b336079479fa10f706f0636eaa6e751, and bbfa49d1e287de44994955b44d19281be3195b44.