CVE-2023-53659
BaseFortify
Publication date: 2025-10-07
Last updated on: 2026-02-03
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 5.16 |
| linux | linux_kernel | 6.5 |
| linux | linux_kernel | From 6.2 (inc) to 6.4.7 (inc) |
| intel | i40e | * |
| intel | iavf | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-125 | The product reads data past the end, or before the beginning, of the intended buffer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is an out-of-bounds (OOB) error in the Linux kernel's iavf driver. It occurs when the number of channels set during the removal of a device (iavf_remove) is greater than the allocated transmit/receive rings. If a reset operation times out, the system incorrectly updates the number of active queues, leading to an out-of-bounds memory access. This can cause kernel errors and instability.
How can this vulnerability impact me? :
The vulnerability can lead to kernel memory corruption due to out-of-bounds access, which may cause system crashes, instability, or unexpected behavior in the Linux kernel networking stack. This can affect the reliability and availability of systems using the affected iavf driver.
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 out-of-bounds errors related to the iavf driver, such as KASAN slab-out-of-bounds messages during device removal. The provided reproducer script uses commands like 'cat repro.sh' to run a test that triggers the issue by setting sriov_numvfs and changing channel settings with 'ethtool -L'. Monitoring dmesg or kernel logs for messages similar to 'BUG: KASAN: slab-out-of-bounds in iavf_free_all_tx_resources' can indicate the presence of the vulnerability.
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation involves avoiding the conditions that trigger the out-of-bounds error, such as not setting the number of virtual functions (sriov_numvfs) to a value greater than the allocated tx/rx rings and avoiding rapid changes to channel settings on the affected iavf device. Applying the patch that fixes the out-of-bounds issue in the iavf_remove() function in the Linux kernel is the definitive fix.