Kernel crash via unchecked receive-flow cleanup
Published Oct 14, 2026 · Updated Oct 14, 2026
NULL dereference in Linux's TI K3 UDMA glue allows attackers to crash the kernel when receive-channel allocation fails. k3_udma_glue_release_rx_chn() runs its flow-release loop after devm_kcalloc() fails, and k3_udma_glue_release_rx_flow() dereferences the unallocated rx_chn->flows array. Reachability requires the affected driver and a failed receive-flow allocation; attacker control over that failure and required privileges are not documented.
Summary
What happened
NULL dereference in Linux's TI K3 UDMA glue allows attackers to crash the kernel when receive-channel allocation fails. k3_udma_glue_release_rx_chn() runs its flow-release loop after devm_kcalloc() fails, and k3_udma_glue_release_rx_flow() dereferences the unallocated rx_chn->flows array. Reachability requires the affected driver and a failed receive-flow allocation; attacker control over that failure and required privileges are not documented.
The record
- CVE
- CVE-2026-98416
- Published
- Oct 14, 2026
- Updated
- Oct 14, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 14, 2026CVE publishedPublication date reported by the CVE source.
- Oct 14, 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=5.6
- Affected versionversion=d702419134133db1eab2067dc6ea5723467fd917 <0294b6dd515256c03ea2dbf508ddd3826d788579
- Affected versionversion=d702419134133db1eab2067dc6ea5723467fd917 <5a6cb4d387eebf7d32a6ed3fcd39f94bf38bd134
- Affected versionversion=d702419134133db1eab2067dc6ea5723467fd917 <5b2d92b7b177226e1dca2e80dc8369131276c2a4
- Affected versionversion=d702419134133db1eab2067dc6ea5723467fd917 <89f5414660724bb562db4ac74665da16d4a57d99
- Affected versionversion=d702419134133db1eab2067dc6ea5723467fd917 <967612574c542dec71f820a6eb16dea80dd187a1
- Affected versionversion=d702419134133db1eab2067dc6ea5723467fd917 <b14e6c52872556de2d6c137531e0ce85085c10ed
- Affected versionversion=d702419134133db1eab2067dc6ea5723467fd917 <b2985956e06632939bee47cee13bccd78ad7c3a1
- Affected versionversion=d702419134133db1eab2067dc6ea5723467fd917 <b51ed7885ab0e8ecad765adc13b465cb1498cdc9
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.
Get started