RDMA/srp: bound SRP_RSP sense copy by the received length
In the Linux kernel, the following vulnerability has been resolved: RDMA/srp: bound SRP_RSP sense copy by the received length srp_process_rsp() copies sense data from rsp->data + resp_data_len, where resp_data_len is the full 32-bit value supplied by the SRP target and is never checked against the number of bytes actually received (wc->byte_len). The copy length is bounded to SCSI_SENSE_BUFFERSIZE, so at most 96 bytes are copied, but the source offset is not bounded. A malicious or compromised SRP target on the InfiniBand/RoCE fabric that the initiator has logged into can return an SRP_RSP with SRP_RSP_FLAG_SNSVALID set and a large resp_data_len. The receive buffer is allocated at the target-chosen max_ti_iu_len, so the source of the sense copy lands past the bytes actually received; with resp_data_len near 0xFFFFFFFF it is gigabytes past the buffer and the read faults. Copy the sense data only if it has not been truncated, that is, only if the response header, the response data, and the sense region fit within the bytes actually received; otherwise drop the sense and log. The in-tree iSER and NVMe-RDMA receive paths already bound their parse by wc->byte_len; this brings ib_srp into line with them.
- Published
- Jun 25, 2026
- Updated
- Aug 5, 2026
- EPSS
- 0.5% · 42th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
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%
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.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel2.6.15 and later · before 5.10.259
- linux linux kernel5.11 and later · before 5.15.210
- linux linux kernel5.16 and later · before 6.1.176
- linux linux kernel6.2 and later · before 6.6.143
- linux linux kernel6.7 and later · before 6.12.94
- linux linux kernel6.13 and later · before 6.18.36
- linux linux kernel6.19 and later · before 7.0.13
- linux linux kernel7.1
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
- 2.6.15affected
- aef9ec39c47f0cece886ddd6b53c440321e0b2a6 and later · before 3889517c2ec7f364914aea8209abfff735f7ecdeaffected · git
- aef9ec39c47f0cece886ddd6b53c440321e0b2a6 and later · before ed77cc819ad631264787cade5ae5ec4c535ec6bbaffected · git
- aef9ec39c47f0cece886ddd6b53c440321e0b2a6 and later · before 0b9ee09d5e849591f17d98c078033dadea967293affected · git
- aef9ec39c47f0cece886ddd6b53c440321e0b2a6 and later · before 0d64bc200ebe4f275b27438c6e593903e0b16fe1affected · git
- aef9ec39c47f0cece886ddd6b53c440321e0b2a6 and later · before 2015038195939eac54a1ee83c9d98ef1a8ccbbceaffected · git
- aef9ec39c47f0cece886ddd6b53c440321e0b2a6 and later · before f92a285db7ff6e598591ccbfb551be155c5f4d57affected · git
- aef9ec39c47f0cece886ddd6b53c440321e0b2a6 and later · before 3523e53ff95f1837ec3f57ff7558532bcb2661b7affected · git
- aef9ec39c47f0cece886ddd6b53c440321e0b2a6 and later · before 13e91fd076306f5d0cdfa14f53d69e37274723c4affected · git
- before 2.6.15not 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.176-1 | 6.1.176-1 |
| Debian:13 | linux | before 6.12.94-1 | 6.12.94-1 |
| Debian:14 | linux | before 7.0.13-1 | 7.0.13-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
- CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV83Now
- CVE-2019-13272In the Linux kernel before 5.1.17, ptrace_link in kernel/ptrace.c mishandles the recording of the credentials of a process that wants to creKEV77This week
- CVE-2013-6282The (1) get_user and (2) put_user API functions in the Linux kernel before 3.5.5 on the v6k and v7 ARM platforms do not validate certain addKEV77This week
- CVE-2013-2094The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows loKEV77This week
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 | 0b9ee09d5e849591f17d98c078033dadea967293 | Vendor (CNA) |
| Linux Linux | 0d64bc200ebe4f275b27438c6e593903e0b16fe1 | Vendor (CNA) |
| Linux Linux | 13e91fd076306f5d0cdfa14f53d69e37274723c4 | Vendor (CNA) |
| Linux Linux | 2015038195939eac54a1ee83c9d98ef1a8ccbbce | Vendor (CNA) |
| Linux Linux | 3523e53ff95f1837ec3f57ff7558532bcb2661b7 | Vendor (CNA) |
| Linux Linux | 3889517c2ec7f364914aea8209abfff735f7ecde | Vendor (CNA) |
| Linux Linux | ed77cc819ad631264787cade5ae5ec4c535ec6bb | Vendor (CNA) |
| Linux Linux | f92a285db7ff6e598591ccbfb551be155c5f4d57 | Vendor (CNA) |
| debian:linux | 6.1.176-1 · 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
- 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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- git.kernel.org/stable/c/0b9ee09d5e849591f17d98c078033dadea967293
- git.kernel.org/stable/c/0d64bc200ebe4f275b27438c6e593903e0b16fe1
- git.kernel.org/stable/c/13e91fd076306f5d0cdfa14f53d69e37274723c4
- git.kernel.org/stable/c/2015038195939eac54a1ee83c9d98ef1a8ccbbce
- git.kernel.org/stable/c/3523e53ff95f1837ec3f57ff7558532bcb2661b7
- git.kernel.org/stable/c/3889517c2ec7f364914aea8209abfff735f7ecde
- git.kernel.org/stable/c/ed77cc819ad631264787cade5ae5ec4c535ec6bb
- git.kernel.org/stable/c/f92a285db7ff6e598591ccbfb551be155c5f4d57
Vendor advisories and official records. Exploit/PoC links are deliberately left out.