VDB

CVE-2026-72124

CVE-2026-72124 PUBLISHED CVSS 8.8 HIGH

can: isotp: serialize TX state transitions under so->rx_lock

Reported by linux · Published August 15, 2026

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.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
LinuxLinuxcf070fe33bfbd1a4c21236078fadb35dd223a157, bbedeb67a9a684f2fb78c55bd3662c400526715e, a7d90e7b5e75d7406c889fe36e9a61ee364a00cb, 6da8119e8dd542194103139812d1a4b7dcd1aedd, 5.10, 4f1fdf1a1c317bcac0c6b6c8e12642c9983de1ca, 37beb16e08cae94cc05840c7274225e3b0b38ae7, 377a8f500704da42ed86a4541ed930e9dcfdb2ea, 0b05eca9589f609e2491b528dccf683168a4cda8

Risk scores

CVSS 3.1
8.8
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

VendorProductVersions
LinuxLinuxe057dd3fc20ffb3d7f150af46542a51b59b90127, e057dd3fc20ffb3d7f150af46542a51b59b90127, e057dd3fc20ffb3d7f150af46542a51b59b90127
LinuxLinux5.10, 0, 5.10.265
LinuxLinux6.1.183, 0, 6.6.148
linuxlinux_kernel5.10, 5.10, 5.10

Timeline

  • Aug 15, 2026 Coalition ESS Score
  • Aug 15, 2026 CVE Published
  • Aug 19, 2026 Security Advisory
  • Aug 24, 2026 EPSS Score (30 in total, the first dated here)
  • Oct 16, 2026 CVE Updated

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2026-72124
vulnetix vdb fixes CVE-2026-72124

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-72124/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›