CVE-2026-45845
NULL Pointer Dereference in Linux Kernel TAPRIO Qdisc
Publication date: 2026-05-27
Last updated on: 2026-05-27
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | * |
| linux | kernel | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the Linux kernel's TAPRIO child qdisc implementation. When a TAPRIO child qdisc is deleted, a function stores a NULL pointer into an array without proper handling. Later, when the system tries to dump class information, it dereferences this NULL pointer, causing a kernel NULL pointer dereference.
The issue can be triggered by an unprivileged local user in a network namespace with certain capabilities enabled, leading to a kernel panic. The root cause is that the code does not substitute a safe placeholder for the NULL pointer, which leads to unsafe dereferencing during control-plane dump operations.
How can this vulnerability impact me? :
This vulnerability can cause a kernel panic, effectively crashing the system. An unprivileged local user can exploit this to cause a denial of service by triggering the NULL pointer dereference in the kernel's networking subsystem.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability involves a NULL pointer dereference in the Linux kernel's taprio qdisc when handling RTM_GETTCLASS dump operations after deleting a TAPRIO child qdisc.
Detection can involve monitoring for kernel panics or oops messages related to taprio_dump_class or NULL pointer dereferences in the kernel logs.
Specifically, checking kernel logs (e.g., using dmesg or journalctl) for messages like "taprio_dump_class" or "null-ptr-deref" around the time of network qdisc operations may indicate exploitation attempts.
Commands to help detect this include:
- dmesg | grep -i 'taprio_dump_class'
- journalctl -k | grep -i 'null-ptr-deref'
- tc qdisc show
- Monitoring for unexpected kernel panics or crashes after network namespace or qdisc manipulations.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability is fixed by substituting &noop_qdisc when new is NULL in taprio_graft(), preventing NULL pointer dereferences.
Immediate mitigation steps include:
- Update the Linux kernel to a version that includes the fix for this vulnerability.
- If updating immediately is not possible, restrict unprivileged users from creating network namespaces or manipulating taprio qdiscs by limiting CAP_NET_ADMIN capabilities.
- Disable or avoid using the CONFIG_NET_SCH_TAPRIO feature if it is not required.
- Monitor kernel logs for signs of exploitation attempts and kernel panics related to taprio qdisc operations.