CVE-2026-89532: svcrdma: Fix pcl_for_each_segment for empty chunks
Noroxi assessment
Priority: Monitor (action score 36/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.50% (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 06d0390c37fa6714624af771bd72bbf1a7ed9bb1, 1e2e3481e39103a386b86be1c33eaef97cbdf16e, 3a78b841879c2a3243f74edc514236fb2907167f; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 06d0390c37fa6714624af771bd72bbf1a7ed9bb1, 1e2e3481e39103a386b86be1c33eaef97cbdf16e, 3a78b841879c2a3243f74edc514236fb2907167f; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1 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: Fix pcl_for_each_segment for empty chunks When a parsed chunk list contains a chunk whose ch_segcount is zero, pcl_for_each_segment computes its inclusive upper bound as &chunk->ch_segments[ch_segcount - 1]. ch_segcount is u32, so the subtraction wraps to 0xFFFFFFFF and the bound lands far past the ch_segments flex array. The loop body then walks unrelated memory at sizeof(struct svc_rdma_segment) stride until it faults. A zero-segcount chunk is reachable from the wire: xdr_check_write_chunk() only rejects segcount values greater than rc_maxpages, and pcl_alloc_write() links a freshly allocated chunk onto rc_write_pcl/rc_reply_pcl before its segment-fill loop runs, so a Write or Reply chunk advertising zero segments leaves ch_segcount == 0 on the list. When the transport has negotiated Send-With-Invalidate, svc_rdma_get_inv_rkey() iterates all four PCLs with pcl_for_each_segment and dereferences segment->rs_handle on each iteration, turning the underflow into an out-of-bounds read and a general protection fault. xdr_check_write_list / xdr_check_reply_chunk pcl_alloc_write() chunk = pcl_alloc_chunk(...) /* ch_segcount = 0 */ list_add_tail(&chunk->ch_list, &pcl->cl_chunks) /* fill loop iterates zero times for wire segcount 0 */ svc_rdma_get_inv_rkey() pcl_for_each_chunk(rc_write_pcl) pcl_for_each_segment(segment, chunk) pos <= &ch_segments[0u - 1u] /* 0xFFFFFFFF */ segment->rs_handle /* OOB read -> GPF */ Fix by switching the macro to a half-open upper bound that uses ch_segcount directly. For ch_segcount == 0 the loop start equals the loop end and the body is skipped; for ch_segcount > 0 the iteration range is unchanged. All six existing call sites in net/sunrpc/xprtrdma/svc_rdma_recvfrom.c and net/sunrpc/xprtrdma/svc_rdma_rw.c remain correct under the new bound, so no caller changes are needed.
- Published
- Sep 11, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.5% · 43th percentile
- CWE
- —
Report tools
Action score
36
Monitor
Low priority for now.
- CVSS
- 36 / 40 · 9.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 9.1
- 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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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
- 5.11affected
- 78147ca8b4a9b6cf0e597ddd6bf17959e08376c2 and later · before 1e2e3481e39103a386b86be1c33eaef97cbdf16eaffected · git
- 78147ca8b4a9b6cf0e597ddd6bf17959e08376c2 and later · before 3a78b841879c2a3243f74edc514236fb2907167faffected · git
- 78147ca8b4a9b6cf0e597ddd6bf17959e08376c2 and later · before 06d0390c37fa6714624af771bd72bbf1a7ed9bb1affected · git
- 78147ca8b4a9b6cf0e597ddd6bf17959e08376c2 and later · before 9c5a03c3dc505c0295339b0a1b9e4fe36447e482affected · git
- 78147ca8b4a9b6cf0e597ddd6bf17959e08376c2 and later · before a1c954ca4977a4e6ec73ef92fe48073ec54f9fc8affected · git
- 78147ca8b4a9b6cf0e597ddd6bf17959e08376c2 and later · before 6d33a7e6bf6c6b293a266a617201285a1ad32c56affected · git
- 78147ca8b4a9b6cf0e597ddd6bf17959e08376c2 and later · before b7713a784c59515d0aba558c8f5df6a0164dd3a9affected · git
- before 5.11not affected · semver
- 5.15.221 and later · up to and including 5.15.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-89530Sep 11, 2026 · svcrdma: Reject inline replies that overflow the pull-up buffer39Monitor
- ← EarlierCVE-2026-89531Sep 11, 2026 · svcrdma: Reject connection when transport allocation fails0Monitor
- Later →CVE-2026-89533Sep 11, 2026 · svcrdma: Fix offset arithmetic in read_chunk_range39Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 06d0390c37fa6714624af771bd72bbf1a7ed9bb1 | Vendor (CNA) |
| Linux Linux | 1e2e3481e39103a386b86be1c33eaef97cbdf16e | Vendor (CNA) |
| Linux Linux | 3a78b841879c2a3243f74edc514236fb2907167f | Vendor (CNA) |
| Linux Linux | 6d33a7e6bf6c6b293a266a617201285a1ad32c56 | Vendor (CNA) |
| Linux Linux | 9c5a03c3dc505c0295339b0a1b9e4fe36447e482 | Vendor (CNA) |
| Linux Linux | a1c954ca4977a4e6ec73ef92fe48073ec54f9fc8 | Vendor (CNA) |
| Linux Linux | b7713a784c59515d0aba558c8f5df6a0164dd3a9 | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | 6.6.157.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
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.
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 researchersFinders, 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.
- TR-26-1085 · Sep 14, 2026(Linux Kernel Güvenlik Bildirimi)
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
- none
- 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
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/1e2e3481e39103a386b86be1c33eaef97cbdf16e
- git.kernel.org/stable/c/3a78b841879c2a3243f74edc514236fb2907167f
- git.kernel.org/stable/c/6d33a7e6bf6c6b293a266a617201285a1ad32c56
- git.kernel.org/stable/c/9c5a03c3dc505c0295339b0a1b9e4fe36447e482
- git.kernel.org/stable/c/a1c954ca4977a4e6ec73ef92fe48073ec54f9fc8
- git.kernel.org/stable/c/b7713a784c59515d0aba558c8f5df6a0164dd3a9
Vendor advisories and official records. Exploit/PoC links are deliberately left out.