net/sched: act_ct: don't WARN on benign flow_offload_alloc() failure
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 64ff70b80fd403110b67dd9f7184a604fdb0da43 · < 00734f3684fcec42c319bedfe68a5d357c720b53| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel's act_ct code can issue a warning when flow_offload_alloc() fails during conntrack processing. On a system with panic_on_warn=1, a local unprivileged user can panic the system by racing a conntrack flush against packets using a tc action ct commit classifier.
Operators running Linux kernels with tc action ct commit and panic_on_warn=1 should check whether their kernel includes the fix; affected versions were not specified.