CVE-2026-72421
Linux kernel vulnerability
- Published15 Aug 2026
Description
In the Linux kernel, the following vulnerability has been resolved: ipv4: fib: Don't ignore error route in local/main tables. When CONFIG_IP_MULTIPLE_TABLES is enabled but no rule is added, fib_lookup() performs route lookup directly on two tables. Since the first lookup does not properly bail out, the result of an error route in the merged local/main table could be overwritten by another route in the default table: # unshare -n # ip link set lo up # ip route add 192.168.0.0/24 dev lo table 253 # ip route add unreachable 192.168.0.0/24 # ip route get 192.168.0.1 192.168.0.1 dev lo table default uid 0 cache <local> Once a random rule is added, the error route is respected: # ip rule add table 0 # ip rule del table 0 # ip route get 192.168.0.1 RTNETLINK answers: No route to host Let's fix the inconsistent behaviour.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:NRemediation
No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.
References
- https://git.kernel.org/stable/c/49eaf1403201357762d745a35882fb734107d763
- https://git.kernel.org/stable/c/5ae18d87a45698e8244d0fcba64c658c35a7dd3d
- https://git.kernel.org/stable/c/828fad4fd418bcdb9f5d66fec0d184c52a85ec31
- https://git.kernel.org/stable/c/9127589aabdee588278e8d0d0bd3709a760a92c8
- https://git.kernel.org/stable/c/a29e95fbc51e8a1b932773fd0e259b2080881443
- https://git.kernel.org/stable/c/a668fa160247d7bbe921548cb845f607b8b9305f
- https://git.kernel.org/stable/c/b72f0db64205d9ce462038ba995d5d31eff32dc1
- https://git.kernel.org/stable/c/fd25996f57a95d56bc568c89b4921edcf334b7d8
Frequently asked
Is CVE-2026-72421 being actively exploited?
CVE-2026-72421 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.60%.
How severe is CVE-2026-72421?
CVE-2026-72421 has a CVSS 3.1 base score of 10.0, rated critical. EPSS estimates a 0.60% probability of exploitation.
How do I fix CVE-2026-72421?
Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-72421 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.