CVE-2026-23449
Double-Free Vulnerability in Linux Kernel TEQL Network Scheduler
Publication date: 2026-04-03
Last updated on: 2026-04-27
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 7.0.0-rc3-00149-ge5b31d988a41 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability may cause kernel crashes with messages indicating a double-free error in skb_release_data, often visible in kernel logs.
To detect this issue, monitor your system's kernel logs for error messages similar to:
- "BUG: KASAN: double-free in skb_release_data (net/core/skbuff.c:1139)"
- Look for call traces involving teql_destroy, qdisc_reset, and related functions in the net/sched subsystem.
You can use commands like 'dmesg' or 'journalctl -k' to review kernel logs for these errors.
Can you explain this vulnerability to me?
This vulnerability is a double-free bug in the Linux kernel's TEQL (True Link Equalizer) network scheduler. It occurs when a TEQL device has a lockless Qdisc as its root, and the function qdisc_reset is not called using the seq_lock to prevent race conditions with the datapath. This improper handling can lead to a double-free error, which means the same memory is freed twice, causing kernel crashes.
How can this vulnerability impact me? :
The impact of this vulnerability includes potential crashes of the Linux kernel due to double-free errors. Such crashes can lead to denial of service (DoS) conditions, where the affected system becomes unstable or unresponsive. This can disrupt normal operations and potentially cause data loss or require system reboots.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability is fixed by ensuring that qdisc_reset is called using the seq_lock when a TEQL device has a lockless Qdisc as root.
Immediate mitigation steps include updating your Linux kernel to a version that contains the fix for this issue.
Until an update is applied, avoid using TEQL devices with lockless Qdiscs as root to prevent triggering the double-free condition.