Skip to main content
VulnerabilityPublished Updated

CVE-2025-40158: Linux kernel · ipv6: use RCU in ip6_output()

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 8.1 High · fixed in 423895685f367b5a0a956bd14b02df0192bded4c : patch Linux kernel soon.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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-06-16.

Patch
Available – fixed in 423895685f367b5a0a956bd14b02df0192bded4c, 11709573cc4e48dc34c80fc7ab9ce5b159e29695, 92803b826e40e49a5e8a6e208f4b4574e9d19426 +1
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Upgrade Linux kernel to 423895685f367b5a0a956bd14b02df0192bded4c, 11709573cc4e48dc34c80fc7ab9ce5b159e29695, 92803b826e40e49a5e8a6e208f4b4574e9d19426 or 0393f85c3241c19ba8550f04a812e7d19f6b3082.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 4a6ce2b6f2ecabbddcfe47e7cf61dd0f00b10e36, < 423895685f367b5a0a956bd14b02df0192bded4c
Fixed in
  • 423895685f367b5a0a956bd14b02df0192bded4c
LinuxLinuxAffected
  • ≥ 4a6ce2b6f2ecabbddcfe47e7cf61dd0f00b10e36, < 11709573cc4e48dc34c80fc7ab9ce5b159e29695
Fixed in
  • 11709573cc4e48dc34c80fc7ab9ce5b159e29695
LinuxLinuxAffected
  • ≥ 4a6ce2b6f2ecabbddcfe47e7cf61dd0f00b10e36, < 92803b826e40e49a5e8a6e208f4b4574e9d19426
Fixed in
  • 92803b826e40e49a5e8a6e208f4b4574e9d19426
LinuxLinuxAffected
  • ≥ 4a6ce2b6f2ecabbddcfe47e7cf61dd0f00b10e36, < 0393f85c3241c19ba8550f04a812e7d19f6b3082
Fixed in
  • 0393f85c3241c19ba8550f04a812e7d19f6b3082
LinuxLinuxAffected
  • =4.13
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: ipv6: use RCU in ip6_output() Use RCU in ip6_output() in order to use dst_dev_rcu() to prevent possible UAF. We can remove rcu_read_lock()/rcu_read_unlock() pairs from ip6_finish_output2().

References

Community reviews

Loading reviews…