Service interruption via IPv6 error-path memory leak
Published Apr 3, 2025 · Updated Sep 8, 2026
Memory leakage in Linux kernel IPv6 routing code allows local users to exhaust memory and interrupt affected Linux-based systems. In fib6_nh_init(), failure to allocate rt6i_pcpu leaves nh_common.nhc_pcpu_rth_output allocated because the error path omits fib_nh_common_release(). Reachability requires local low-privileged access and an allocation failure; repeated failures consume kernel memory without altering data.
Summary
What happened
Memory leakage in Linux kernel IPv6 routing code allows local users to exhaust memory and interrupt affected Linux-based systems. In fib6_nh_init(), failure to allocate rt6i_pcpu leaves nh_common.nhc_pcpu_rth_output allocated because the error path omits fib_nh_common_release(). Reachability requires local low-privileged access and an allocation failure; repeated failures consume kernel memory without altering data.
The record
- CVE
- CVE-2025-22005
- Published
- Apr 3, 2025
- Updated
- Sep 8, 2026
- Vendor
- Siemens
- Product
- SIPLUS S7-1500 CPU 1518-4 PN/DP MFP
- Classifications
- CWE-401, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 3, 2025CVE publishedPublication date reported by the CVE source.
- Sep 8, 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=V3.1.6 <*
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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