sch_htb: make htb_deactivate() idempotent
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 98cd7ed92753090a714f0802d4434314526fe61d, Kernel a9945f7cf1709adc5d2d31cb6cfc85627ce299a8, Kernel 3769478610135e82b262640252d90f6efb05be71 and 9 more.
In the Linux kernel, the following vulnerability has been resolved: sch_htb: make htb_deactivate() idempotent Alan reported a NULL pointer dereference in htb_next_rb_node() after we made htb_qlen_notify() idempotent. It turns out in the following case it introduced some regression: htb_dequeue_tree(): |-> fq_codel_dequeue() |-> qdisc_tree_reduce_backlog() |-> htb_qlen_notify() |-> htb_deactivate() |-> htb_next_rb_node() |-> htb_deactivate() For htb_next_rb_node(), after calling the 1st htb_deactivate(), the clprio[prio]->ptr could be already set to NULL, which means htb_next_rb_node() is vulnerable here. For htb_deactivate(), although we checked qlen before calling it, in case of qlen==0 after qdisc_tree_reduce_backlog(), we may call it again which triggers the warning inside. To fix the issues here, we need to: 1) Make htb_deactivate() idempotent, that is, simply return if we already call it before. 2) Make htb_next_rb_node() safe against ptr==NULL. Many thanks to Alan for testing and for the reproducer.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=0a188c0e197383683fd093ab1ea6ce9a5869a6ea <98cd7ed92753090a714f0802d4434314526fe61d, >=32ae12ce6a9f6bace186ca7335220ff59b6cc3cd <a9945f7cf1709adc5d2d31cb6cfc85627ce299a8, >=5ba8b837b522d7051ef81bacf3d95383ff8edce5 <3769478610135e82b262640252d90f6efb05be71, >=6.1.138 <6.1.139, >=6.12.28 <6.12.29, >=6.14.6 <6.14.7, >=6.6.90 <6.6.91, >=73cf6af13153d62f9b76eff422eea79dbc70f15e <c928dd4f6bf0c25c72b11824a1e9ac9bd37296a0, >=967955c9e57f8eebfccc298037d4aaf3d42bc1c9 <c2d25fddd867ce20a266806634eeeb5c30cb520c, >=a61f1b5921761fbaf166231418bc1db301e5bf59 <c4792b9e38d2f61b07eac72f10909fa76130314b, >=bbbf5e0f87078b715e7a665d662a2c0e77f044ae <31ff70ad39485698cf779f2078132d80b57f6c07, >=e6b45f4de763b00dc1c55e685e2dd1aaf525d3c1 <99ff8a20fd61315bf9ae627440a5ff07d22ee153 | 98cd7ed92753090a714f0802d4434314526fe61d, a9945f7cf1709adc5d2d31cb6cfc85627ce299a8, 3769478610135e82b262640252d90f6efb05be71, 6.1.139, 6.12.29, 6.14.7, 6.6.91, c928dd4f6bf0c25c72b11824a1e9ac9bd37296a0, c2d25fddd867ce20a266806634eeeb5c30cb520c, c4792b9e38d2f61b07eac72f10909fa76130314b, 31ff70ad39485698cf779f2078132d80b57f6c07, 99ff8a20fd61315bf9ae627440a5ff07d22ee153 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket