CVE-2023-53556
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 | 6.5 |
| linux | linux_kernel | 6.5 |
| linux | linux_kernel | From 5.16 (inc) to 6.1.42 (exc) |
| linux | linux_kernel | From 5.11 (inc) to 5.15.123 (exc) |
| linux | linux_kernel | From 5.5 (inc) to 5.10.188 (exc) |
| linux | linux_kernel | From 6.2 (inc) to 6.4.7 (exc) |
| linux | linux_kernel | From 3.14 (inc) to 5.4.251 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-416 | The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a use-after-free bug in the Linux kernel's iavf driver related to network device handling. Specifically, it occurs because the code adds NAPI structures for all allocated q_vectors but only deletes some of them before freeing the q_vectors, leaving invalid pointers in the device's napi_list. This can cause the kernel to access freed memory, leading to potential crashes or undefined behavior.
How can this vulnerability impact me? :
The use-after-free vulnerability can cause system instability, including kernel crashes or denial of service, by allowing the kernel to access invalid memory. This could disrupt network functionality on affected systems and potentially be exploited to cause further damage or escalate privileges, depending on the environment.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by observing kernel logs for use-after-free errors related to free_netdev, especially messages from KASAN (Kernel Address Sanitizer). The provided reproducer script (repro.sh) demonstrates triggering the issue by manipulating sriov_numvfs and network interface settings. You can monitor kernel logs using commands like 'dmesg | grep free_netdev' or 'journalctl -k | grep free_netdev' to detect related errors.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version where this use-after-free vulnerability in the iavf driver has been fixed. Avoid running operations that manipulate sriov_numvfs and network interface queues in a way similar to the reproducer script until the patch is applied.