All vulnerabilities

Servers and applications

CVE-2026-99672

can: protect the receive lists with a per-device lock

Severity
Unrated
Published
20 Nov 2026
Last changed
20 Nov 2026
Added to UpHeron
20 Nov 2026
Fixed in
6.12.118, 6.18.64, 7.3.5
Sources
CVE Program

Description

In the Linux kernel, the following vulnerability has been resolved:

The receive lists of a CAN device are located in the device's can_ml_priv and travel with the device when it is moved to another network namespace. But they are protected by the per-netns rcvlists_lock. So can_rx_unregister() needs dev_net(dev) to pick the right lock and silently returns when the passed namespace does not match dev_net(dev) anymore.

isotp_release() and bcm_release() leave their notifier list before they take any lock that serializes against the netdev notifier, which runs under RTNL. When the bound device is moved to another namespace in this window, the notifier skips the socket and the release path has to remove the filters itself. isotp_release() passes the socket's namespace, which does not match dev_net(dev) anymore. bcm_rx_unreg() passes dev_net(dev), which can_rx_unregister() reads again for its check, so a namespace change between both reads makes the check fail as well.

From the CVE Program. Shortened; the full text is there.

Affected software

SoftwareAffected versions
Linux kernelServers and applications · cna:linux|linux
  • From 4.12 before 6.12.118
  • From 6.13 before 6.18.64
  • From 6.19 before 7.3.5

About Linux kernel

Unix-like operating system kernel, basis for all Linux operating systems

From Wikidata, CC0 1.0.
GitHub stars
255,726GitHub, 15 Nov 2026
Forks
67,394GitHub, 15 Nov 2026
Developer
Linus TorvaldsWikidata
License
GNU General Public License, version 2.0Wikidata
Written in
CWikidata
First released
25 Aug 1991Wikidata
First published on GitHub
4 Sept 2011GitHub

References

  • CVE.org https://www.cve.org/CVERecord?id=CVE-2026-99672