CVE-2026-45905: xfrm: fix ip_rt_bug race in icmp_route_lookup reverse path
Noroxi assessment
Priority: Monitor (action score 18/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.11% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: Linux Linux 1c9ef28f643cce34a6a6c36c8f4d6d60a60db7e1, 2c1f59005da9dd4b07b26984fd719e36557dc57c, 423ce12d10b426709489d6b84fdaa6d2f31c5652.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 1c9ef28f643cce34a6a6c36c8f4d6d60a60db7e1, 2c1f59005da9dd4b07b26984fd719e36557dc57c, 423ce12d10b426709489d6b84fdaa6d2f31c5652 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: xfrm: fix ip_rt_bug race in icmp_route_lookup reverse path icmp_route_lookup() performs multiple route lookups to find a suitable route for sending ICMP error messages, with special handling for XFRM (IPsec) policies. The lookup sequence is: 1. First, lookup output route for ICMP reply (dst = original src) 2. Pass through xfrm_lookup() for policy check 3. If blocked (-EPERM) or dst is not local, enter "reverse path" 4. In reverse path, call xfrm_decode_session_reverse() to get fl4_dec which reverses the original packet's flow (saddr<->daddr swapped) 5. If fl4_dec.saddr is local (we are the original destination), use __ip_route_output_key() for output route lookup 6. If fl4_dec.saddr is NOT local (we are a forwarding node), use ip_route_input() to simulate the reverse packet's input path 7. Finally, pass rt2 through xfrm_lookup() with XFRM_LOOKUP_ICMP flag The bug occurs in step 6: ip_route_input() is called with fl4_dec.daddr (original packet's source) as destination. If this address becomes local between the initial check and ip_route_input() call (e.g., due to concurrent "ip addr add"), ip_route_input() returns a LOCAL route with dst.output set to ip_rt_bug. This route is then used for ICMP output, causing dst_output() to call ip_rt_bug(), triggering a WARN_ON: ------------[ cut here ]------------ WARNING: net/ipv4/route.c:1275 at ip_rt_bug+0x21/0x30, CPU#1 Call Trace: <TASK> ip_push_pending_frames+0x202/0x240 icmp_push_reply+0x30d/0x430 __icmp_send+0x1149/0x24f0 ip_options_compile+0xa2/0xd0 ip_rcv_finish_core+0x829/0x1950 ip_rcv+0x2d7/0x420 __netif_receive_skb_one_core+0x185/0x1f0 netif_receive_skb+0x90/0x450 tun_get_user+0x3413/0x3fb0 tun_chr_write_iter+0xe4/0x220 ... Fix this by checking rt2->rt_type after ip_route_input(). If it's RTN_LOCAL, the route cannot be used for output, so treat it as an error. The reproducer requires kernel modification to widen the race window, making it unsuitable as a selftest. It is available at: https://gist.github.com/mrpre/eae853b72ac6a750f5d45d64ddac1e81
- Published
- May 27, 2026
- Updated
- Jun 24, 2026
- EPSS
- 0.1% · 1th percentile
- CWE
- CWE-362
Report tools
Action score
18
Monitor
Low priority for now.
- CVSS
- 18 / 40 · 4.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel2.6.25 and later · before 6.1.165
- linux linux kernel6.2 and later · before 6.6.128
- linux linux kernel6.7 and later · before 6.12.75
- linux linux kernel6.13 and later · before 6.18.14
- linux linux kernel6.19 and later · before 6.19.4
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.25affected
- 8b7817f3a959ed99d7443afc12f78a7e1fcc2063 and later · before 9a95ec9144eeff1fc6fbcc21b677e322c6f1430baffected · git
- 8b7817f3a959ed99d7443afc12f78a7e1fcc2063 and later · before 2c1f59005da9dd4b07b26984fd719e36557dc57caffected · git
- 8b7817f3a959ed99d7443afc12f78a7e1fcc2063 and later · before b04061f89ffc6168e7ec3c71d0086ec3c3797228affected · git
- 8b7817f3a959ed99d7443afc12f78a7e1fcc2063 and later · before 1c9ef28f643cce34a6a6c36c8f4d6d60a60db7e1affected · git
- 8b7817f3a959ed99d7443afc12f78a7e1fcc2063 and later · before 423ce12d10b426709489d6b84fdaa6d2f31c5652affected · git
- 8b7817f3a959ed99d7443afc12f78a7e1fcc2063 and later · before 81b84de32bb27ae1ae2eb9acf0420e9d0d14bf00affected · git
- before 2.6.25not affected · semver
- 6.1.165 and later · up to and including 6.1.*not affected · semver
- 6.6.128 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.170-1 | 6.1.170-1 |
| Debian:13 | linux | before 6.12.85-1 | 6.12.85-1 |
| Debian:14 | linux | before 6.18.14-1 | 6.18.14-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-45903May 27, 2026 · bpf: Fix memory access flags in helper prototypes28Monitor
- ← EarlierCVE-2026-45904May 27, 2026 · powerpc/eeh: fix recursive pci_lock_rescan_remove locking in EEH event handling22Monitor
- Later →CVE-2026-45906May 27, 2026 · power: supply: pf1550: Fix use-after-free in power_supply_changed()31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1c9ef28f643cce34a6a6c36c8f4d6d60a60db7e1 | Vendor (CNA) |
| Linux Linux | 2c1f59005da9dd4b07b26984fd719e36557dc57c | Vendor (CNA) |
| Linux Linux | 423ce12d10b426709489d6b84fdaa6d2f31c5652 | Vendor (CNA) |
| Linux Linux | 81b84de32bb27ae1ae2eb9acf0420e9d0d14bf00 | Vendor (CNA) |
| Linux Linux | 9a95ec9144eeff1fc6fbcc21b677e322c6f1430b | Vendor (CNA) |
| Linux Linux | b04061f89ffc6168e7ec3c71d0086ec3c3797228 | Vendor (CNA) |
| debian:linux | 6.1.170-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0290 · Jun 2, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')CVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/2c1f59005da9dd4b07b26984fd719e36557dc57c
- git.kernel.org/stable/c/423ce12d10b426709489d6b84fdaa6d2f31c5652
- git.kernel.org/stable/c/81b84de32bb27ae1ae2eb9acf0420e9d0d14bf00
- git.kernel.org/stable/c/9a95ec9144eeff1fc6fbcc21b677e322c6f1430b
- git.kernel.org/stable/c/b04061f89ffc6168e7ec3c71d0086ec3c3797228
Vendor advisories and official records. Exploit/PoC links are deliberately left out.