CVE-2026-99672
can: protect the receive lists with a per-device lock
No exploitation reported by the sources we read.
- Published2026-11-20
- Fixed in7.3.5 · 6.18.64 · 6.12.118
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
In the Linux kernel, the following vulnerability has been resolved: can: protect the receive lists with a per-device lock 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. In both cases can_rx_unregister() silently returns. As can_rx_register() stores rcv->sk without a reference, the remaining receivers point to the freed socket (isotp) or the freed op (bcm): BUG: KASAN: use-after-free in isotp_rcv+0x1570/0x24d0 Read of size 1 at addr ffff888118130552 by task isotp_ns_uaf/578 can_rcv_filter+0x4af/0x8c0 can_receive+0x28d/0x3c0 can_rcv+0x2a9/0x310 __netif_receive_skb_one_core+0x21a/0x260 process_backlog+0x210/0x760 Besides this, the lists of a device are protected by the rcvlists_lock of the namespace that is passed in. Callers which pass dev_net(dev) read it at different times, so the same lists may be modified under the locks of different namespaces while the device is moved. Taking RTNL in these release paths is no option: raw_bind(), raw_setsockopt() and raw_release() already hold RTNL while adding and removing up to CAN_RAW_FILTER_MAX filters per socket, which unprivileged users can trigger repeatedly and which makes RTNL a global bottleneck. Instead fix the root cause and add a spinlock to struct can_dev_rcv_lists, which protects the receive lists of a CAN device or the 'any' CAN device lists of a namespace. It is initialized in can_set_ml_priv(), which is used by all CAN network devices. With this, can_rx_unregister() finds the subscription independently of the current namespace of the device. The protocols keep the device valid with their tracked references. The per-netns rcvlists_lock only protects the receive list statistics anymore, and CAN_RAW, CAN_BCM and CAN_ISOTP pass the namespace that has been used for can_rx_register(). So isotp_release() and bcm_release() now remove their filters correctly without RTNL, and raw_release(), raw_setsockopt(), raw_bind() and isotp_bind() do not need RTNL anymore and add and remove their filters under lock_sock(). To serialize bind() with NETDEV_UNREGISTER, bind() publishes the device inside the RCU section of its lookup, and raw_notify() and isotp_notify() recheck the bound device under lock_sock(). As RTNL does not keep NETDEV_DOWN out of bind() anymore, bind() checks IFF_UP after publishing the bound device, with a barrier pair against raw_notify() and isotp_notify(), so a down transition during bind() is still reported with ENETDOWN.
Timeline
dates in UTC- 2026-11-2005:50CVE publishedCNA
Versions per branch
OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 7.3 | ≥ 6.19.0, < 7.3.5 | 7.3.5 | OSV |
| 6.x | ≥ 6.13.0, < 6.18.64 | 6.18.64 | OSV |
| 6.12 | ≥ 4.12.0, < 6.12.118 | 6.12.118 | OSV |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Products declared by the CNA2 products
As Linux, the CNA that assigned this CVE, declared them in the CVE record; versions as written.
- Linuxother versions: not affected
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected- ≥ 8e8cda6d737d356054c9eeef642aec0e8ae7e6bc, < 59d91f555ada337458c48316987b8ef46487f885fixed in 59d91f555ada337458c48316987b8ef46487f885git
- ≥ 8e8cda6d737d356054c9eeef642aec0e8ae7e6bc, < 4b625dde57c0a40a933bf017ff93a64a7306aa43fixed in 4b625dde57c0a40a933bf017ff93a64a7306aa43git
- ≥ 8e8cda6d737d356054c9eeef642aec0e8ae7e6bc, < 228e795ec650c33ebbce8ba81ce983c84d64d889fixed in 228e795ec650c33ebbce8ba81ce983c84d64d889git
- ≥ 8e8cda6d737d356054c9eeef642aec0e8ae7e6bc, < 0f3ad9ab40e3dad06d5c0693806e07935ceedbc3fixed in 0f3ad9ab40e3dad06d5c0693806e07935ceedbc3git
- Linuxother versions: affected
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected- = 4.12no fix stated
Not affected < 4.12 · ≥ 6.12.118, ≤ 6.12.* · ≥ 6.18.64, ≤ 6.18.* · ≥ 7.3.5, ≤ 7.3.* · ≥ 7.4-rc2
Source: the CNA record (CVE Program), © The MITRE Corporation,CVE terms of useCVE recordupdated 2026-11-20
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Packages
- kernelAzure Linux:3all versions · no fixed version listed
- linuxDebian:14all versions · no fixed version listed
- linuxDebian:13all versions · fixed in 6.12.118-1
- linuxDebian:12all versions · no fixed version listed
- linux-ltsAlpaquita:streamfrom 6.18.62-r0 · fixed in 6.18.64-r0
- linux-ltsAlpaquita:25from 6.12.115-r0 · no fixed version listed
- linux-ltsAlpaquita:23from 6.1.191-r1 · no fixed version listed
Vendor advisories
kernel: kernel: Denial of service via use-after-free in CAN subsystem during namespace migration
kernel.src as a component of Red Hat Enterprise Linux 10 · kernel as a component of Red Hat Enterprise Linux 6 · kernel-abi-whitelists as a component of Red Hat Enterprise Linux 6 · +173 more
Fix
- Update Linux kernel to 7.3.5 · 6.18.64 · 6.12.118
- No fix available, says the vendor Red Hat Product Security CVE-2026-99672 · 162 productsFix deferred
- No fix planned, says the vendor Red Hat Product Security CVE-2026-99672 · 14 productsOut of support scope
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Metasploit modules
- none listed Metasploit Framework
Sources
- NVDCVE recordread 2026-11-22
- CNACVSS 3.17.82026-11-22
- FIRST EPSSEPSS score0.2 %2026-11-21
- OSVaffected packages—
- GitHub Advisoriesadvisory—
Identifiers
- AZL-115486same flawAzure Linux · MIT
- EUVD-2026-130965same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-4ghg-qw9q-9mgpsame flawGitHub Advisory Database · CC-BY-4.0
- DSA-6652-1advisory covering several CVEsDebian · LicenseRef-unstated
Technical details
- CVSS v3 vector
- CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Published
- 2026-11-20
- Last modified
- 2026-11-22
- NVD status
- Received
- GitHub advisory
- GHSA-4ghg-qw9q-9mgp
Frequently asked questions
What is CVE-2026-99672?
Is CVE-2026-99672 actively exploited?
What is the CVSS score for CVE-2026-99672?
Running Linux kernel? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website checks · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-4ghg-qw9q-9mgp
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- OSV.dev · Per record, as its publisher states it: each row carries the label in sourceLicense when one is served
- Red Hat Product Security (CSAF and VEX) · CC-BY-4.0