CVE-2025-38405
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 | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | 6.16 |
| 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
Can you explain this vulnerability to me?
This vulnerability is a memory leak in the Linux kernel's nvmet subsystem. When nvmet receives commands with metadata, it causes a continuous memory leak related to the bio integrity structure (bio->bi_integrity). This happens because after a certain kernel commit, each use of bio_init must be paired with bio_uninit to properly free bio integrity memory. Nvmet was not calling bio_uninit for inline bios, leading to the leak.
How can this vulnerability impact me? :
The memory leak can cause increased memory usage over time, potentially leading to system instability or crashes if the leaked memory accumulates significantly. This can degrade system performance and reliability, especially on systems heavily using nvmet with metadata commands.