CVE-2026-72421

CRITICALPre-NVD 10.010.0—
EchelonGraph scoreMEDIUM confidence

Score 10.0 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-15. A secondary CVSS source baseline 10.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
10.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 10.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

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 v3
10.0
EG Score
10.0CRITICALmedium confidence
EG Risk
50
EG Risk 50/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity100% × 45%
Exploitation1% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
46th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact total (CVSS ≥ 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (8)

Auto-updated Oct 5, 2026
Patch available.
generic

ipv4: fib: Don't ignore error route in local/main tables. - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fd25996f57a95d56bc568c89b4921edcf334b7d8
generic

ipv4: fib: Don't ignore error route in local/main tables. - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b72f0db64205d9ce462038ba995d5d31eff32dc1
generic

ipv4: fib: Don't ignore error route in local/main tables. - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a668fa160247d7bbe921548cb845f607b8b9305f
generic

ipv4: fib: Don't ignore error route in local/main tables. - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a29e95fbc51e8a1b932773fd0e259b2080881443
generic

ipv4: fib: Don't ignore error route in local/main tables. - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9127589aabdee588278e8d0d0bd3709a760a92c8
generic

ipv4: fib: Don't ignore error route in local/main tables. - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/828fad4fd418bcdb9f5d66fec0d184c52a85ec31
generic

ipv4: fib: Don't ignore error route in local/main tables. - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5ae18d87a45698e8244d0fcba64c658c35a7dd3d
generic

ipv4: fib: Don't ignore error route in local/main tables. - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/49eaf1403201357762d745a35882fb734107d763

Vendor Advisories for CVE-2026-72421(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1035.38) @ noble2026-10-05ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (55 versions)
  • every version up to 6.1.180-1: fixed in 6.1.180-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.96-1 (31 versions)
  • every version up to 6.12.100-1: fixed in 6.12.100-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (160 versions)
  • every version up to 7.1.5-1: fixed in 7.1.5-1
—

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 53× in last 7d / 254× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 423 total refreshes for this CVE.

  1. 2026-10-05 06:47 UTCVendor advisory
  2. 2026-10-05 06:47 UTCGHSA enrichment
  3. 2026-10-05 02:24 UTCEG score recompute
  4. 2026-10-05 02:24 UTCVendor advisory
  5. 2026-10-05 02:24 UTCGHSA enrichment
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-04 22:01 UTCVendor advisory
  8. 2026-10-04 22:01 UTCGHSA enrichment
  9. 2026-10-04 16:29 UTCVendor advisory
  10. 2026-10-04 16:29 UTCGHSA enrichment
  11. 2026-10-04 12:07 UTCVendor advisory
  12. 2026-10-04 12:06 UTCGHSA enrichment
  13. 2026-10-04 07:10 UTCVendor advisory
  14. 2026-10-04 07:10 UTCGHSA enrichment
  15. 2026-10-04 03:34 UTCVendor advisory
  16. 2026-10-04 03:34 UTCGHSA enrichment
  17. 2026-10-03 19:34 UTCEG score recompute
  18. 2026-10-03 19:34 UTCVendor advisory
  19. 2026-10-03 19:33 UTCGHSA enrichment
  20. 2026-10-03 14:26 UTCEPSS rescore
  21. 2026-10-03 00:48 UTCVendor advisory
  22. 2026-10-03 00:48 UTCGHSA enrichment
  23. 2026-10-02 19:30 UTCEG score recompute
  24. 2026-10-02 19:30 UTCVendor advisory
  25. 2026-10-02 19:30 UTCGHSA enrichment
Show 75 more
  1. 2026-10-02 15:53 UTCVendor advisory
  2. 2026-10-02 15:53 UTCGHSA enrichment
  3. 2026-10-02 07:09 UTCEG score recompute
  4. 2026-10-02 07:09 UTCVendor advisory
  5. 2026-10-02 07:09 UTCGHSA enrichment
  6. 2026-10-01 19:50 UTCEPSS rescore
  7. 2026-10-01 13:05 UTCVendor advisory
  8. 2026-10-01 13:05 UTCGHSA enrichment
  9. 2026-10-01 09:28 UTCVendor advisory
  10. 2026-10-01 09:28 UTCGHSA enrichment
  11. 2026-10-01 05:51 UTCVendor advisory
  12. 2026-10-01 05:51 UTCGHSA enrichment
  13. 2026-10-01 01:35 UTCVendor advisory
  14. 2026-10-01 01:35 UTCGHSA enrichment
  15. 2026-09-30 21:06 UTCEG score recompute
  16. 2026-09-30 21:06 UTCVendor advisory
  17. 2026-09-30 21:06 UTCGHSA enrichment
  18. 2026-09-30 15:03 UTCEPSS rescore
  19. 2026-09-29 07:22 UTCVendor advisory
  20. 2026-09-29 07:22 UTCGHSA enrichment
  21. 2026-09-29 03:46 UTCVendor advisory
  22. 2026-09-29 03:46 UTCGHSA enrichment
  23. 2026-09-29 00:07 UTCEG score recompute
  24. 2026-09-29 00:07 UTCVendor advisory
  25. 2026-09-29 00:07 UTCGHSA enrichment
  26. 2026-09-28 13:52 UTCEPSS rescore
  27. 2026-09-28 13:35 UTCVendor advisory
  28. 2026-09-28 13:35 UTCGHSA enrichment
  29. 2026-09-28 09:58 UTCVendor advisory
  30. 2026-09-28 09:58 UTCGHSA enrichment
  31. 2026-09-28 06:20 UTCVendor advisory
  32. 2026-09-28 06:20 UTCGHSA enrichment
  33. 2026-09-28 02:43 UTCVendor advisory
  34. 2026-09-28 02:43 UTCGHSA enrichment
  35. 2026-09-27 22:55 UTCVendor advisory
  36. 2026-09-27 22:55 UTCGHSA enrichment
  37. 2026-09-27 16:45 UTCEG score recompute
  38. 2026-09-27 16:45 UTCVendor advisory
  39. 2026-09-27 16:45 UTCGHSA enrichment
  40. 2026-09-27 13:48 UTCEPSS rescore
  41. 2026-09-27 12:28 UTCVendor advisory
  42. 2026-09-27 12:28 UTCGHSA enrichment
  43. 2026-09-27 08:36 UTCEG score recompute
  44. 2026-09-27 08:36 UTCVendor advisory
  45. 2026-09-27 08:36 UTCGHSA enrichment
  46. 2026-09-26 15:59 UTCEPSS rescore
  47. 2026-09-25 09:53 UTCVendor advisory
  48. 2026-09-25 09:53 UTCGHSA enrichment
  49. 2026-09-25 06:16 UTCVendor advisory
  50. 2026-09-25 06:16 UTCGHSA enrichment
  51. 2026-09-25 02:39 UTCVendor advisory
  52. 2026-09-25 02:39 UTCGHSA enrichment
  53. 2026-09-24 17:05 UTCEG score recompute
  54. 2026-09-24 17:05 UTCVendor advisory
  55. 2026-09-24 17:05 UTCGHSA enrichment
  56. 2026-09-24 11:39 UTCVendor advisory
  57. 2026-09-24 11:39 UTCGHSA enrichment
  58. 2026-09-24 08:02 UTCVendor advisory
  59. 2026-09-24 08:02 UTCGHSA enrichment
  60. 2026-09-24 04:04 UTCVendor advisory
  61. 2026-09-24 04:04 UTCGHSA enrichment
  62. 2026-09-24 00:11 UTCVendor advisory
  63. 2026-09-24 00:11 UTCGHSA enrichment
  64. 2026-09-23 20:35 UTCEG score recompute
  65. 2026-09-23 20:35 UTCVendor advisory
  66. 2026-09-23 20:34 UTCGHSA enrichment
  67. 2026-09-23 17:54 UTCEPSS rescore
  68. 2026-09-23 15:01 UTCVendor advisory
  69. 2026-09-23 15:00 UTCGHSA enrichment
  70. 2026-09-23 11:24 UTCVendor advisory
  71. 2026-09-23 11:24 UTCGHSA enrichment
  72. 2026-09-23 07:46 UTCVendor advisory
  73. 2026-09-23 07:46 UTCGHSA enrichment
  74. 2026-09-23 04:08 UTCVendor advisory
  75. 2026-09-23 04:08 UTCGHSA enrichment

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-72421?
CVE-2026-72421 is a critical vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: ipv4: fib: Don't ignore error route in local/main tables. When CONFIGIPMULTIPLE_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,…
When was CVE-2026-72421 disclosed?
CVE-2026-72421 was first published on August 15, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72421 actively exploited?
CVE-2026-72421 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (46th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-72421?
CVE-2026-72421 has a CVSS base score of 10.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-72421?
A fix for CVE-2026-72421 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-72421 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-72421

Explore →

Is Your Infrastructure Affected by CVE-2026-72421?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs