Kernel memory corruption via IPv6 device race
Published Nov 12, 2025 · Updated Aug 5, 2026
Use-after-free in the Linux kernel IPv6 output path from 4.13 through 6.17.2 allows remote attackers to corrupt kernel memory. ip6_output() obtains and dereferences the destination network device without an encompassing RCU read-side critical section, allowing concurrent device release to leave a stale pointer. Exploitation requires forwarded IPv6 traffic to coincide with a network-device lifetime change; the resulting access can crash the kernel or corrupt memory.
Summary
What happened
Use-after-free in the Linux kernel IPv6 output path from 4.13 through 6.17.2 allows remote attackers to corrupt kernel memory. ip6_output() obtains and dereferences the destination network device without an encompassing RCU read-side critical section, allowing concurrent device release to leave a stale pointer. Exploitation requires forwarded IPv6 traffic to coincide with a network-device lifetime change; the resulting access can crash the kernel or corrupt memory.
The record
- CVE
- CVE-2025-40158
- Published
- Nov 12, 2025
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 12, 2025CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.13
- Affected versionversion=4a6ce2b6f2ecabbddcfe47e7cf61dd0f00b10e36 <0393f85c3241c19ba8550f04a812e7d19f6b3082
- Affected versionversion=4a6ce2b6f2ecabbddcfe47e7cf61dd0f00b10e36 <11709573cc4e48dc34c80fc7ab9ce5b159e29695
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo