CVE-2025-38405Network attack vector

Remote denial of service via bio-integrity leak

Published Jul 25, 2025 · Updated Aug 5, 2026

Memory leak in Linux nvmet 6.10.10 and 6.11 allows remote attackers to exhaust kernel memory with metadata-bearing NVMe commands. Inline bios initialized by nvmet retain bio->bi_integrity because their completion path omits the required bio_uninit operation. An unauthenticated peer must reach an NVMe-over-RDMA target and repeatedly send protection-information I/O, eventually causing allocation failures, a hang, or a panic.

CVSS severity7.5
High
EPSS probability0.36%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Memory leak in Linux nvmet 6.10.10 and 6.11 allows remote attackers to exhaust kernel memory with metadata-bearing NVMe commands. Inline bios initialized by nvmet retain bio->bi_integrity because their completion path omits the required bio_uninit operation. An unauthenticated peer must reach an NVMe-over-RDMA target and repeatedly send protection-information I/O, eventually causing allocation failures, a hang, or a panic.

The record

CVE
CVE-2025-38405
Published
Jul 25, 2025
Updated
Aug 5, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
T1499
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jul 25, 2025CVE publishedPublication date reported by the CVE source.
  2. Aug 5, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=6.10.10 <6.11
  2. Affected versionversion=6.11
  3. Affected versionversion=64149da0fddbbfe43e11c0348d8c8b4171dae3a2
  4. Affected versionversion=bf4c89fc8797f5c0964a0c3d561fbe7e8483b62f <190f4c2c863af7cc5bb354b70e0805f06419c038
  5. Affected versionversion=bf4c89fc8797f5c0964a0c3d561fbe7e8483b62f <2e2028fcf924d1c6df017033c8d6e28b735a0508
  6. Affected versionversion=bf4c89fc8797f5c0964a0c3d561fbe7e8483b62f <431e58d56fcb5ff1f9eb630724a922e0d2a941df

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=6.10.10 <6.11; version=6.11; version=64149da0fddbbfe43e11c0348d8c8b4171dae3a2; version=bf4c89fc8797f5c0964a0c3d561fbe7e8483b62f <190f4c2c863af7cc5bb354b70e0805f06419c038; version=bf4c89fc8797f5c0964a0c3d561fbe7e8483b62f <2e2028fcf924d1c6df017033c8d6e28b735a0508; version=bf4c89fc8797f5c0964a0c3d561fbe7e8483b62f <431e58d56fcb5ff1f9eb630724a922e0d2a941df

Published CVSS scores

7.5Linux kernel CVE teamCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
5.5CanonicalCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

T1499Endpoint Denial of Service

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo