CVE-2026-72122

CVE CVE-2026-72122EUVD EUVD-2026-58880Published 2026-08-15T05:53:00.000ZLast changed 2026-08-17T05:40:35.000ZCVSS 7.3

What the advisory describes

In the Linux kernel, the following vulnerability has been resolved: can: bcm: fix lockless bound/ifindex race and silent RX_SETUP failure bcm_sendmsg() reads bo->ifindex and checks bo->bound before taking lock_sock(), while bcm_notify(), bcm_connect() and bcm_release() all mutate both fields under that same lock. Because the lockless reads and the locked writes are unordered with respect to each other, a racing bcm_notify() (device unregister) or bcm_connect() (concurrent bind on another thread sharing the socket) can make bcm_sendmsg() observe an inconsistent combination, e.g. a stale bound=1 together with the now-cleared ifindex=0, silently turning a socket bound to a specific CAN interface into one that also matches "any" interface. Keep the lockless bo->bound check purely as a fast-path reject, and move the ifindex read (and a bo->bound re-check) into the locked section, where every writer already serializes. This removes the possibility of observing the two fields torn against each other, rather than trying to fix it with more READ_ONCE()/WRITE_ONCE() pairs on two independently updated fields. Annotate the now-purely-lockless bo->bound accesses consistently across all its write sites. Also fix bcm_rx_setup() silently returning success when the target device disappears concurrently instead of reporting -ENODEV, so a broken RX op is no longer left registered as if it had succeeded.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

• Linux — Linux ffd980f976e7fd666c2e61bf8ab35107efd11828 <b70f1a15533afeeec5d07f20bec3f3867ab1c7b6; ffd980f976e7fd666c2e61bf8ab35107efd11828 <ffa80a2af27c97453861a5128e537214a31cd18a; patch: 6.1.178; patch: 6.6.145; patch: 5.15.212; ffd980f976e7fd666c2e61bf8ab35107efd11828 <d9b091d9d22fee81ec53fb55d2032951993ceadb; patch: 6.12.97; ffd980f976e7fd666c2e61bf8ab35107efd11828 <0f6f9f95294b4cbb26ba02209e893e3bd91237c3; 2.6.25; patch: 5.10.261; patch: 7.1.5; ffd980f976e7fd666c2e61bf8ab35107efd11828 <6bcc5cd247c2934373bc2a1cdf8bf12321169543; patch: 0; patch: 7.2; ffd980f976e7fd666c2e61bf8ab35107efd11828 <35f0ac19efb1a3f6c5e12c00e475a9ec2d9c3a6d; patch: 6.18.40; ffd980f976e7fd666c2e61bf8ab35107efd11828 <9e60c586faeaed80d55ab8ce2a4b8e56133bc395; ffd980f976e7fd666c2e61bf8ab35107efd11828 <b9c6ac6fb4e01b34575816066e5d3890a57b3c86

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

• Linux — Linux

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.