CVE-2026-72118

CVE CVE-2026-72118EUVD EUVD-2026-59076Veröffentlicht 2026-08-15T05:52:57.000ZZuletzt geändert 2026-08-19T16:36:11.000Z

Was das Advisory beschreibt

In the Linux kernel, the following vulnerability has been resolved: can: bcm: fix CAN frame rx/tx statistics KCSAN detected a data race within the bcm_rx_handler() when two CAN frames have been simultaneously received and processed in a single rx op by two different CPUs. Use atomic operations with (signed) long data types to access the statistics in the hot path to fix the KCSAN complaint. Additionally simplify the update and check of statistics overflow by using the atomic operations in separate bcm_update_[rx|tx]_stats() functions. The rx variant runs under bcm_rx_update_lock to prevent races when resetting the two rx counters; the tx variant runs under bcm_tx_lock and only needs to guard its own counter's overflow. As the rx path resets its values already at LONG_MAX / 100, there is no conflict between the two locking domains (bcm_rx_update_lock vs. bcm_tx_lock) even for ops that use both paths. The rx statistics update and the frames_filtered update in bcm_rx_changed() were previously performed in two separate bcm_rx_update_lock sections. For an rx op subscribed on all interfaces (ifindex == 0), bcm_rx_handler() can run concurrently on different CPUs, so a counter reset by one CPU between these two sections could leave frames_filtered larger than frames_abs on another CPU, producing a bogus (even negative) reduction percentage in procfs. Update the statistics in the same critical section as bcm_rx_changed() to close this gap, which also removes the now unneeded extra lock/unlock pair around the traffic_flags calculation.

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 ffd980f976e7fd666c2e61bf8ab35107efd11828 <8b2783172d92edd650de6006ebd1c800937021ab; ffd980f976e7fd666c2e61bf8ab35107efd11828 <e6c24ba95fc3f1b5e1dcd28b1c6e59ef61a9daa5; ffd980f976e7fd666c2e61bf8ab35107efd11828 <970caff5c1a63702c80e08d920256bcb5f88ecc5; 2.6.25; ffd980f976e7fd666c2e61bf8ab35107efd11828 <df47f07cdc801a6afe05a486b5a343c3e532a93c; ffd980f976e7fd666c2e61bf8ab35107efd11828 <fd75884eae40a7be47867cbfc9fc84a80bb8ddb4; patch: 6.6.148; patch: 6.18.42; patch: 6.12.101; patch: 7.2; patch: 0; patch: 5.15.216; patch: 6.1.183; patch: 5.10.265; ffd980f976e7fd666c2e61bf8ab35107efd11828 <8104bcdb2612fdda95169ddc3b49747b2ff98d24; patch: 7.1.5; ffd980f976e7fd666c2e61bf8ab35107efd11828 <47fca0d1620f2d4fab0677564989ef2b9c225c66; ffd980f976e7fd666c2e61bf8ab35107efd11828 <640acf3566fc897065127001be875ebc5401c218

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.