CVE-2026-90293

CVE CVE-2026-90293EUVD EUVD-2026-81886Veröffentlicht 2026-09-17T16:08:20.000ZZuletzt geändert 2026-09-18T17:54:23.000ZCVSS 7.5

Was das Advisory beschreibt

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.

Quelle: EUVD (ENISA), im Wortlaut der Meldung.

Produkte, die das Advisory nennt

Diese Angaben stammen aus der Meldung selbst, nicht aus einer Prüfung durch uns.

• Linux — Linux 3.10; b8d26b3be8b33682cf163274ed07479a70554633 <9b2c61344992c8c2b883e1eebe416cc488a19390; patch: 6.18.52; b8d26b3be8b33682cf163274ed07479a70554633 <5247dde9daac7e107853b6fea043f7f47be033f7; b8d26b3be8b33682cf163274ed07479a70554633 <d4f8257c3283919ca7e149381d062b9af5f7df7d; patch: 6.12.110; patch: 7.3-rc1; patch: 5.10.270; b8d26b3be8b33682cf163274ed07479a70554633 <9c21a433022219ca899d1b3cd9049991f51a6a2c; b8d26b3be8b33682cf163274ed07479a70554633 <068fe9841d2585b79d479fc7b58251d02d0b066f; patch: 6.1.188; patch: 5.15.221; patch: 7.2.6; b8d26b3be8b33682cf163274ed07479a70554633 <6c506fee5a5f2c8719c65bcfc5e5d0862b0a1946; patch: 6.6.157; b8d26b3be8b33682cf163274ed07479a70554633 <962edb9a6b0dae09d33a677485a398fc7d55968c; patch: 0; b8d26b3be8b33682cf163274ed07479a70554633 <ad4492dcaf90a1d1a728ec5eef1a68ce5355027a

Die genannten Versionen sind die Angabe der Meldung. Patchlage vergleicht keine Versionsnummern und leitet aus ihnen keine Aussage ab — welche Version installiert ist, muss ein Mensch nachsehen.

Im Produktkatalog geführt

Für diese Produkte kann ein Bestand in Patchlage erfasst werden. Ein Advisory dazu erscheint am Morgen danach im Lagebericht.

• Linux — Linux

Patchlage meldet Treffer und Verdachtsfälle. Zu allem anderen sagt dieses System nichts — weder diese Seite noch der Lagebericht behauptet je, dass ein Bestand sicher ist.