CVE-2023-53595
BaseFortify
Publication date: 2025-10-04
Last updated on: 2026-03-21
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
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 related to the octeontx2-pf mcs component. It occurs when the system is rebooted after creating a macsec interface, causing kernel crashes due to improper teardown order. The issue leads to the kernel attempting to access a NULL pointer, resulting in a crash.
How can this vulnerability impact me? :
This vulnerability can cause the Linux kernel to crash during system reboot after creating a macsec interface, leading to system instability or downtime. Such crashes can disrupt normal operations and potentially cause data loss or service interruptions.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring the system logs for kernel NULL pointer dereference crash messages related to the macsec interface and octeontx2-pf driver. Look for log entries similar to: 'Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000' and call traces involving 'cn10k_mdo_del_secy', 'macsec_common_dellink', or 'macsec_notify'. You can use commands like 'dmesg | grep -i "NULL pointer dereference"' or 'journalctl -k | grep -i macsec' to find relevant kernel crash logs.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include applying the patch that fixes the NULL pointer dereference by correcting the teardown order of the macsec interface on octeontx2-pf. Until the patch is applied, avoid rebooting the system after creating a macsec interface to prevent the crash. Monitoring for crash logs and avoiding use of the affected macsec interface on octeontx2-pf hardware can also reduce risk.