CVE-2026-52997

net/sched: sch_dualpi2: drain both C-queue and L-queue in dualpi2_change()

State
Published
Severity
Not scored
Published
Jun 24, 2026
Updated
Jun 24, 2026
Reserved
Jun 9, 2026

Read the record on cve.org

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.

Scores

The record has no CVSS score.

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • 320d031ad6e4d67e8e1ab08ac71efda02bc85683 to before 86cf2eba2056bcf9c41fba260e599bd95bf9943bAffected
  • 320d031ad6e4d67e8e1ab08ac71efda02bc85683 to before 3042add80c2c50bd127d570b83319af612efde65Affected
  • 320d031ad6e4d67e8e1ab08ac71efda02bc85683 to before 478ed6b7d2577439c610f91fa8759a4c878a4264Affected
LinuxLinux
  • 6.17Affected
  • before 6.17Not affected
  • 6.18.33 through 6.18.*Not affected
  • 7.0.10 through 7.0.*Not affected
  • 7.1 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.