CVE-2026-98416
Last modified
CVE-2026-98416 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: dmaengine: ti: k3-udma-glue: fix NULL dereference in k3_udma_glue_release_rx_chn() If devm_kcalloc() for rx_chn->flows fails in a channel request function, the error path calls k3_udma_glue_release_rx_chn(), which dereferences the NULL rx_chn->flows pointer in k3_udma_glue_release_rx_flow(). Skip the flow release loop in k3_udma_glue_release_rx_chn() when rx_chn->flows is not allocated. Found by Linux Verification Center (linuxtesting.org) with SVACE..
Description
In the Linux kernel, the following vulnerability has been resolved: dmaengine: ti: k3-udma-glue: fix NULL dereference in k3_udma_glue_release_rx_chn() If devm_kcalloc() for rx_chn->flows fails in a channel request function, the error path calls k3_udma_glue_release_rx_chn(), which dereferences the NULL rx_chn->flows pointer in k3_udma_glue_release_rx_flow(). Skip the flow release loop in k3_udma_glue_release_rx_chn() when rx_chn->flows is not allocated. Found by Linux Verification Center (linuxtesting.org) with SVACE.
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= d702419134133db1eab2067dc6ea5723467fd917, < b51ed7885ab0e8ecad765adc13b465cb1498cdc9; >= d702419134133db1eab2067dc6ea5723467fd917, < b2985956e06632939bee47cee13bccd78ad7c3a1; >= d702419134133db1eab2067dc6ea5723467fd917, < 967612574c542dec71f820a6eb16dea80dd187a1; >= d702419134133db1eab2067dc6ea5723467fd917, < 89f5414660724bb562db4ac74665da16d4a57d99; >= d702419134133db1eab2067dc6ea5723467fd917, < 5a6cb4d387eebf7d32a6ed3fcd39f94bf38bd134; >= d702419134133db1eab2067dc6ea5723467fd917, < b14e6c52872556de2d6c137531e0ce85085c10ed; >= d702419134133db1eab2067dc6ea5723467fd917, < 5b2d92b7b177226e1dca2e80dc8369131276c2a4; >= d702419134133db1eab2067dc6ea5723467fd917, < 0294b6dd515256c03ea2dbf508ddd3826d788579 |
| Linux | Linux | 5.6 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-98416?
How severe is CVE-2026-98416?
How do I fix CVE-2026-98416?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-98410In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98411In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98412In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98413In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98414In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98415In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98417In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98418In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98419In the Linux kernel, the following vulnerability has been re…
- CVE-2026-9842The Backstage - Customizer Demo Access plugin for WordPress …7.5
- CVE-2026-98420In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98421In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-98416?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST