Denial of service via IPv6 route-cache lock contention
Published Jul 5, 2024 · Updated Nov 4, 2025
Denial of service in the Linux kernel before 6.3 allows remote attackers to exhaust CPU via crafted ICMPv6 Packet Too Big traffic. The IPv6 destination route cache scans every entry during garbage collection while holding a lock after its size threshold is exceeded. A flood of crafted messages creates lock contention and saturates CPU, making network destinations unreachable.
Summary
What happened
Denial of service in the Linux kernel before 6.3 allows remote attackers to exhaust CPU via crafted ICMPv6 Packet Too Big traffic. The IPv6 destination route cache scans every entry during garbage collection while holding a lock after its size threshold is exceeded. A flood of crafted messages creates lock contention and saturates CPU, making network destinations unreachable.
The record
- CVE
- CVE-2023-52340
- Published
- Jul 5, 2024
- Updated
- Nov 4, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-400, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 5, 2024CVE publishedPublication date reported by the CVE source.
- Nov 4, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
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