IB/isert: post the full-feature receive buffers after session registration
Summary
| CVE | CVE-2026-90293 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-09-17 17:17:26 UTC |
| Updated | 2026-09-18 18:17:52 UTC |
| Description | 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. |
Risk And Classification
Primary CVSS: v3.1 7.5 HIGH from 416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | Secondary | 7.5 | HIGH | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| 3.1 | CNA | DECLARED | 7.5 | HIGH | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
CVSS v3.1 Breakdown
Attack Vector
NetworkAttack Complexity
LowPrivileges Required
NoneUser Interaction
NoneScope
UnchangedConfidentiality
NoneIntegrity
NoneAvailability
HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected b8d26b3be8b33682cf163274ed07479a70554633 962edb9a6b0dae09d33a677485a398fc7d55968c git | Not specified |
| CNA | Linux | Linux | affected b8d26b3be8b33682cf163274ed07479a70554633 068fe9841d2585b79d479fc7b58251d02d0b066f git | Not specified |
| CNA | Linux | Linux | affected b8d26b3be8b33682cf163274ed07479a70554633 d4f8257c3283919ca7e149381d062b9af5f7df7d git | Not specified |
| CNA | Linux | Linux | affected b8d26b3be8b33682cf163274ed07479a70554633 9c21a433022219ca899d1b3cd9049991f51a6a2c git | Not specified |
| CNA | Linux | Linux | affected b8d26b3be8b33682cf163274ed07479a70554633 9b2c61344992c8c2b883e1eebe416cc488a19390 git | Not specified |
| CNA | Linux | Linux | affected b8d26b3be8b33682cf163274ed07479a70554633 6c506fee5a5f2c8719c65bcfc5e5d0862b0a1946 git | Not specified |
| CNA | Linux | Linux | affected b8d26b3be8b33682cf163274ed07479a70554633 ad4492dcaf90a1d1a728ec5eef1a68ce5355027a git | Not specified |
| CNA | Linux | Linux | affected b8d26b3be8b33682cf163274ed07479a70554633 5247dde9daac7e107853b6fea043f7f47be033f7 git | Not specified |
| CNA | Linux | Linux | affected 3.10 | Not specified |
| CNA | Linux | Linux | unaffected 3.10 semver | Not specified |
| CNA | Linux | Linux | unaffected 5.10.270 5.10.* semver | Not specified |
| CNA | Linux | Linux | unaffected 5.15.221 5.15.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.1.188 6.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.157 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.110 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.52 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2.6 7.2.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.3-rc1 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/d4f8257c3283919ca7e149381d062b9af5f7df7d | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/6c506fee5a5f2c8719c65bcfc5e5d0862b0a1946 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/5247dde9daac7e107853b6fea043f7f47be033f7 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/068fe9841d2585b79d479fc7b58251d02d0b066f | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/9c21a433022219ca899d1b3cd9049991f51a6a2c | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/962edb9a6b0dae09d33a677485a398fc7d55968c | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/ad4492dcaf90a1d1a728ec5eef1a68ce5355027a | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/9b2c61344992c8c2b883e1eebe416cc488a19390 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.