Severity by source
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
AC:H reflects the genuine race condition requiring sustained concurrent pressure; PR:L for CAP_NET_ADMIN obtainable via user namespaces on many distros.
Primary rating from Vendor (Linux).
CVSS VectorVendor: Linux
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Lifecycle Timeline
5DescriptionCVE.org
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:
- Reader walks the RCU-protected bucket chain, finds filter f
- Writer unlinks f, calls route4_reset_fastmap(), then tcf_queue_work()
- Reader calls route4_set_fastmap() and writes f into the cache
*after* the writer's reset, caching a pointer about to be freed
- After the RCU grace period, kfree(f) executes
- 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.
AnalysisAI
Use-after-free in the Linux kernel's route4 (cls_route) traffic classifier fastmap cache allows a local attacker with CAP_NET_ADMIN to read freed kernel heap memory by racing filter deletion against fastmap cache population, potentially escalating to full kernel compromise. Affected versions span Linux 3.18 through current stable branches; the kernel security team backported fixes to eight LTS/stable lines (5.10.265, 5.15.216, 6.1.183, 6.6.152, 6.12.104, 6.18.45, 7.1.9, and 7.2). …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires three concurrent conditions: (1) the cls_route module must be loaded and at least one route4 filter must be actively configured using `tc filter add ... … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The NVD-assigned CVSS 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) accurately reflects the local, low-privilege, high-impact nature of this kernel UAF, but AC:L overstates ease of exploitation - the CVE description explicitly notes the race was only reproducible with an mdelay(100) artificial accelerator and concurrent stress testing provided by ZDI and Santosh, indicating the natural race window is narrow. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | A local user on an Ubuntu system exploits unprivileged user namespaces to create a network namespace, gaining CAP_NET_ADMIN, then configures cls_route filters and drives sustained concurrent filter add/delete cycles while simultaneously flooding the interface with packets matching the targeted (id, iif) tuple. By sustaining the concurrency pressure, the attacker probabilistically wins the race between route4_set_fastmap() and route4_reset_fastmap()+kfree, landing a stale fastmap pointer that survives the RCU grace period and yields a KASAN slab-use-after-free read primitive; with a kernel heap spray primitive, this escalates to arbitrary code execution in ring 0. … |
| Remediation | The primary fix is to upgrade the running kernel to a patched stable release: 5.10.265 or later for the 5.10 LTS branch, 5.15.216 or later for 5.15 LTS, 6.1.183 or later for 6.1 LTS, 6.6.152 or later for 6.6 LTS, 6.12.104 or later for 6.12, 6.18.45 or later for 6.18, 7.1.9 or later for 7.1, or 7.2 for mainline. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: Inventory all Linux systems and identify those running vulnerable kernel versions (3.18 through 7.2 prior to the patched releases listed below). …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-64005
GHSA-qm4p-6qr9-f3w6