Kernel crash via unchecked IPv6 route device pointer
Published Sep 17, 2025 · Updated Sep 17, 2025
A NULL pointer dereference in the Linux kernel allows local users to crash the system via a crafted IPv6 extension-header packet. When extension-header route lookup fails, icmp6_dev() reads rt6i_idev->dev from ip6_null_entry without first checking whether rt6i_idev is NULL. The demonstrated trigger requires local raw IPv6 packet injection and enabled segment routing; the bounded consequence is a kernel crash.
Summary
What happened
A NULL pointer dereference in the Linux kernel allows local users to crash the system via a crafted IPv6 extension-header packet. When extension-header route lookup fails, icmp6_dev() reads rt6i_idev->dev from ip6_null_entry without first checking whether rt6i_idev is NULL. The demonstrated trigger requires local raw IPv6 packet injection and enabled segment routing; the bounded consequence is a kernel crash.
The record
- CVE
- CVE-2023-53343
- Published
- Sep 17, 2025
- Updated
- Sep 17, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 17, 2025CVE publishedPublication date reported by the CVE source.
- Sep 17, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.14
- Affected versionversion=4832c30d5458387ff2533ff66fbde26ad8bb5a2d <1462e9d9aa52d14665eaca6d89d22c4af44ede04
- Affected versionversion=4832c30d5458387ff2533ff66fbde26ad8bb5a2d <2aaa8a15de73874847d62eb595c6683bface80fd
- Affected versionversion=4832c30d5458387ff2533ff66fbde26ad8bb5a2d <3fabca5d9cae0140b6aad09a1c6b9aa57089fbb8
- Affected versionversion=4832c30d5458387ff2533ff66fbde26ad8bb5a2d <61b4c4659746959056450b92a5d7e6bc1243b31b
- Affected versionversion=4832c30d5458387ff2533ff66fbde26ad8bb5a2d <8803c59fde4dd370a627dfbf7183682fa0cabf70
- Affected versionversion=4832c30d5458387ff2533ff66fbde26ad8bb5a2d <aa657d319e6c7502a4eb85cc0ee80cc81b8e5724
- Affected versionversion=4832c30d5458387ff2533ff66fbde26ad8bb5a2d <d30ddd7ff15df9d91a793ce3f06f0190ff7afacc
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
- Linux kernel Scapy IPv6 triggerproof of concept · demonstrated
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