CVE-2026-52997
Last modified
CVE-2026-52997 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: net/sched: sch_dualpi2: drain both C-queue and L-queue in dualpi2_change() Fix dualpi2_change() to correctly enforce updated limit and memlimit values after a configuration change of the dualpi2 qdisc. Before this patch, dualpi2_change() always attempted to dequeue packets via the root qdisc (C-queue) when reducing backlog or memory usage, and unconditionally assumed that a valid skb will be returned. When traffic classification results in packets being queued in the L-queue while the C-queue is empty, this leads to a NULL skb dereference during limit or memlimit enforcement. This is fixed by first dequeuing from the C-queue path if it is non-empty. EPSS estimates a 0.17% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: net/sched: sch_dualpi2: drain both C-queue and L-queue in dualpi2_change() Fix dualpi2_change() to correctly enforce updated limit and memlimit values after a configuration change of the dualpi2 qdisc. Before this patch, dualpi2_change() always attempted to dequeue packets via the root qdisc (C-queue) when reducing backlog or memory usage, and unconditionally assumed that a valid skb will be returned. When traffic classification results in packets being queued in the L-queue while the C-queue is empty, this leads to a NULL skb dereference during limit or memlimit enforcement. This is fixed by first dequeuing from the C-queue path if it is non-empty. Once the C-queue is empty, packets are dequeued directly from the L-queue. Return values from qdisc_dequeue_internal() are checked for both queues. When dequeuing from the L-queue, the parent qdisc qlen and backlog counters are updated explicitly to keep overall qdisc statistics consistent.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 6.17, < 6.18.33 |
| Linux | Linux Kernel | >= 6.19, < 7.0.10 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-52997?
How severe is CVE-2026-52997?
How do I fix CVE-2026-52997?
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-52991In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-52992In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-52993In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-52994In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-52995In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-52996In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-52998In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-52999In the Linux kernel, the following vulnerability has been re…9.1
- CVE-2026-5300Unauthenticated functionality in CoolerControl/coolercontro…9.1
- CVE-2026-53000In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53001In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53002In the Linux kernel, the following vulnerability has been re…9.8
Are you affected by CVE-2026-52997?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
