System crash via repeated HTB deactivation
Published May 20, 2025 · Updated May 11, 2026
NULL pointer dereference in Linux kernel HTB qdisc versions 6.1.138, 6.6.90, 6.12.28, and 6.14.6 allows local users to crash the system. During HTB dequeue, fq_codel_dequeue can reduce the backlog to zero and call htb_deactivate before htb_dequeue_tree calls it again, leaving clprio[prio]->ptr NULL for htb_next_rb_node. A local low-privileged user must reach the affected traffic-control dequeue path; the reported consequence is a kernel crash, not data disclosure or modification.
Summary
What happened
NULL pointer dereference in Linux kernel HTB qdisc versions 6.1.138, 6.6.90, 6.12.28, and 6.14.6 allows local users to crash the system. During HTB dequeue, fq_codel_dequeue can reduce the backlog to zero and call htb_deactivate before htb_dequeue_tree calls it again, leaving clprio[prio]->ptr NULL for htb_next_rb_node. A local low-privileged user must reach the affected traffic-control dequeue path; the reported consequence is a kernel crash, not data disclosure or modification.
The record
- CVE
- CVE-2025-37953
- Published
- May 20, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 20, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 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=0a188c0e197383683fd093ab1ea6ce9a5869a6ea <98cd7ed92753090a714f0802d4434314526fe61d
- Affected versionversion=32ae12ce6a9f6bace186ca7335220ff59b6cc3cd <a9945f7cf1709adc5d2d31cb6cfc85627ce299a8
- Affected versionversion=5ba8b837b522d7051ef81bacf3d95383ff8edce5 <3769478610135e82b262640252d90f6efb05be71
- Affected versionversion=6.1.138 <6.1.139
- Affected versionversion=6.12.28 <6.12.29
- Affected versionversion=6.14.6 <6.14.7
- Affected versionversion=6.6.90 <6.6.91
- Affected versionversion=73cf6af13153d62f9b76eff422eea79dbc70f15e <c928dd4f6bf0c25c72b11824a1e9ac9bd37296a0
- Affected versionversion=967955c9e57f8eebfccc298037d4aaf3d42bc1c9 <c2d25fddd867ce20a266806634eeeb5c30cb520c
- Affected versionversion=a61f1b5921761fbaf166231418bc1db301e5bf59 <c4792b9e38d2f61b07eac72f10909fa76130314b
- Affected versionversion=bbbf5e0f87078b715e7a665d662a2c0e77f044ae <31ff70ad39485698cf779f2078132d80b57f6c07
- Affected versionversion=e6b45f4de763b00dc1c55e685e2dd1aaf525d3c1 <99ff8a20fd61315bf9ae627440a5ff07d22ee153
What conditions does exploitation require?
What is affected?
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