IB/isert: post the full-feature receive buffers after session registration
Noroxi assessment
Priority: Monitor (action score 30/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.68% (FIRST EPSS); higher than 51.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.
- Fixed version: Linux Linux 068fe9841d2585b79d479fc7b58251d02d0b066f, 5247dde9daac7e107853b6fea043f7f47be033f7, 6c506fee5a5f2c8719c65bcfc5e5d0862b0a1946.
Low priority for now. Upgrade to Linux Linux 068fe9841d2585b79d479fc7b58251d02d0b066f, 5247dde9daac7e107853b6fea043f7f47be033f7, 6c506fee5a5f2c8719c65bcfc5e5d0862b0a1946 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: IB/isert: post the full-feature receive buffers after session registration isert_put_login_tx() posts the full-feature receive buffers before __transport_register_session() runs, so an initiator that does not wait for the final Login Response can still have a SCSI command executed against an se_session whose se_tpg is NULL - the same oops as the previous patch, at target_submit+0xbe. Post them from isert_get_rx_pdu(), which the previous patch already uses to send that response, and post them before that send: the receive queue is filled at the moment the initiator is told it may use it. Allocating there keeps the existing property that a memory allocation failure cannot happen once the final Login Response is on the wire. The receive queue is already empty between the final Login Request and isert_post_recvm(); this moves the second point later, from a median of 92 us to 172 us over 1200 logins. Only an initiator that sends before it has been told to can reach that window, and on IB and RoCE its send is retried there until the buffers appear - isert_rdma_accept() asks for rnr_retry_count = 7. iWARP has no RNR flow control, so there the same send terminates the connection instead. Measured over rxe, 400 login cycles per run, with an initiator that does not wait: an instrumented build counted no entries to isert_recv_done() before the buffers are posted in 10 runs, where that initiator oopsed 8 of 10 unpatched runs and 5 of 10 with only the previous patch. Not tested: iWARP, discovery sessions over iSER, and real HCAs.
- Published
- Sep 17, 2026
- Updated
- Sep 18, 2026
- EPSS
- 0.6% · 51th percentile
- CWE
- —
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.5
- 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
- 3.10affected
- b8d26b3be8b33682cf163274ed07479a70554633 and later · before 962edb9a6b0dae09d33a677485a398fc7d55968caffected · git
- b8d26b3be8b33682cf163274ed07479a70554633 and later · before 068fe9841d2585b79d479fc7b58251d02d0b066faffected · git
- b8d26b3be8b33682cf163274ed07479a70554633 and later · before d4f8257c3283919ca7e149381d062b9af5f7df7daffected · git
- b8d26b3be8b33682cf163274ed07479a70554633 and later · before 9c21a433022219ca899d1b3cd9049991f51a6a2caffected · git
- b8d26b3be8b33682cf163274ed07479a70554633 and later · before 9b2c61344992c8c2b883e1eebe416cc488a19390affected · git
- b8d26b3be8b33682cf163274ed07479a70554633 and later · before 6c506fee5a5f2c8719c65bcfc5e5d0862b0a1946affected · git
- b8d26b3be8b33682cf163274ed07479a70554633 and later · before ad4492dcaf90a1d1a728ec5eef1a68ce5355027aaffected · git
- b8d26b3be8b33682cf163274ed07479a70554633 and later · before 5247dde9daac7e107853b6fea043f7f47be033f7affected · git
- before 3.10not 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-90291Sep 17, 2026 · module/dups: Fix use-after-free in kmod_dup_req lifetime handling31Monitor
- ← EarlierCVE-2026-90292Sep 17, 2026 · RDMA/siw: Fix use-after-free in siw_accept()31Monitor
- Later →CVE-2026-90294Sep 17, 2026 · IB/isert: delay the final Login Response until the session is registered30Monitor
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 | 068fe9841d2585b79d479fc7b58251d02d0b066f | Vendor (CNA) |
| Linux Linux | 5247dde9daac7e107853b6fea043f7f47be033f7 | Vendor (CNA) |
| Linux Linux | 6c506fee5a5f2c8719c65bcfc5e5d0862b0a1946 | Vendor (CNA) |
| Linux Linux | 962edb9a6b0dae09d33a677485a398fc7d55968c | Vendor (CNA) |
| Linux Linux | 9b2c61344992c8c2b883e1eebe416cc488a19390 | Vendor (CNA) |
| Linux Linux | 9c21a433022219ca899d1b3cd9049991f51a6a2c | Vendor (CNA) |
| Linux Linux | ad4492dcaf90a1d1a728ec5eef1a68ce5355027a | Vendor (CNA) |
| Linux Linux | d4f8257c3283919ca7e149381d062b9af5f7df7d | Vendor (CNA) |
| 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
- none
- 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
- None
- 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:N/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
Show all references (7 more)Show less
- git.kernel.org/stable/c/5247dde9daac7e107853b6fea043f7f47be033f7
- git.kernel.org/stable/c/6c506fee5a5f2c8719c65bcfc5e5d0862b0a1946
- git.kernel.org/stable/c/962edb9a6b0dae09d33a677485a398fc7d55968c
- git.kernel.org/stable/c/9b2c61344992c8c2b883e1eebe416cc488a19390
- git.kernel.org/stable/c/9c21a433022219ca899d1b3cd9049991f51a6a2c
- git.kernel.org/stable/c/ad4492dcaf90a1d1a728ec5eef1a68ce5355027a
- git.kernel.org/stable/c/d4f8257c3283919ca7e149381d062b9af5f7df7d
Vendor advisories and official records. Exploit/PoC links are deliberately left out.