CVE-2025-38107: net_sched: ets: fix a race in ets_qdisc_change()
In the Linux kernel, the following vulnerability has been resolved:
net_sched: ets: fix a race in ets_qdisc_change()
Gerrard Tai reported a race condition in ETS, whenever SFQ perturb timer
fires at the wrong time.
The race is as follows:
CPU 0 CPU 1
[1]: lock root
[2]: qdisc_tree_flush_backlog()
[3]: unlock root
|
| [5]: lock root
| [6]: rehash
| [7]: qdisc_tree_reduce_backlog()
|
[4]: qdisc_put()
This can be abused to underflow a parent's qlen.
Calling qdisc_purge_queue() instead of qdisc_tree_flush_backlog()
should fix the race, because all packets will be purged from the qdisc
before releasing the lock.
Security readout for executives and security teams
Plain-English summary
A Linux traffic-control race can corrupt queue accounting when ETS and SFQ operations overlap. A local, low-privileged attacker may be able to trigger serious confidentiality, integrity, and availability impacts. Exposure depends on the installed kernel and use or accessibility of the affected queuing functionality.
Executive priority
Treat as a high-priority local privilege-boundary issue, especially on shared Linux hosts, container platforms, and systems admitting untrusted users. Patch through supported vendor channels after confirming applicability. Internet exposure alone does not establish vulnerability because the documented attack vector is local.
Technical view
CVE-2025-38107 is a race in ets_qdisc_change(). An SFQ perturb timer can rehash queues between backlog flushing and qdisc release, allowing a parent qdisc's qlen to underflow. The kernel fix purges queued packets with qdisc_purge_queue() before releasing the lock. CVSS 3.1 is 7.8 with local, low-complexity, low-privilege attack characteristics.
Likely exposure
Potentially exposed systems run an affected Linux kernel and make the implicated ETS/SFQ traffic-control path reachable to a local low-privileged user. The supplied version list is ambiguous, so inventory should be matched against distribution advisories and the applicable stable-kernel fix commit rather than version numbers alone.
Exploitation context
The supplied record does not identify public exploitation, and its KEV indicator is false. Exploitation is local, requires low privileges, needs no user interaction, and is rated low complexity. No remote attack path is established by the provided evidence.
Researcher notes
The core defect is an ordering race across root-qdisc locking, backlog handling, SFQ rehashing, and qdisc release. The described consequence is parent qlen underflow. The supplied CVSS asserts high confidentiality, integrity, and availability impact, but the bundle does not provide a public proof of concept or observed exploitation details.
Mitigation direction
Install the kernel security update provided by the operating-system or appliance vendor.
Match custom kernels against the applicable upstream stable fix commit.
Prioritize multi-user systems where untrusted local users can reach traffic-control functionality.
If patching is delayed, review vendor guidance for supported temporary mitigations.
Validation and detection
Record each system's running kernel version, distribution release, and vendor package revision.
Confirm the installed package includes the applicable upstream stable fix.
Review whether ETS and SFQ queuing disciplines are configured or available to untrusted local users.
After updating, reboot where required and verify the patched kernel is running.
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-38107 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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
1ADP providers
10Source links
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.