CVE-2026-98303ipv4: icmp: reject RTN_UNREACHABLE input routes in icmp_route_lookup
- —Not scoredno CVSS score yet
- 0.18%Exploitation in 30 daysEPSS · top 92% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: ipv4: icmp: reject RTN_UNREACHABLE input routes in icmp_route_lookup When the forward output route cannot be used in icmp_route_lookup(), it enters the "reverse path" and calls ip_route_input() on fl4_dec.daddr, the original packet's source address. ip_route_input() only returns an error for truly invalid packets. For unreachable addresses it will succeed and return an input route whose dst.output is set to ip_rt_bug(). The existing check only rejects RTN_LOCAL routes, so the RTN_UNREACHABLE route types can still be returned and later used for output, syzkaller triggering a WARN_ON_ONCE() in ip_rt_bug() as bellow: ------------[ cut here ]------------ WARNING: net/ipv4/route.c:1273 at ip_rt_bug+0x14/0x20 RIP: 0010:ip_rt_bug+0x14/0x20 Call Trace: ip_push_pending_frames+0xfa/0x100 __icmp_send+0x905/0xf10 ip_options_compile+0xc0/0xd0 ip_rcv_finish_core+0x321/0xae0 ip_rcv+0x1de/0x260 __netif_receive_skb_one_core+0x11a/0x130 netif_receive_skb+0x7b/0x260 tun_get_user+0x11bf/0x1c10 ------------[ cut here ]------------ Reject input route that is RTN_UNREACHABLE to fix it. The net warning is only printed for RTN_LOCAL, as RTN_UNREACHABLE is not the result of a race condition.
Timeline
ID reserved
By Linux
- 11 days later
· 11 days later
Published
- 13 days later
· 13 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.18% · top 92% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 8b7817f3a959ed99d7443afc12f78a7e1fcc2063 – < 06083cea4a3b95f5ebc85312f97d7086e6c9e782
- affected 8b7817f3a959ed99d7443afc12f78a7e1fcc2063 – < 83aa83f81a8fec30ff5372dee60b2f0561bcb2ca
- affected 8b7817f3a959ed99d7443afc12f78a7e1fcc2063 – < cac69c50716c712ef0114837c9427da66066124c
- affected 8b7817f3a959ed99d7443afc12f78a7e1fcc2063 – < 1af2d87964d87ba7626d96928d68c09158b5a223
- affected 8b7817f3a959ed99d7443afc12f78a7e1fcc2063 – < fda3000147dc96c75ba162f680bec0a9fecf3037
- affected 8b7817f3a959ed99d7443afc12f78a7e1fcc2063 – < 2998147b59c9df0a51477c7a6b3d1f0ba3127dd4
- affected 2.6.25
- unaffected < 2.6.25
- unaffected 6.1.189 – ≤ 6.1.*
- unaffected 6.6.158 – ≤ 6.6.*
- unaffected 6.12.112 – ≤ 6.12.*
- unaffected 6.18.54 – ≤ 6.18.*
- unaffected 7.2.8 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References6
- https://git.kernel.org/stable/c/06083cea4a3b95f5ebc85312f97d7086e6c9e782 (opens in a new tab)
- https://git.kernel.org/stable/c/83aa83f81a8fec30ff5372dee60b2f0561bcb2ca (opens in a new tab)
- https://git.kernel.org/stable/c/cac69c50716c712ef0114837c9427da66066124c (opens in a new tab)
- https://git.kernel.org/stable/c/1af2d87964d87ba7626d96928d68c09158b5a223 (opens in a new tab)
- https://git.kernel.org/stable/c/fda3000147dc96c75ba162f680bec0a9fecf3037 (opens in a new tab)
- https://git.kernel.org/stable/c/2998147b59c9df0a51477c7a6b3d1f0ba3127dd4 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-93288 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-98303)Record last updated .