CVE-2023-53343
BaseFortify
Publication date: 2025-09-17
Last updated on: 2025-12-11
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 4.14 (inc) to 4.19.291 (exc) |
| linux | linux_kernel | From 4.20 (inc) to 5.4.251 (exc) |
| linux | linux_kernel | From 5.5 (inc) to 5.10.188 (exc) |
| linux | linux_kernel | From 5.11 (inc) to 5.15.121 (exc) |
| linux | linux_kernel | From 5.16 (inc) to 6.1.40 (exc) |
| linux | linux_kernel | From 6.2 (inc) to 6.4.5 (exc) |
| linux | linux_kernel | 6.5 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-476 | The product dereferences a pointer that it expects to be valid but is NULL. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a NULL pointer dereference in the Linux kernel's IPv6 ICMP handling code. It occurs when a specially crafted IPv6 packet with certain extension headers (like RPL or SRv6) uses the same link-local address as both source and destination, and is forwarded to an external IP. The kernel fails to properly check if a routing entry is NULL before dereferencing it, leading to a kernel crash (NULL pointer dereference).
How can this vulnerability impact me? :
This vulnerability can cause the Linux kernel to crash due to a NULL pointer dereference when processing certain IPv6 packets. This can lead to denial of service (DoS) conditions on affected systems, potentially disrupting network services and system availability.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring for kernel NULL pointer dereference crashes related to icmp6 and IPv6 extension headers, especially involving packets with link-local source and destination addresses and segment routing headers. The provided example script demonstrates how to generate a test packet that triggers the issue using Python and scapy. You can use similar scripts to test your system. Additionally, checking kernel logs (e.g., dmesg) for Oops messages referencing icmp6_send or NULL pointer dereference in IPv6 handling can help detect exploitation attempts.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include disabling or restricting the processing of IPv6 Segment Routing and related IPv6 extension headers (such as RPL, SRv6) if not needed, as the vulnerability involves these headers. You can disable segment routing by setting /proc/sys/net/*seg6_enabled* files to 0. Also, ensure your Linux kernel is updated to a version where this vulnerability is fixed. Monitoring and filtering suspicious IPv6 packets with link-local source and destination addresses and segment routing headers at network boundaries can help reduce exposure.