System crash via dying routing-rule reference
Published Aug 15, 2026 · Updated Aug 15, 2026
Race condition in Linux kernel fib_rules_dump() allows local users to crash the system during concurrent routing-rule deletion and dumping. During rocker_router_fib_event()'s RCU traversal, fib_rule_get() increments a dying fib_rule's reference count without first checking whether it is nonzero. Triggering the race requires local low-privileged access; successful exploitation can interrupt service by crashing the host, with no user interaction.
Summary
What happened
Race condition in Linux kernel fib_rules_dump() allows local users to crash the system during concurrent routing-rule deletion and dumping. During rocker_router_fib_event()'s RCU traversal, fib_rule_get() increments a dying fib_rule's reference count without first checking whether it is nonzero. Triggering the race requires local low-privileged access; successful exploitation can interrupt service by crashing the host, with no user interaction.
The record
- CVE
- CVE-2026-74288
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-911, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 15, 2026CVE publishedPublication date reported by the CVE source.
- Aug 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.12
- Affected versionversion=5d7bfd141924a5ece21eb612ad3c56612f041c1e <0f929b59f4cd0e05bb1ecefe12b77e85911d4be2
- Affected versionversion=5d7bfd141924a5ece21eb612ad3c56612f041c1e <1fbc6c6efe78f4454a51afa0587efb6826f60f00
- Affected versionversion=5d7bfd141924a5ece21eb612ad3c56612f041c1e <2821e85c058f81c9948a2fb1a634f7b47457d51c
- Affected versionversion=5d7bfd141924a5ece21eb612ad3c56612f041c1e <2dfdc210d240bd48bb2ea746430b02b5571b6db9
- Affected versionversion=5d7bfd141924a5ece21eb612ad3c56612f041c1e <3af0bc1bd9039e2e50abf3e2d7fee411f38bce4e
- Affected versionversion=5d7bfd141924a5ece21eb612ad3c56612f041c1e <4b7ae30c81c2ee10a644749a3704a5c797ccc308
- Affected versionversion=5d7bfd141924a5ece21eb612ad3c56612f041c1e <a7ef30753353ba6a95d693b1863a0214222a199a
- Affected versionversion=5d7bfd141924a5ece21eb612ad3c56612f041c1e <bb4a5b3c91af3c8d705bb2e9f6f8069a70db26fc
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo