Skip to main content
Mallory
CriticalVulnerability

CVE-2026-72129: Out-of-bounds read in Linux kernel NVMe-over-RDMA inline-data handling

Published Aug 15, 2026 · Updated 11 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS9.8Critical · v3.1
EPSS0.71%54th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Linux
IdentifiersCVE-2026-72129CWE-125

CVE-2026-72129 is a memory-safety vulnerability in the Linux kernel NVMe-over-RDMA target implementation. The nvmet_rdma_use_inline_sg() function incorrectly maps a host-controlled inline-data offset into a per-command scatterlist. Although validation requires off + len <= inline_data_size, mapping assumes the data starts in the first inline page. When inline_data_size exceeds PAGE_SIZE, an accepted offset beyond the first page causes PAGE_SIZE - off to underflow, producing a scatterlist length of approximately 4 GiB and allowing the block backend to read beyond the inline buffer. The page-count calculation also ignores the starting offset, under-counting scatterlist entries when the requested span crosses a page boundary. These errors can cause kernel memory over-reads, data corruption, and system crashes.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Malformed NVMe-over-RDMA inline-data requests can trigger out-of-bounds kernel memory reads, potentially exposing kernel memory, corrupting data written to backing storage, or crashing the target system. CVE-specific assessments assign high confidentiality, integrity, and availability impacts. Arbitrary code execution has not been demonstrated in the available technical details, and no known exploits are identified.

Mitigation

If you can’t patch tonight, do this now.

Until patching is complete, disable NVMe-over-RDMA target functionality where unnecessary. For required targets, restrict connectivity to trusted initiators and isolate storage networks. Prioritize ports configured with inline_data_size greater than PAGE_SIZE. Reducing inline_data_size alone should not be considered a complete workaround because the offset-dependent page-counting defect is separate. No explicit vendor-approved workaround is identified.

Remediation

Patch, then assume compromise.

Install the vendor-provided kernel update for the exact distribution, release, architecture, and kernel flavor, then reboot into the patched kernel. The fix must split the inline offset into a page index and an in-page offset, start the scatterlist at the correct page, and calculate the page count using page_off + len. It must also update nvmet_rdma_release_rsp() to recognize scatterlists anywhere within the persistent inline_sg range; otherwise, cleanup can incorrectly free an inline page. For RHEL 8.10, RHSA-2026:66000 supplies kernel release 4.18.0-553.160.1.el8_10. Other distributions require their corresponding security updates. SUSE builds marked as undergoing QA should not be assumed publicly available.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
LinuxLinux Kerneloperating_system
FAQ

Frequently asked questions

Is CVE-2026-72129 exploited in the wild?
As of Nov 6, 2026, Mallory has no reports of CVE-2026-72129 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-72129?
As of Nov 6, 2026, Mallory has found no public exploit for CVE-2026-72129.
Is there a patch for CVE-2026-72129?
Install the vendor-provided kernel update for the exact distribution, release, architecture, and kernel flavor, then reboot into the patched kernel. The fix must split the inline offset into a page index and an in-page offset, start the scatterlist at the correct page, and calculate the page count using page_off + len.
What products are affected by CVE-2026-72129?
Linux Kernel.
How severe is CVE-2026-72129?
CVE-2026-72129 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 0.71% (54th percentile) as of Nov 6, 2026.
Activity feed

Recent activity

27 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+16 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.