CVE-2026-97959net/sched: cls_route: free emptied bucket on filter move
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
In the Linux kernel, the following vulnerability has been resolved: net/sched: cls_route: free emptied bucket on filter move route4_change can move an existing filter to a different top-level bucket: route4_set_parms recomputes the handle from TCA_ROUTE4_TO/ FROM/IIF, and the handle-mismatch check is gated on the 'new' flag, so for an existing filter the new handle may differ from the old one and land in a different bucket. When this happens, the filter is unlinked from the old bucket, but the bucket itself is never freed once it goes empty. The stale empty bucket remains in head->table[], causing route4_delete to report *last=false even after the last live filter is gone. That pins the empty tcf_proto and causes a leak. Fix this by refcounting the filters linked to a bucket and freeing the bucket when the count drops to zero. The existing scan in route4_delete goes away with it. The count is updated at all sites that link or unlink a filter during add, change and delete, and the bucket is dropped from head->table[] as soon as it reaches zero. Conditions to recreate the bug: CONFIG_NET_CLS_ROUTE4=y, CONFIG_NET_SCH_INGRESS=y, CONFIG_NET_CLS_ACT=y. tc qdisc replace dev lo clsact tc filter add dev lo ingress protocol ip pref 100 route from 1 to 1 tc filter change dev lo ingress protocol ip pref 100 handle 0x10001 \ route from 1 to 2 tc filter del dev lo ingress protocol ip pref 100 handle 0x10002 \ route from 1 to 2 tc filter show dev lo ingress | grep -c 'pref 100 route chain 0 '
- CVSS
- Not yet scored
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Oct 3, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from 1e052be69d045c8d0f82ff1116fd3e5a79661745 before 9e7741b41a25b9d49df4d262fa314342e6f95c50; from 1e052be69d045c8d0f82ff1116fd3e5a79661745 before 48d38bf8c22a05fde07ba1f885cde27b851649a2; from 1e052be69d045c8d0f82ff1116fd3e5a79661745 before cc99d26b12431e4e4d0e346ec32764eb42c0aed9; from 1e052be69d045c8d0f82ff1116fd3e5a79661745 before 41e94079200aaf0cdbe4594b0af75710b33da124; from 1e052be69d045c8d0f82ff1116fd3e5a79661745 before 2e2f130951d34871b0643bf700164d97cff4b427; from 1e052be69d045c8d0f82ff1116fd3e5a79661745 before f8495d67434e1cb7e511297687ca55fdb28e4c20; from 1e052be69d045c8d0f82ff1116fd3e5a79661745 before 81dd117c04422c6d0c7974aba9fa6a0ba370959b; from 1e052be69d045c8d0f82ff1116fd3e5a79661745 before 1853f30cf5c84971f99788a76207c6f745380896 | CNA record |
References
- https://git.kernel.org/stable/c/9e7741b41a25b9d49df4d262fa314342e6f95c50
- https://git.kernel.org/stable/c/48d38bf8c22a05fde07ba1f885cde27b851649a2
- https://git.kernel.org/stable/c/cc99d26b12431e4e4d0e346ec32764eb42c0aed9
- https://git.kernel.org/stable/c/41e94079200aaf0cdbe4594b0af75710b33da124
- https://git.kernel.org/stable/c/2e2f130951d34871b0643bf700164d97cff4b427
- https://git.kernel.org/stable/c/f8495d67434e1cb7e511297687ca55fdb28e4c20
- https://git.kernel.org/stable/c/81dd117c04422c6d0c7974aba9fa6a0ba370959b
- https://git.kernel.org/stable/c/1853f30cf5c84971f99788a76207c6f745380896
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.