net/sched: act_ct: don't WARN on benign flow_offload_alloc() failure
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 00734f3684fcec42c319bedfe68a5d357c720b53, Kernel 424ba52c0058deeb940d02cba52eb0aeb288db33, Kernel 47abe7a5c4eb53269aca3506446f851572a059a3 and 5 more.
In the Linux kernel, the following vulnerability has been resolved: net/sched: act_ct: don't WARN on benign flow_offload_alloc() failure flow_offload_alloc() returns NULL when the conntrack entry is dying (e.g. raced with a conntrack flush) or when the GFP_ATOMIC allocation fails; both are expected under load and neither is a kernel bug. This path runs from softirq on every committed packet, so with panic_on_warn=1 an unprivileged user can panic the box just by racing a conntrack flush against a `tc ... action ct commit` classifier. Reproduced with a custom repro under QEMU: a small, fixed set of UDP flows through `tc filter ... action ct commit` on lo, raced against threads flooding bare ctnetlink CT_DELETE (flush) requests. Hits WARNING: net/sched/act_ct.c:437 (tcf_ct_flow_table_add(), inlined into tcf_ct_act() in this build) within ~15s on the unpatched kernel; same setup is clean on the patched kernel. The fix itself is behavior-preserving: both branches already did `goto err_alloc` before and after, only the WARN is removed.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =5.7, >=64ff70b80fd403110b67dd9f7184a604fdb0da43 <00734f3684fcec42c319bedfe68a5d357c720b53, >=64ff70b80fd403110b67dd9f7184a604fdb0da43 <424ba52c0058deeb940d02cba52eb0aeb288db33, >=64ff70b80fd403110b67dd9f7184a604fdb0da43 <47abe7a5c4eb53269aca3506446f851572a059a3, >=64ff70b80fd403110b67dd9f7184a604fdb0da43 <650787233c2fd6e515a7c5f371019a9fa080ccd2, >=64ff70b80fd403110b67dd9f7184a604fdb0da43 <af475f599270e59313552e6c6f3af8507da672b8, >=64ff70b80fd403110b67dd9f7184a604fdb0da43 <d512c484bd93a5f2794aa03c9faeb7bcb82dbd4a, >=64ff70b80fd403110b67dd9f7184a604fdb0da43 <d805560ad69cb266d669341ca01e26bffb0d2c67, >=64ff70b80fd403110b67dd9f7184a604fdb0da43 <e8fcf3f08834e939b797311742ee72b1e2a08096 | 00734f3684fcec42c319bedfe68a5d357c720b53, 424ba52c0058deeb940d02cba52eb0aeb288db33, 47abe7a5c4eb53269aca3506446f851572a059a3, 650787233c2fd6e515a7c5f371019a9fa080ccd2, af475f599270e59313552e6c6f3af8507da672b8, d512c484bd93a5f2794aa03c9faeb7bcb82dbd4a, d805560ad69cb266d669341ca01e26bffb0d2c67, e8fcf3f08834e939b797311742ee72b1e2a08096 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket