CVE-2026-99672 (GCVE-0-2026-99672)
Vulnerability from cvelistv5 – Published: 2026-11-20 05:50 – Updated: 2026-11-20 05:50| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Linux | Linux |
Affected:
8e8cda6d737d356054c9eeef642aec0e8ae7e6bc , < 59d91f555ada337458c48316987b8ef46487f885
(git)
Affected: 8e8cda6d737d356054c9eeef642aec0e8ae7e6bc , < 4b625dde57c0a40a933bf017ff93a64a7306aa43 (git) Affected: 8e8cda6d737d356054c9eeef642aec0e8ae7e6bc , < 228e795ec650c33ebbce8ba81ce983c84d64d889 (git) Affected: 8e8cda6d737d356054c9eeef642aec0e8ae7e6bc , < 0f3ad9ab40e3dad06d5c0693806e07935ceedbc3 (git) |
guessed | |
| Linux | Linux |
Affected:
4.12
Unaffected: 0 , < 4.12 (semver) Unaffected: 6.12.118 , ≤ 6.12.* (semver) Unaffected: 6.18.64 , ≤ 6.18.* (semver) Unaffected: 7.3.5 , ≤ 7.3.* (semver) Unaffected: 7.4-rc2 , ≤ * (original_commit_for_fix) |
guessed |
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"include/linux/can/can-ml.h",
"include/net/netns/can.h",
"net/can/af_can.c",
"net/can/bcm.c",
"net/can/isotp.c",
"net/can/raw.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "59d91f555ada337458c48316987b8ef46487f885",
"status": "affected",
"version": "8e8cda6d737d356054c9eeef642aec0e8ae7e6bc",
"versionType": "git"
},
{
"lessThan": "4b625dde57c0a40a933bf017ff93a64a7306aa43",
"status": "affected",
"version": "8e8cda6d737d356054c9eeef642aec0e8ae7e6bc",
"versionType": "git"
},
{
"lessThan": "228e795ec650c33ebbce8ba81ce983c84d64d889",
"status": "affected",
"version": "8e8cda6d737d356054c9eeef642aec0e8ae7e6bc",
"versionType": "git"
},
{
"lessThan": "0f3ad9ab40e3dad06d5c0693806e07935ceedbc3",
"status": "affected",
"version": "8e8cda6d737d356054c9eeef642aec0e8ae7e6bc",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"include/linux/can/can-ml.h",
"include/net/netns/can.h",
"net/can/af_can.c",
"net/can/bcm.c",
"net/can/isotp.c",
"net/can/raw.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "4.12"
},
{
"lessThan": "4.12",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.118",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.64",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.3.*",
"status": "unaffected",
"version": "7.3.5",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.4-rc2",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.12.118",
"versionStartIncluding": "4.12",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.64",
"versionStartIncluding": "4.12",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.3.5",
"versionStartIncluding": "4.12",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.4-rc2",
"versionStartIncluding": "4.12",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ncan: protect the receive lists with a per-device lock\n\nThe receive lists of a CAN device are located in the device\u0027s\ncan_ml_priv and travel with the device when it is moved to another\nnetwork namespace. But they are protected by the per-netns\nrcvlists_lock. So can_rx_unregister() needs dev_net(dev) to pick the\nright lock and silently returns when the passed namespace does not\nmatch dev_net(dev) anymore.\n\nisotp_release() and bcm_release() leave their notifier list before they\ntake any lock that serializes against the netdev notifier, which runs\nunder RTNL. When the bound device is moved to another namespace in this\nwindow, the notifier skips the socket and the release path has to remove\nthe filters itself. isotp_release() passes the socket\u0027s namespace, which\ndoes not match dev_net(dev) anymore. bcm_rx_unreg() passes dev_net(dev),\nwhich can_rx_unregister() reads again for its check, so a namespace\nchange between both reads makes the check fail as well. In both cases\ncan_rx_unregister() silently returns. As can_rx_register() stores\nrcv-\u003esk without a reference, the remaining receivers point to the freed\nsocket (isotp) or the freed op (bcm):\n\n BUG: KASAN: use-after-free in isotp_rcv+0x1570/0x24d0\n Read of size 1 at addr ffff888118130552 by task isotp_ns_uaf/578\n can_rcv_filter+0x4af/0x8c0\n can_receive+0x28d/0x3c0\n can_rcv+0x2a9/0x310\n __netif_receive_skb_one_core+0x21a/0x260\n process_backlog+0x210/0x760\n\nBesides this, the lists of a device are protected by the rcvlists_lock\nof the namespace that is passed in. Callers which pass dev_net(dev) read\nit at different times, so the same lists may be modified under the locks\nof different namespaces while the device is moved.\n\nTaking RTNL in these release paths is no option: raw_bind(),\nraw_setsockopt() and raw_release() already hold RTNL while adding and\nremoving up to CAN_RAW_FILTER_MAX filters per socket, which unprivileged\nusers can trigger repeatedly and which makes RTNL a global bottleneck.\n\nInstead fix the root cause and add a spinlock to struct\ncan_dev_rcv_lists, which protects the receive lists of a CAN device or\nthe \u0027any\u0027 CAN device lists of a namespace. It is initialized in\ncan_set_ml_priv(), which is used by all CAN network devices. With this,\ncan_rx_unregister() finds the subscription independently of the\ncurrent namespace of the device. The protocols keep the device valid\nwith their tracked references. The per-netns rcvlists_lock only protects\nthe receive list statistics anymore, and CAN_RAW, CAN_BCM and CAN_ISOTP\npass the namespace that has been used for can_rx_register().\n\nSo isotp_release() and bcm_release() now remove their filters correctly\nwithout RTNL, and raw_release(), raw_setsockopt(), raw_bind() and\nisotp_bind() do not need RTNL anymore and add and remove their filters\nunder lock_sock(). To serialize bind() with NETDEV_UNREGISTER, bind()\npublishes the device inside the RCU section of its lookup, and\nraw_notify() and isotp_notify() recheck the bound device under lock_sock().\nAs RTNL does not keep NETDEV_DOWN out of bind() anymore, bind() checks\nIFF_UP after publishing the bound device, with a barrier pair against\nraw_notify() and isotp_notify(), so a down transition during bind() is\nstill reported with ENETDOWN."
}
],
"providerMetadata": {
"dateUpdated": "2026-11-20T05:50:21.150Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/59d91f555ada337458c48316987b8ef46487f885"
},
{
"url": "https://git.kernel.org/stable/c/4b625dde57c0a40a933bf017ff93a64a7306aa43"
},
{
"url": "https://git.kernel.org/stable/c/228e795ec650c33ebbce8ba81ce983c84d64d889"
},
{
"url": "https://git.kernel.org/stable/c/0f3ad9ab40e3dad06d5c0693806e07935ceedbc3"
}
],
"title": "can: protect the receive lists with a per-device lock",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-99672",
"datePublished": "2026-11-20T05:50:21.150Z",
"dateReserved": "2026-09-25T10:25:14.428Z",
"dateUpdated": "2026-11-20T05:50:21.150Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-99672",
"date": "2026-11-20",
"epss": "0.00168",
"percentile": "0.06297"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"include/linux/can/can-ml.h",
"include/net/netns/can.h",
"net/can/af_can.c",
"net/can/bcm.c",
"net/can/isotp.c",
"net/can/raw.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "59d91f555ada337458c48316987b8ef46487f885",
"status": "affected",
"version": "8e8cda6d737d356054c9eeef642aec0e8ae7e6bc",
"versionType": "git"
},
{
"lessThan": "4b625dde57c0a40a933bf017ff93a64a7306aa43",
"status": "affected",
"version": "8e8cda6d737d356054c9eeef642aec0e8ae7e6bc",
"versionType": "git"
},
{
"lessThan": "228e795ec650c33ebbce8ba81ce983c84d64d889",
"status": "affected",
"version": "8e8cda6d737d356054c9eeef642aec0e8ae7e6bc",
"versionType": "git"
},
{
"lessThan": "0f3ad9ab40e3dad06d5c0693806e07935ceedbc3",
"status": "affected",
"version": "8e8cda6d737d356054c9eeef642aec0e8ae7e6bc",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"include/linux/can/can-ml.h",
"include/net/netns/can.h",
"net/can/af_can.c",
"net/can/bcm.c",
"net/can/isotp.c",
"net/can/raw.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "4.12"
},
{
"lessThan": "4.12",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.118",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.64",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.3.*",
"status": "unaffected",
"version": "7.3.5",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.4-rc2",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ncan: protect the receive lists with a per-device lock\n\nThe receive lists of a CAN device are located in the device\u0027s\ncan_ml_priv and travel with the device when it is moved to another\nnetwork namespace. But they are protected by the per-netns\nrcvlists_lock. So can_rx_unregister() needs dev_net(dev) to pick the\nright lock and silently returns when the passed namespace does not\nmatch dev_net(dev) anymore.\n\nisotp_release() and bcm_release() leave their notifier list before they\ntake any lock that serializes against the netdev notifier, which runs\nunder RTNL. When the bound device is moved to another namespace in this\nwindow, the notifier skips the socket and the release path has to remove\nthe filters itself. isotp_release() passes the socket\u0027s namespace, which\ndoes not match dev_net(dev) anymore. bcm_rx_unreg() passes dev_net(dev),\nwhich can_rx_unregister() reads again for its check, so a namespace\nchange between both reads makes the check fail as well. In both cases\ncan_rx_unregister() silently returns. As can_rx_register() stores\nrcv-\u003esk without a reference, the remaining receivers point to the freed\nsocket (isotp) or the freed op (bcm):\n\n BUG: KASAN: use-after-free in isotp_rcv+0x1570/0x24d0\n Read of size 1 at addr ffff888118130552 by task isotp_ns_uaf/578\n can_rcv_filter+0x4af/0x8c0\n can_receive+0x28d/0x3c0\n can_rcv+0x2a9/0x310\n __netif_receive_skb_one_core+0x21a/0x260\n process_backlog+0x210/0x760\n\nBesides this, the lists of a device are protected by the rcvlists_lock\nof the namespace that is passed in. Callers which pass dev_net(dev) read\nit at different times, so the same lists may be modified under the locks\nof different namespaces while the device is moved.\n\nTaking RTNL in these release paths is no option: raw_bind(),\nraw_setsockopt() and raw_release() already hold RTNL while adding and\nremoving up to CAN_RAW_FILTER_MAX filters per socket, which unprivileged\nusers can trigger repeatedly and which makes RTNL a global bottleneck.\n\nInstead fix the root cause and add a spinlock to struct\ncan_dev_rcv_lists, which protects the receive lists of a CAN device or\nthe \u0027any\u0027 CAN device lists of a namespace. It is initialized in\ncan_set_ml_priv(), which is used by all CAN network devices. With this,\ncan_rx_unregister() finds the subscription independently of the\ncurrent namespace of the device. The protocols keep the device valid\nwith their tracked references. The per-netns rcvlists_lock only protects\nthe receive list statistics anymore, and CAN_RAW, CAN_BCM and CAN_ISOTP\npass the namespace that has been used for can_rx_register().\n\nSo isotp_release() and bcm_release() now remove their filters correctly\nwithout RTNL, and raw_release(), raw_setsockopt(), raw_bind() and\nisotp_bind() do not need RTNL anymore and add and remove their filters\nunder lock_sock(). To serialize bind() with NETDEV_UNREGISTER, bind()\npublishes the device inside the RCU section of its lookup, and\nraw_notify() and isotp_notify() recheck the bound device under lock_sock().\nAs RTNL does not keep NETDEV_DOWN out of bind() anymore, bind() checks\nIFF_UP after publishing the bound device, with a barrier pair against\nraw_notify() and isotp_notify(), so a down transition during bind() is\nstill reported with ENETDOWN."
}
],
"id": "CVE-2026-99672",
"lastModified": "2026-11-20T06:18:01.797",
"metrics": {},
"published": "2026-11-20T06:18:01.797",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/0f3ad9ab40e3dad06d5c0693806e07935ceedbc3"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/228e795ec650c33ebbce8ba81ce983c84d64d889"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/4b625dde57c0a40a933bf017ff93a64a7306aa43"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/59d91f555ada337458c48316987b8ef46487f885"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
},
"redhat_vex": {
"aggregate_severity": "Moderate",
"current_release_date": "2026-11-20T11:26:22+00:00",
"cve": "CVE-2026-99672",
"id": "CVE-2026-99672",
"initial_release_date": "2026-11-20T05:50:21.150000+00:00",
"product_status:known_affected": "176",
"product_status:known_not_affected": "28",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "kernel: kernel: Denial of service via use-after-free in CAN subsystem during namespace migration",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-99672.json",
"version": "3"
}
}
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.