Skip to main content
VulnerabilityPublished Updated

CVE-2026-45905: Linux kernel · xfrm: fix ip_rt_bug race in icmp_route_lookup reverse path

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in b04061f89ffc6168e7ec3c71d0086ec3c3797228 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:05 UTC

Severity
Medium

Rated Medium by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in b04061f89ffc6168e7ec3c71d0086ec3c3797228, 423ce12d10b426709489d6b84fdaa6d2f31c5652, 81b84de32bb27ae1ae2eb9acf0420e9d0d14bf00 +3

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 8b7817f3a959ed99d7443afc12f78a7e1fcc2063, < b04061f89ffc6168e7ec3c71d0086ec3c3797228
Fixed in
  • b04061f89ffc6168e7ec3c71d0086ec3c3797228
LinuxLinuxAffected
  • ≥ 8b7817f3a959ed99d7443afc12f78a7e1fcc2063, < 423ce12d10b426709489d6b84fdaa6d2f31c5652
Fixed in
  • 423ce12d10b426709489d6b84fdaa6d2f31c5652
LinuxLinuxAffected
  • ≥ 8b7817f3a959ed99d7443afc12f78a7e1fcc2063, < 81b84de32bb27ae1ae2eb9acf0420e9d0d14bf00
Fixed in
  • 81b84de32bb27ae1ae2eb9acf0420e9d0d14bf00
LinuxLinuxAffected
  • ≥ 8b7817f3a959ed99d7443afc12f78a7e1fcc2063, < 9a95ec9144eeff1fc6fbcc21b677e322c6f1430b
Fixed in
  • 9a95ec9144eeff1fc6fbcc21b677e322c6f1430b
LinuxLinuxAffected
  • ≥ 8b7817f3a959ed99d7443afc12f78a7e1fcc2063, < 2c1f59005da9dd4b07b26984fd719e36557dc57c
Fixed in
  • 2c1f59005da9dd4b07b26984fd719e36557dc57c
LinuxLinuxAffected
  • ≥ 8b7817f3a959ed99d7443afc12f78a7e1fcc2063, < 1c9ef28f643cce34a6a6c36c8f4d6d60a60db7e1
Fixed in
  • 1c9ef28f643cce34a6a6c36c8f4d6d60a60db7e1

AI-suggested

A fix is available and has been applied in multiple Linux kernel commits. Users should update to a Linux kernel version that includes the fix identified by the provided commit hashes. No additional mitigation is required beyond applying the official patch.

Description

A race condition in the Linux kernel's icmp_route_lookup function can cause a WARN_ON in the networking code due to improper handling of route lookups when addresses change concurrently. This occurs when ip_route_input() returns a LOCAL route that is incorrectly used for ICMP output, triggering a kernel warning and potential instability. The issue arises from a timing window where an address becomes local between checks, leading to a route type misuse.

References

Community reviews

Loading reviews…