Kernel compromise via RED queue-length race
Published Jul 3, 2025 · Updated Aug 5, 2026
Race condition in the Linux RED scheduler allows local users to compromise the kernel through concurrent RED changes and SFQ rehashing. __red_change() releases the root lock after flushing backlog, allowing an SFQ timer rehash to reduce the same backlog before qdisc_put() and underflow the parent queue length. CAP_NET_ADMIN in the owning user namespace is required; the resulting stale queue state enables kernel memory disclosure, corruption, or panic.
Summary
What happened
Race condition in the Linux RED scheduler allows local users to compromise the kernel through concurrent RED changes and SFQ rehashing. __red_change() releases the root lock after flushing backlog, allowing an SFQ timer rehash to reduce the same backlog before qdisc_put() and underflow the parent queue length. CAP_NET_ADMIN in the owning user namespace is required; the resulting stale queue state enables kernel memory disclosure, corruption, or panic.
The record
- CVE
- CVE-2025-38108
- Published
- Jul 3, 2025
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-362, T1068, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 3, 2025CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0c8d13ac96070000da33f394f45e9c19638483c5 <110a47efcf23438ff8d31dbd9c854fae2a48bf98
- Affected versionversion=0c8d13ac96070000da33f394f45e9c19638483c5 <2790c4ec481be45a80948d059cd7c9a06bc37493
- Affected versionversion=0c8d13ac96070000da33f394f45e9c19638483c5 <2a71924ca4af59ffc00f0444732b6cd54b153d0e
- Affected versionversion=0c8d13ac96070000da33f394f45e9c19638483c5 <444ad445df5496a785705019268a8a84b84484bb
- Affected versionversion=0c8d13ac96070000da33f394f45e9c19638483c5 <4b755305b2b0618e857fdadb499365b5f2e478d1
- Affected versionversion=0c8d13ac96070000da33f394f45e9c19638483c5 <85a3e0ede38450ea3053b8c45d28cf55208409b8
- Affected versionversion=0c8d13ac96070000da33f394f45e9c19638483c5 <a1bf6a4e9264a685b0e642994031f9c5aad72414
- Affected versionversion=0c8d13ac96070000da33f394f45e9c19638483c5 <f569984417a4e12c67366e69bdcb752970de921d
- Affected versionversion=5.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo