CVE-2026-74583

net/sched: cls_route: fix fastmap use-after-free on filter

HIGH
7.8
CVSS Score
Published: August 21, 2026 at 04:31 PM UTC
Updated: October 16, 2026 at 08:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: net/sched: cls_route: fix fastmap use-after-free on filter The route4 classifier maintains a 16-slot fastmap cache that stores raw struct route4_filter pointers indexed by (id, iif). The reader (route4_classify) populates this cache via route4_set_fastmap() for every classified packet that hits a filter. The writer (route4_delete, route4_change) clears the cache via route4_reset_fastmap() before RCU-deferred kfree of the filter. This creates a UAF race: 1. Reader walks the RCU-protected bucket chain, finds filter f 2. Writer unlinks f, calls route4_reset_fastmap(), then tcf_queue_work() 3. Reader calls route4_set_fastmap() and writes f into the cache *after* the writer's reset, caching a pointer about to be freed 4. After the RCU grace period, kfree(f) executes 5. Next classified packet on the same (id, iif) tuple hits the stale fastmap entry and reads f->res from freed memory Reproduced with an mdelay(100) accelerator in route4_set_fastmap() and a concurrent add/delete stress test (provided by both zdi and Santosh). Both triggered KASAN slab-use-after-free reports in the route4 fastmap paths. Fix: Introduce a per-filter boolean dying flag to suppress stale fastmap republishing by in-flight readers.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

1109c00547fc66df45b9ff923544be4c1e1bec133.18
Vendor states this is fixed in 0e7a8cf8895b06d07c7311f028eba16ad742b9bc (fixed)
Vendor states this is fixed in 47d7f7051253bdc02b1d245d87e38f16d31a74df (fixed)
Vendor states this is fixed in 5ec9001be6d0eb527251125632ec8fe88278897f (fixed)
Vendor states this is fixed in 7897198b26445b4009a057bda1986b94a99e5d5f (fixed)
Vendor states this is fixed in 820f083c294ad6d319c02a7d43294f2ed2565139 (fixed)
Vendor states this is fixed in a17f636c9330eac879822ce29f998e5abd1b72c1 (fixed)
Vendor states this is fixed in ae9aff87025219005a2d16b4fe83d6f24643e50d (fixed)
Vendor states this is fixed in b969984b2bdc85d721ce4047cd270cd37ec705a2 (fixed)
Vendor states this is fixed in 3.18 (unaffected)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.104 (unaffected)
Vendor states this is fixed in 6.18.45 (unaffected)
Vendor states this is fixed in 6.6.152 (unaffected)
Vendor states this is fixed in 7.1.9 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card