Kernel crash via incorrect receive-buffer cleanup
Published Oct 23, 2026 · Updated Oct 23, 2026
Invalid buffer cleanup in the Linux DPAA2 switch driver allows attackers to crash the kernel during receive-error handling. The dpaa2_switch_rx() error path calls dpaa2_switch_free_fd(), a transmit-only helper that interprets receive-buffer annotations as an skb pointer and attempts to free it. Exposure requires the affected driver and DPAA2 switch hardware to encounter a receive-processing error; the public patch does not establish a reliable attacker-controlled trigger or demonstrate code execution.
Summary
What happened
Invalid buffer cleanup in the Linux DPAA2 switch driver allows attackers to crash the kernel during receive-error handling. The dpaa2_switch_rx() error path calls dpaa2_switch_free_fd(), a transmit-only helper that interprets receive-buffer annotations as an skb pointer and attempts to free it. Exposure requires the affected driver and DPAA2 switch hardware to encounter a receive-processing error; the public patch does not establish a reliable attacker-controlled trigger or demonstrate code execution.
The record
- CVE
- CVE-2026-98911
- Published
- Oct 23, 2026
- Updated
- Oct 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 23, 2026CVE publishedPublication date reported by the CVE source.
- Oct 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <5.15.222
- Affected versionversion=0 <6.1.189
- Affected versionversion=0 <6.12.111
- Affected versionversion=0 <6.18.53
- Affected versionversion=0 <6.6.158
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <259ad6093204b999d41e7e6d0ad90ef9a71a44ab
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <74c1c9f5c0c30bbd0c2cf87b6e3507e7ea46c13d
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <791068c962469af0090e1a1ee63657fb9eef40db
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ee54f8d7e642c44cfcc2dcb390b4c50e145d81b8
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f4ceb8e3d6d5becb4cda7a7098a8638e18c835a1
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <fa232b4496cb59503ae5108c756cbe10e59b0bc3
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us