Bug 2383399 (CVE-2025-38405) - CVE-2025-38405 kernel: nvmet: fix memory leak of bio integrity
Summary: CVE-2025-38405 kernel: nvmet: fix memory leak of bio integrity
Keywords:
Status: NEW
Alias: CVE-2025-38405
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-07-25 14:02 UTC by OSIDB Bzimport
Modified: 2026-06-29 18:25 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:18134 0 None None None 2026-05-19 08:35:33 UTC
Red Hat Product Errata RHSA-2026:18587 0 None None None 2026-05-19 12:49:11 UTC

Description OSIDB Bzimport 2025-07-25 14:02:34 UTC 
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.
Comment 1 Jon Moroney 2025-07-25 19:24:28 UTC 
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025072511-CVE-2025-38405-014e@gregkh/T
Comment 6 errata-xmlrpc 2026-05-19 08:35:32 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2026:18134 https://access.redhat.com/errata/RHSA-2026:18134
Comment 7 errata-xmlrpc 2026-05-19 12:49:10 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:18587 https://access.redhat.com/errata/RHSA-2026:18587
Note You need to log in before you can comment on or make changes to this bug.