LiveActive security incident?Get immediate response
CVE Record

CVE-2025-38350: net/sched: Always pass notifications when child class becomes empty

In the Linux kernel, the following vulnerability has been resolved: net/sched: Always pass notifications when child class becomes empty Certain classful qdiscs may invoke their classes' dequeue handler on an enqueue operation. This may unexpectedly empty the child qdisc and thus make an in-flight class passive via qlen_notify(). Most qdiscs do not expect such behaviour at this point in time and may re-activate the class eventually anyways which will lead to a use-after-free. The referenced fix commit attempted to fix this behavior for the HFSC case by moving the backlog accounting around, though this turned out to be incomplete since the parent's parent may run into the issue too. The following reproducer demonstrates this use-after-free: tc qdisc add dev lo root handle 1: drr tc filter add dev lo parent 1: basic classid 1:1 tc class add dev lo parent 1: classid 1:1 drr tc qdisc add dev lo parent 1:1 handle 2: hfsc def 1 tc class add dev lo parent 2: classid 2:1 hfsc rt m1 8 d 1 m2 0 tc qdisc add dev lo parent 2:1 handle 3: netem tc qdisc add dev lo parent 3:1 handle 4: blackhole echo 1 | socat -u STDIN UDP4-DATAGRAM:127.0.0.1:8888 tc class delete dev lo classid 1:1 echo 1 | socat -u STDIN UDP4-DATAGRAM:127.0.0.1:8888 Since backlog accounting issues leading to a use-after-frees on stale class pointers is a recurring pattern at this point, this patch takes a different approach. Instead of trying to fix the accounting, the patch ensures that qdisc_tree_reduce_backlog always calls qlen_notify when the child qdisc is empty. This solves the problem because deletion of qdiscs always involves a call to qdisc_reset() and / or qdisc_purge_queue() which ultimately resets its qlen to 0 thus causing the following qdisc_tree_reduce_backlog() to report to the parent. Note that this may call qlen_notify on passive classes multiple times. This is not a problem after the recent patch series that made all the classful qdiscs qlen_notify() handlers idempotent.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-38350 is a Linux kernel memory-safety flaw. Under specific traffic-control queue configurations, the kernel may continue using memory after it is freed. The CVSS assessment models high confidentiality, integrity, and availability impact, including a possible system crash. Exploitation requires local access; practical exposure depends on permission to configure relevant queues.

Executive priority

Patch promptly, prioritizing shared or multi-user Linux systems and environments delegating traffic-control configuration. Escalate if untrusted local users can manipulate qdiscs. The high CVSS impact supports urgency, but the local attack vector and absence of supplied active-exploitation evidence do not support an emergency internet-wide response.

Technical view

Certain classful qdiscs may dequeue during enqueue, unexpectedly emptying a child queue and making an in-flight class passive through qlen_notify(). Later reactivation can leave stale class pointers, causing a use-after-free. The fix makes qdisc_tree_reduce_backlog() notify the parent whenever the child is empty; repeated notifications are safe because affected handlers are idempotent.

Likely exposure

Linux systems running vulnerable kernel builds are candidates. Triggering involves classful traffic-control queuing and local access. The sources do not establish whether ordinary users can reach the required functionality by default. Supplied version data lacks sufficient per-entry status detail for reliable affected and fixed release boundaries.

Exploitation context

The CVSS vector is local, low-complexity, low-privilege, and requires no user interaction. The bundle includes a reproducer, demonstrating triggerability rather than malicious exploitation. This CVE is not listed in KEV, and no supplied source reports active exploitation.

Researcher notes

The CVE record provides a concrete reproducer and upstream stable fixes, supporting the use-after-free diagnosis. It does not establish code execution, attacks in the wild, or ordinary-user reachability. Per-version status details were flattened in the supplied bundle, so exact affected ranges cannot be determined confidently from this evidence alone.

Mitigation direction

  • Apply distribution kernel updates incorporating an applicable referenced stable fix.
  • Reboot into the updated kernel and confirm the running build changed.
  • Until patched, restrict untrusted local access and authority to configure traffic-control qdiscs.
  • Use vendor advisories to resolve fixed releases and backports for each maintained kernel line.

Validation and detection

  • Inventory deployed kernel versions, builds, and distribution backport status.
  • Determine whether local users or services can configure relevant classful qdiscs.
  • Confirm the running kernel contains the applicable referenced fix or vendor backport.
  • After updating, run approved regression tests for normal traffic-control behavior in staging.
Prepared
Confidence
medium
Sources
10

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-38350 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
3ADP providers
13Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2025-38350Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
siemens-SADPADP container
CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux1034e3310752e8675e313f7271b348914008719a, f9f593e34d2fb67644372c8f7b033bdc622ad228, 89c301e929a0db14ebd94b4d97764ce1d6981653, f1dde3eb17dc1b8bd07aed00004b1e05fc87a3d4, 93c276942e75de0e5bc91576300d292e968f5a02, 49b21795b8e5654a7df3d910a12e1060da4c04cf, 3f981138109f63232a5fb7165938d4c945cc1b9d, 3f981138109f63232a5fb7165938d4c945cc1b9d, 3f3a22eebbc32b4fa8ce9c1d5f9db214b45b9335, 5.4.294, 5.10.238, 5.15.185, 6.1.141, 6.6.93, 6.12.31, 6.14.9unaffected
LinuxLinux6.15, 0, 5.4.296, 5.10.240, 5.15.187, 6.1.144, 6.6.97, 6.12.37, 6.15.6, 6.16affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.