Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-89530: svcrdma: Reject inline replies that overflow the pull-up buffer

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.49% (FIRST EPSS).
  • 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 0fbe20dfe74b783d255bf389a6ea77aa25dc7860, 1949dd1576f7a8aa161b1330c6125df9d53046d5, 4.20.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 0fbe20dfe74b783d255bf389a6ea77aa25dc7860, 1949dd1576f7a8aa161b1330c6125df9d53046d5, 4.20 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: svcrdma: Reject inline replies that overflow the pull-up buffer An RPC-over-RDMA client can request a reply, such as an NFS READ payload, without providing a Write list or a Reply chunk to carry it. When such a reply needs more scatter/gather entries than the device's Send Queue supports, svc_rdma_pull_up_needed() selects pull-up and svc_rdma_pull_up_reply_msg() linearizes the whole reply into sctxt->sc_xprt_buf. That buffer is only sc_max_req_size bytes, while the reply on this path is bounded only by the client's request, so svc_rdma_xb_linearize() copies past the end of the buffer and corrupts adjacent slab memory. The oversized length is then stored in sc_sges[0].length and posted, so the device also reads beyond the mapped region. The SGE-exhaustion branch is the only pull-up path that can exceed the buffer: the threshold branch pulls up only replies smaller than RPCRDMA_PULLUP_THRESH, and replies that fit the device's SGE budget are sent directly without linearization. Make svc_rdma_pull_up_needed() report -E2BIG when the reply it would pull up cannot fit sc_max_req_size, and fail the request with ERR_CHUNK as RFC 8166 Section 4.5.3 directs rather than dropping the connection. The helper no longer answers a simple yes/no question: it now reports pull-up, no pull-up, or -E2BIG for a reply too large to linearize. Rename svc_rdma_pull_up_needed() to svc_rdma_check_pull_up() so its name no longer implies a boolean predicate.

CriticalCVSS 9.8 · v3.1—No exploit Fix available
Published
Sep 11, 2026
Updated
Oct 30, 2026
EPSS
0.4% · 42th 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.4%

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-89530

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.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

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

    • 9b65b18f817d9ada2bf67351f24bdcce6789a0bb, d564356e1919d1178568c19af410cfc1a9076663, 5.0affected
    • e248aa7be86e8179f20ac0931774ecd746f3f5bf and later · before b73011049dbe909f73fd9620d94ef1757d7af2ebaffected · git
    • e248aa7be86e8179f20ac0931774ecd746f3f5bf and later · before 8068358f445a11296328ffa7c524701596814a17affected · git
    • e248aa7be86e8179f20ac0931774ecd746f3f5bf and later · before fcd91b9957462d398792201c239dffaeff1cc8b2affected · git
    • e248aa7be86e8179f20ac0931774ecd746f3f5bf and later · before 1949dd1576f7a8aa161b1330c6125df9d53046d5affected · git
    • e248aa7be86e8179f20ac0931774ecd746f3f5bf and later · before 8ec60eb51fae37cd3d334ff26e4a7d6fb21ff7cfaffected · git
    • e248aa7be86e8179f20ac0931774ecd746f3f5bf and later · before 0fbe20dfe74b783d255bf389a6ea77aa25dc7860affected · git
    • 4.19.22 and later · before 4.20affected · semver
    • 4.20.9 and later · before 4.21affected · semver
    • before 5.0not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2

+96

Same product

linux: all records

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

Published before and after this one in the same product

  • ← EarlierCVE-2026-89528Sep 11, 2026 · svcrdma: Reject Read lists that exceed the page budget
    30Monitor
  • ← EarlierCVE-2026-89529Sep 11, 2026 · svcrdma: Reject oversized Read segments at decode time
    0Monitor
  • Later →CVE-2026-89531Sep 11, 2026 · svcrdma: Reject connection when transport allocation fails
    0Monitor

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 Linux0fbe20dfe74b783d255bf389a6ea77aa25dc7860Vendor (CNA)
Linux Linux1949dd1576f7a8aa161b1330c6125df9d53046d5Vendor (CNA)
Linux Linux4.20Vendor (CNA)
Linux Linux4.21Vendor (CNA)
Linux Linux8068358f445a11296328ffa7c524701596814a17Vendor (CNA)
Linux Linux8ec60eb51fae37cd3d334ff26e4a7d6fb21ff7cfVendor (CNA)
Linux Linuxb73011049dbe909f73fd9620d94ef1757d7af2ebVendor (CNA)
Linux Linuxfcd91b9957462d398792201c239dffaeff1cc8b2Vendor (CNA)
almalinux:bpftool4.18.0-553.172.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-553.172.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-abi-stablelists4.18.0-553.172.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-core4.18.0-553.172.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-cross-headers4.18.0-553.172.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug4.18.0-553.172.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-core4.18.0-553.172.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-devel4.18.0-553.172.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules4.18.0-553.172.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules-extra4.18.0-553.172.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-devel4.18.0-553.172.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-doc4.18.0-553.172.1.el8_10 · AlmaLinux:8Package registry (OSV)
debian:linux6.12.111-1 · Debian:13Package registry (OSV)
debian:linux-6.126.12.111-1~deb12u1 · Debian:12Package registry (OSV)
red hat:bpftool0:4.18.0-553.172.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:bpftool-debuginfo0:4.18.0-553.172.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel0:4.18.0-553.172.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-abi-stablelists0:4.18.0-553.172.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-core0:4.18.0-553.172.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug0:4.18.0-553.172.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-core0:4.18.0-553.172.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-debuginfo0:4.18.0-553.172.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)

+6

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.

Credits

All researchers

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).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

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

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records