Skip to content
Noroxi
CVE-2026-72129· NVD / CVE Program· CNA Linux

nvmet-rdma: handle inline data with a nonzero offset

Noroxi assessment

Priority: Monitor (action score 39/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.71% (FIRST EPSS); higher than 52.7% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: Linux Linux 11401371152b228448a41d79c6de1c938f93049a, 2944113ad5fbcdf5d349d857c03d2a44b6de75b8, 42a8ea3acd883f4f210d9e54e0975b1e2292b529.

Low priority for now. Upgrade to Linux Linux 11401371152b228448a41d79c6de1c938f93049a, 2944113ad5fbcdf5d349d857c03d2a44b6de75b8, 42a8ea3acd883f4f210d9e54e0975b1e2292b529 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: nvmet-rdma: handle inline data with a nonzero offset nvmet_rdma_use_inline_sg() maps the host-controlled inline data offset into the per-command inline scatterlist. The bounds check admits any offset with off + len <= inline_data_size, but the mapping still assumes the data begins in the first inline page: sg->offset = off; sg->length = min_t(int, len, PAGE_SIZE - off); When a port is configured with inline_data_size > PAGE_SIZE (settable up to max(SZ_16K, PAGE_SIZE)), an offset in (PAGE_SIZE, inline_data_size] makes "PAGE_SIZE - off" underflow, so sg->length is set to ~4 GiB and the block backend reads far past the first inline page. num_pages(len) also ignores the offset, so an in-bounds offset whose [off, off+len) span crosses a page boundary under-counts the scatterlist. Map the offset properly: split it into a page index and an in-page offset, start the scatterlist at that page, and size the page count from page_off + len. Because the request scatterlist may now start at inline_sg[page_idx] rather than inline_sg[0], generalize the inline-SGL identity test in nvmet_rdma_release_rsp() to a range test; otherwise the persistent inline scatterlist is mistaken for an allocated one and nvmet_req_free_sgls() frees an inline page (and warns in free_large_kmalloc()).

CriticalCVSS 9.8 · v3.1—No exploit Fix available
Published
Aug 15, 2026
Updated
Oct 16, 2026
EPSS
0.7% · 52th percentile
CWE
—

Report tools

JSON

Action score

39

Monitor

Low priority for now.

CVSS
39 / 40 · 9.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.7%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
9.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-72129

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.19affected
    • 0d5ee2b2ab4f6776c361bc975c2323bc8b5cf349 and later · before c2106ba1b14d644a5203bea1a50dbe25dcad713caffected · git
    • 0d5ee2b2ab4f6776c361bc975c2323bc8b5cf349 and later · before bf8bcc1c137d54a62a428b00051fdbb13660673baffected · git
    • 0d5ee2b2ab4f6776c361bc975c2323bc8b5cf349 and later · before 11401371152b228448a41d79c6de1c938f93049aaffected · git
    • 0d5ee2b2ab4f6776c361bc975c2323bc8b5cf349 and later · before 7c96581169c9d9a7d0726e554313acfbead6141caffected · git
    • 0d5ee2b2ab4f6776c361bc975c2323bc8b5cf349 and later · before 42a8ea3acd883f4f210d9e54e0975b1e2292b529affected · git
    • 0d5ee2b2ab4f6776c361bc975c2323bc8b5cf349 and later · before 2944113ad5fbcdf5d349d857c03d2a44b6de75b8affected · git
    • 0d5ee2b2ab4f6776c361bc975c2323bc8b5cf349 and later · before 98bcdfa619150b2f41fa15bac140dbaf2584ad05affected · git
    • 0d5ee2b2ab4f6776c361bc975c2323bc8b5cf349 and later · before 48c0162f647bb47e6084ffbc71b8f213f5e2f4f8affected · git
    • before 4.19not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8bpftoolbefore 4.18.0-553.160.1.el8_104.18.0-553.160.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.160.1.el8_104.18.0-553.160.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.160.1.el8_104.18.0-553.160.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.160.1.el8_104.18.0-553.160.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.160.1.el8_104.18.0-553.160.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.160.1.el8_104.18.0-553.160.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.160.1.el8_104.18.0-553.160.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.160.1.el8_104.18.0-553.160.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.160.1.el8_104.18.0-553.160.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.160.1.el8_104.18.0-553.160.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.160.1.el8_104.18.0-553.160.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.160.1.el8_104.18.0-553.160.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.160.1.el8_104.18.0-553.160.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.160.1.el8_104.18.0-553.160.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.160.1.el8_104.18.0-553.160.1.el8_10
AlmaLinux:8kernel-rtbefore 4.18.0-553.160.1.rt7.501.el8_104.18.0-553.160.1.rt7.501.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.160.1.rt7.501.el8_104.18.0-553.160.1.rt7.501.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.160.1.rt7.501.el8_104.18.0-553.160.1.rt7.501.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.160.1.rt7.501.el8_104.18.0-553.160.1.rt7.501.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.160.1.rt7.501.el8_104.18.0-553.160.1.rt7.501.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.160.1.rt7.501.el8_104.18.0-553.160.1.rt7.501.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.160.1.rt7.501.el8_104.18.0-553.160.1.rt7.501.el8_10
AlmaLinux:8kernel-rt-develbefore 4.18.0-553.160.1.rt7.501.el8_104.18.0-553.160.1.rt7.501.el8_10
AlmaLinux:8kernel-rt-modulesbefore 4.18.0-553.160.1.rt7.501.el8_104.18.0-553.160.1.rt7.501.el8_10

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan
  • CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index
    40Plan
  • CVE-2026-72421ipv4: fib: Don't ignore error route in local/main tables.
    40Plan
  • CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler
    40Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux11401371152b228448a41d79c6de1c938f93049aVendor (CNA)
Linux Linux2944113ad5fbcdf5d349d857c03d2a44b6de75b8Vendor (CNA)
Linux Linux42a8ea3acd883f4f210d9e54e0975b1e2292b529Vendor (CNA)
Linux Linux48c0162f647bb47e6084ffbc71b8f213f5e2f4f8Vendor (CNA)
Linux Linux7c96581169c9d9a7d0726e554313acfbead6141cVendor (CNA)
Linux Linux98bcdfa619150b2f41fa15bac140dbaf2584ad05Vendor (CNA)
Linux Linuxbf8bcc1c137d54a62a428b00051fdbb13660673bVendor (CNA)
Linux Linuxc2106ba1b14d644a5203bea1a50dbe25dcad713cVendor (CNA)
almalinux:bpftool4.18.0-553.160.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-553.160.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt4.18.0-553.160.1.rt7.501.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-core4.18.0-553.160.1.rt7.501.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug4.18.0-553.160.1.rt7.501.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-core4.18.0-553.160.1.rt7.501.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-devel4.18.0-553.160.1.rt7.501.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-modules4.18.0-553.160.1.rt7.501.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-modules-extra4.18.0-553.160.1.rt7.501.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-devel4.18.0-553.160.1.rt7.501.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-modules4.18.0-553.160.1.rt7.501.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-modules-extra4.18.0-553.160.1.rt7.501.el8_10 · AlmaLinux:8Package registry (OSV)
debian:linux6.1.180-1 · Debian:12Package registry (OSV)
red hat:kernel-rt0:4.18.0-553.160.1.rt7.501.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-core0:4.18.0-553.160.1.rt7.501.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug0:4.18.0-553.160.1.rt7.501.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-core0:4.18.0-553.160.1.rt7.501.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-debuginfo0:4.18.0-553.160.1.rt7.501.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-devel0:4.18.0-553.160.1.rt7.501.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-kvm0:4.18.0-553.160.1.rt7.501.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-modules0:4.18.0-553.160.1.rt7.501.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-modules-extra0:4.18.0-553.160.1.rt7.501.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)

+5

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records