CVE-2026-72124

CVE CVE-2026-72124EUVD EUVD-2026-58882Veröffentlicht 2026-08-15T05:53:02.000ZZuletzt geändert 2026-08-19T16:36:21.000ZCVSS 8.8

Was das Advisory beschreibt

In the Linux kernel, the following vulnerability has been resolved: can: isotp: serialize TX state transitions under so->rx_lock The TX state machine (so->tx.state) is driven from three contexts: sendmsg() claiming and progressing a transfer, the RX path consuming Flow Control/echo frames, and two hrtimers timing out a stalled transfer. Mixing a lock-free cmpxchg() claim in sendmsg() with hrtimer_cancel() calls made under so->rx_lock elsewhere left windows where a frame or timer callback could act on a state that had already moved on, corrupting an unrelated transfer. so->rx_lock now covers the full lifecycle of a TX claim: sendmsg() takes it to check so->tx.state is ISOTP_IDLE, switch it to ISOTP_SENDING, bump so->tx_gen and drain the previous transfer's timers - all as one critical section. isotp_rcv_fc()/isotp_rcv_cf() already run under this lock via isotp_rcv(), and isotp_rcv_echo() now takes it itself, so none of them can ever observe a transfer mid-claim. This also means a transfer can no longer be handed to sendmsg()'s cleanup paths (signal or send error) while another thread is concurrently claiming or finishing it, so those paths can cancel timers and reset the state unconditionally. isotp_release() claims the socket the same way, so a racing sendmsg() sees a consistent ISOTP_SHUTDOWN and skips arming its timer or sending. Only the hrtimer callbacks stay outside so->rx_lock, since they run under so->rx_lock's cancellation elsewhere and taking it themselves would deadlock. so->tx_gen lets them recognize whether the transfer they timed out is still the one currently active, so they don't report an error against a transfer that has since completed or been superseded.

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 patch: 7.2; patch: 5.10.265; 5.10; e057dd3fc20ffb3d7f150af46542a51b59b90127 <6da8119e8dd542194103139812d1a4b7dcd1aedd; e057dd3fc20ffb3d7f150af46542a51b59b90127 <37beb16e08cae94cc05840c7274225e3b0b38ae7; e057dd3fc20ffb3d7f150af46542a51b59b90127 <0b05eca9589f609e2491b528dccf683168a4cda8; e057dd3fc20ffb3d7f150af46542a51b59b90127 <cf070fe33bfbd1a4c21236078fadb35dd223a157; e057dd3fc20ffb3d7f150af46542a51b59b90127 <bbedeb67a9a684f2fb78c55bd3662c400526715e; patch: 6.1.183; patch: 6.6.148; patch: 6.18.40; patch: 5.15.216; patch: 0; patch: 7.1.5; e057dd3fc20ffb3d7f150af46542a51b59b90127 <377a8f500704da42ed86a4541ed930e9dcfdb2ea; e057dd3fc20ffb3d7f150af46542a51b59b90127 <4f1fdf1a1c317bcac0c6b6c8e12642c9983de1ca; e057dd3fc20ffb3d7f150af46542a51b59b90127 <a7d90e7b5e75d7406c889fe36e9a61ee364a00cb; patch: 6.12.101

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.