CVE-2025-38109
BaseFortify
Publication date: 2025-07-03
Last updated on: 2025-11-20
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) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
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 (UAF) issue in the Linux kernel's mlx5 driver related to the embedded chip virtual function (ECVF) on BlueField devices. Specifically, during the shutdown flow, when a virtual function is created on the ECVF, the vport ACL ingress table is not properly destroyed, leading to a refcount underflow and a use-after-free condition.
How can this vulnerability impact me? :
The vulnerability can cause kernel instability or crashes during device shutdown due to the use-after-free error. This may lead to system reliability issues or denial of service on affected systems using BlueField devices with the mlx5 driver.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring the kernel logs for specific error messages related to the mlx5_core module. Look for log entries indicating a refcount underflow or use-after-free errors during shutdown, such as: 'refcount_t: underflow; use-after-free.' and call traces involving mlx5_core functions. You can use the command 'dmesg | grep mlx5_core' or 'journalctl -k | grep mlx5_core' to check for these messages in the kernel logs.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version where this vulnerability is fixed, as the issue is resolved by correcting the shutdown flow for ECVF vports on BlueField devices. Until an update is applied, avoid creating virtual functions on the embedded chip (ECVF) of BlueField devices or disable the affected mlx5_eswitch functionality if possible to prevent triggering the use-after-free condition during shutdown.