CVE-2026-97413: RDMA/rtrs-srv: Fix integer underflow in process_read and process_write
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.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.
- Fixed version: Linux Linux 24ad03bfeda05fca04c56677e57fd3d6bc3e9978, 2c52b2afded988233cd4ccc185cf5147bbc77a76, 54bf38b27afc08a0eb6b732f9c14eb8a4bcb66b5; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.
Low priority for now. Upgrade to Linux Linux 24ad03bfeda05fca04c56677e57fd3d6bc3e9978, 2c52b2afded988233cd4ccc185cf5147bbc77a76, 54bf38b27afc08a0eb6b732f9c14eb8a4bcb66b5; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes 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: RDMA/rtrs-srv: Fix integer underflow in process_read and process_write usr_len is read from a network-supplied message field (le16_to_cpu) and used to compute data_len = off - usr_len without validating that usr_len <= off. A malicious RDMA client can send usr_len > off causing an integer underflow, resulting in data_len wrapping to a huge size_t value which is then passed to the rdma_ev callback as a memory length, leading to out-of-bounds memory access. Fix by reading and validating usr_len <= off before rtrs_srv_get_ops_ids() in both process_read() and process_write(), ensuring the early return path acquires no reference and has no resource leak.
- Published
- Sep 24, 2026
- Updated
- Oct 3, 2026
- EPSS
- 0.5% · 42th percentile
- CWE
- —
Report tools
Action score
39
Monitor
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
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.
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.8affected
- 9cb837480424e78ed585376f944088246685aec3 and later · before 6b1e26e70d7ca9f0906af2283558a530eeb1f066affected · git
- 9cb837480424e78ed585376f944088246685aec3 and later · before 2c52b2afded988233cd4ccc185cf5147bbc77a76affected · git
- 9cb837480424e78ed585376f944088246685aec3 and later · before b042b4947752df0b3d16e683ac09fb4f7f0e33e0affected · git
- 9cb837480424e78ed585376f944088246685aec3 and later · before 24ad03bfeda05fca04c56677e57fd3d6bc3e9978affected · git
- 9cb837480424e78ed585376f944088246685aec3 and later · before c76e9123ab91a903396d26e6ab1b5caae5c6b149affected · git
- 9cb837480424e78ed585376f944088246685aec3 and later · before 54bf38b27afc08a0eb6b732f9c14eb8a4bcb66b5affected · git
- before 5.8not affected · semver
- 5.15.222 and later · up to and including 5.15.*not affected · semver
- 6.1.189 and later · up to and including 6.1.*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-97411Sep 24, 2026 · net: ibm: emac: mal: fix potential system hang in mal_remove()0Monitor
- ← EarlierCVE-2026-97412Sep 24, 2026 · pds_core: quiesce DMA before freeing resources0Monitor
- Later →CVE-2026-97415Sep 24, 2026 · btrfs: tree-checker: validate names in ROOT_REF and ROOT_BACKREF31Monitor
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 | 24ad03bfeda05fca04c56677e57fd3d6bc3e9978 | Vendor (CNA) |
| Linux Linux | 2c52b2afded988233cd4ccc185cf5147bbc77a76 | Vendor (CNA) |
| Linux Linux | 54bf38b27afc08a0eb6b732f9c14eb8a4bcb66b5 | Vendor (CNA) |
| Linux Linux | 6b1e26e70d7ca9f0906af2283558a530eeb1f066 | Vendor (CNA) |
| Linux Linux | b042b4947752df0b3d16e683ac09fb4f7f0e33e0 | Vendor (CNA) |
| Linux Linux | c76e9123ab91a903396d26e6ab1b5caae5c6b149 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 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).
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/2c52b2afded988233cd4ccc185cf5147bbc77a76
- git.kernel.org/stable/c/54bf38b27afc08a0eb6b732f9c14eb8a4bcb66b5
- git.kernel.org/stable/c/6b1e26e70d7ca9f0906af2283558a530eeb1f066
- git.kernel.org/stable/c/b042b4947752df0b3d16e683ac09fb4f7f0e33e0
- git.kernel.org/stable/c/c76e9123ab91a903396d26e6ab1b5caae5c6b149
Vendor advisories and official records. Exploit/PoC links are deliberately left out.