CVE-2025-38417
BaseFortify
Publication date: 2025-07-25
Last updated on: 2025-11-19
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-401 | The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse. |
Attack-Flow Graph
AI Powered Q&A
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version where the ice driver memory leak in the eswitch reset scenario is fixed. Until then, avoid triggering VF reset procedures unnecessarily and monitor for memory leaks using kmemleak or similar tools.
How can this vulnerability impact me? :
The memory leak can cause increased memory usage over time, potentially leading to system instability or degraded performance, especially on systems using the ice driver with virtual functions and eswitch features. This could affect network functionality and reliability during device reset operations.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by observing memory leaks related to the ice driver during VF reset scenarios. You can test it by creating at least one VF and triggering a reset on the physical function (PF) network device. Suggested commands are: - Create a VF: echo 1 > /sys/class/net/ethX/device/sriov_numvfs - Trigger the reset: echo 1 > /sys/class/net/ethX/device/reset Replace ethX with your PF network device name.
Can you explain this vulnerability to me?
This vulnerability is a memory leak in the Linux kernel's ice driver related to the eswitch code during a reset scenario. Specifically, when the device is in legacy mode, memory for port representor structures was allocated unnecessarily and not freed, causing a memory leak. The fix involves adding a mode checker to allocate memory only in switchdev mode and properly free it in legacy mode.