nvmet: fix memory leak of bio integrity
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.11, 6.12.37, 6.15.6
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: nvmet: fix memory leak of bio integrity If nvmet receives commands with metadata there is a continuous memory leak of kmalloc-128 slab or more precisely bio->bi_integrity. Since commit bf4c89fc8797 ("block: don't call bio_uninit from bio_endio") each user of bio_init has to use bio_uninit as well. Otherwise the bio integrity is not getting free. Nvmet uses bio_init for inline bios. Uninit the inline bio to complete deallocation of integrity in bio.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From bf4c89fc8797f5c0964a0c3d561fbe7e8483b62f · fixed in 431e58d56fcb5ff1f9eb630724a922e0d2a941df; From bf4c89fc8797f5c0964a0c3d561fbe7e8483b62f · fixed in 2e2028fcf924d1c6df017033c8d6e28b735a0508; From bf4c89fc8797f5c0964a0c3d561fbe7e8483b62f · fixed in 190f4c2c863af7cc5bb354b70e0805f06419c038; From 6.10.10 · fixed in 6.11
- Linux Linux
6.11
- KernelLinux
From 6.11.0 · fixed in 6.12.37; From 6.13.0 · fixed in 6.15.6