{"api_version":"1","generated_at":"2026-08-17T16:00:56+00:00","cve":"CVE-2026-72116","urls":{"html":"https://cve.report/CVE-2026-72116","api":"https://cve.report/api/cve/CVE-2026-72116.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-72116","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-72116"},"summary":{"title":"can: bcm: fix stale rx/tx ops after device removal","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ncan: bcm: fix stale rx/tx ops after device removal\n\nRX: an RX_SETUP update(!) for an existing op skipped can_rx_register()\nunconditionally, even when a concurrent NETDEV_UNREGISTER had already\ntorn down its registration (op->rx_reg_dev == NULL). This silently\ndid not re-enable frame delivery for that updated filter. bcm_rx_setup()\nnow re-registers in that case, while leaving rx_ops with ifindex = 0\n(all CAN devices) which never carry a tracked rx_reg_dev registered as-is.\n\nTX: bcm_notify() only handled bo->rx_ops on NETDEV_UNREGISTER, leaving\ntx_ops with an active cyclic transmission re-arming its hrtimer\nindefinitely to execute bcm_tx_timeout_handler(). Cancelling the hrtimer\nprevents the runaway timer and any injection into a later reused ifindex,\nsince nothing else calls bcm_can_tx() for the op until an explicit\nTX_SETUP update re-arms it.\n\nUnlike bcm_rx_unreg(), which clears the tracked rx_reg_dev for rx_ops,\nthe ifindex is intentionally left unchanged for tx_ops. bcm_tx_setup()\nalways rejects ifindex 0, so clearing it would strand the op: neither a\nlater TX_SETUP (bcm_find_op()) nor TX_DELETE (bcm_delete_tx_op()) could\never find it again, since both require an exact ifindex match.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-08-15 06:21:26","updated_at":"2026-08-17 06:18:10"},"problem_types":[],"metrics":[{"version":"3.1","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","type":"Secondary","score":"7.1","severity":"HIGH","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H","data":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H","baseScore":7.1,"baseSeverity":"HIGH","attackVector":"LOCAL","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"NONE","integrityImpact":"HIGH","availabilityImpact":"HIGH"}},{"version":"3.1","source":"CNA","type":"DECLARED","score":"7.1","severity":"HIGH","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H","data":{"baseScore":7.1,"baseSeverity":"HIGH","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H","version":"3.1"}}],"references":[{"url":"https://git.kernel.org/stable/c/6be3e1fedf03eab36a2c09d755d1171287b2014b","name":"https://git.kernel.org/stable/c/6be3e1fedf03eab36a2c09d755d1171287b2014b","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/3b762c0d950383ab7a002686c9136b9aa55d2d70","name":"https://git.kernel.org/stable/c/3b762c0d950383ab7a002686c9136b9aa55d2d70","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/60d8a7942f4ed2d975207aaeba1adb576707e53d","name":"https://git.kernel.org/stable/c/60d8a7942f4ed2d975207aaeba1adb576707e53d","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/b31d0933509c5a35c0be5736a2ce8df0d1bf112c","name":"https://git.kernel.org/stable/c/b31d0933509c5a35c0be5736a2ce8df0d1bf112c","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/f749e4564952d60e96930c09f2be99955d07c22e","name":"https://git.kernel.org/stable/c/f749e4564952d60e96930c09f2be99955d07c22e","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-72116","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72116","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected ffd980f976e7fd666c2e61bf8ab35107efd11828 60d8a7942f4ed2d975207aaeba1adb576707e53d git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected ffd980f976e7fd666c2e61bf8ab35107efd11828 f749e4564952d60e96930c09f2be99955d07c22e git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected ffd980f976e7fd666c2e61bf8ab35107efd11828 6be3e1fedf03eab36a2c09d755d1171287b2014b git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected ffd980f976e7fd666c2e61bf8ab35107efd11828 b31d0933509c5a35c0be5736a2ce8df0d1bf112c git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected ffd980f976e7fd666c2e61bf8ab35107efd11828 3b762c0d950383ab7a002686c9136b9aa55d2d70 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 2.6.25","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 2.6.25 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.6.148 6.6.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.101 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.42 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1.5 7.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"72116","cve":"CVE-2026-72116","epss":"0.002150000","percentile":"0.122680000","score_date":"2026-08-16","updated_at":"2026-08-17 00:01:06"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["net/can/bcm.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"60d8a7942f4ed2d975207aaeba1adb576707e53d","status":"affected","version":"ffd980f976e7fd666c2e61bf8ab35107efd11828","versionType":"git"},{"lessThan":"f749e4564952d60e96930c09f2be99955d07c22e","status":"affected","version":"ffd980f976e7fd666c2e61bf8ab35107efd11828","versionType":"git"},{"lessThan":"6be3e1fedf03eab36a2c09d755d1171287b2014b","status":"affected","version":"ffd980f976e7fd666c2e61bf8ab35107efd11828","versionType":"git"},{"lessThan":"b31d0933509c5a35c0be5736a2ce8df0d1bf112c","status":"affected","version":"ffd980f976e7fd666c2e61bf8ab35107efd11828","versionType":"git"},{"lessThan":"3b762c0d950383ab7a002686c9136b9aa55d2d70","status":"affected","version":"ffd980f976e7fd666c2e61bf8ab35107efd11828","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["net/can/bcm.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"2.6.25"},{"lessThan":"2.6.25","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.6.*","status":"unaffected","version":"6.6.148","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.101","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.42","versionType":"semver"},{"lessThanOrEqual":"7.1.*","status":"unaffected","version":"7.1.5","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.2","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.6.148","versionStartIncluding":"2.6.25","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.101","versionStartIncluding":"2.6.25","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.42","versionStartIncluding":"2.6.25","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1.5","versionStartIncluding":"2.6.25","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2","versionStartIncluding":"2.6.25","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\ncan: bcm: fix stale rx/tx ops after device removal\n\nRX: an RX_SETUP update(!) for an existing op skipped can_rx_register()\nunconditionally, even when a concurrent NETDEV_UNREGISTER had already\ntorn down its registration (op->rx_reg_dev == NULL). This silently\ndid not re-enable frame delivery for that updated filter. bcm_rx_setup()\nnow re-registers in that case, while leaving rx_ops with ifindex = 0\n(all CAN devices) which never carry a tracked rx_reg_dev registered as-is.\n\nTX: bcm_notify() only handled bo->rx_ops on NETDEV_UNREGISTER, leaving\ntx_ops with an active cyclic transmission re-arming its hrtimer\nindefinitely to execute bcm_tx_timeout_handler(). Cancelling the hrtimer\nprevents the runaway timer and any injection into a later reused ifindex,\nsince nothing else calls bcm_can_tx() for the op until an explicit\nTX_SETUP update re-arms it.\n\nUnlike bcm_rx_unreg(), which clears the tracked rx_reg_dev for rx_ops,\nthe ifindex is intentionally left unchanged for tx_ops. bcm_tx_setup()\nalways rejects ifindex 0, so clearing it would strand the op: neither a\nlater TX_SETUP (bcm_find_op()) nor TX_DELETE (bcm_delete_tx_op()) could\never find it again, since both require an exact ifindex match."}],"metrics":[{"cvssV3_1":{"baseScore":7.1,"baseSeverity":"HIGH","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H","version":"3.1"},"scenarios":[{"lang":"en","value":"AV:L - The bug is reached only via local PF_CAN/CAN_BCM syscalls (socket/connect/sendmsg TX_SETUP or RX_SETUP); bcm_tx_timeout_handler() is driven by a local hrtimer, not by remote network services or CAN bus frames alone.\nAC:L - An attacker controls both sides by arming cyclic TX with SETTIMER/STARTTIMER, then triggering or waiting for NETDEV_UNREGISTER (e.g., concurrent ip link del in a user namespace) while ifindex reuse is normal kernel behavior, making injection reliably achievable.\nPR:L - can_create(), bcm_connect(), and bcm_sendmsg() perform no capability checks; any local user with CAN access (or CAP_NET_ADMIN in an unprivileged user namespace to create vcan) can open BCM sockets and program cyclic TX/RX ops.\nUI:N - Exploitation requires only the attacker opening a BCM socket and sending TX_SETUP/RX_SETUP messages; no victim action such as mounting media or opening files is needed once local CAN access exists.\nS:U - Impact is unauthorized CAN transmission/monitoring disruption within the same kernel host; it does not cross VM, container, or IOMMU security boundaries even when frames reach an adjacent vehicle or factory CAN segment.\nC:N - The flaw causes stale timer-driven transmission and missed RX re-registration, not kernel memory disclosure; no out-of-bounds read, UAF, or other information-leak primitive is present in this bug.\nI:H - After NETDEV_UNREGISTER, orphaned tx_ops keep bcm_can_tx() running with a stale ifindex, so attacker-crafted cyclic CAN frames can be injected onto any later netdev that reuses that ifindex, including safety-critical automotive or industrial buses.\nA:H - Uncancelled hrtimers on stale tx_ops re-arm bcm_tx_timeout_handler() indefinitely after device removal, causing persistent timer/softirq CPU consumption, and the RX_SETUP path can silently stop frame delivery after unregister races."}]}],"providerMetadata":{"dateUpdated":"2026-08-17T05:40:31.158Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/60d8a7942f4ed2d975207aaeba1adb576707e53d"},{"url":"https://git.kernel.org/stable/c/f749e4564952d60e96930c09f2be99955d07c22e"},{"url":"https://git.kernel.org/stable/c/6be3e1fedf03eab36a2c09d755d1171287b2014b"},{"url":"https://git.kernel.org/stable/c/b31d0933509c5a35c0be5736a2ce8df0d1bf112c"},{"url":"https://git.kernel.org/stable/c/3b762c0d950383ab7a002686c9136b9aa55d2d70"}],"title":"can: bcm: fix stale rx/tx ops after device removal","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-72116","datePublished":"2026-08-15T05:52:56.260Z","dateReserved":"2026-08-09T03:40:39.906Z","dateUpdated":"2026-08-17T05:40:31.158Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-08-15 06:21:26","lastModifiedDate":"2026-08-17 06:18:10","problem_types":[],"metrics":{"cvssMetricV31":[{"source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","type":"Secondary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H","baseScore":7.1,"baseSeverity":"HIGH","attackVector":"LOCAL","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"NONE","integrityImpact":"HIGH","availabilityImpact":"HIGH"},"exploitabilityScore":1.8,"impactScore":5.2}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"72116","Ordinal":"1","Title":"can: bcm: fix stale rx/tx ops after device removal","CVE":"CVE-2026-72116","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"72116","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\ncan: bcm: fix stale rx/tx ops after device removal\n\nRX: an RX_SETUP update(!) for an existing op skipped can_rx_register()\nunconditionally, even when a concurrent NETDEV_UNREGISTER had already\ntorn down its registration (op->rx_reg_dev == NULL). This silently\ndid not re-enable frame delivery for that updated filter. bcm_rx_setup()\nnow re-registers in that case, while leaving rx_ops with ifindex = 0\n(all CAN devices) which never carry a tracked rx_reg_dev registered as-is.\n\nTX: bcm_notify() only handled bo->rx_ops on NETDEV_UNREGISTER, leaving\ntx_ops with an active cyclic transmission re-arming its hrtimer\nindefinitely to execute bcm_tx_timeout_handler(). Cancelling the hrtimer\nprevents the runaway timer and any injection into a later reused ifindex,\nsince nothing else calls bcm_can_tx() for the op until an explicit\nTX_SETUP update re-arms it.\n\nUnlike bcm_rx_unreg(), which clears the tracked rx_reg_dev for rx_ops,\nthe ifindex is intentionally left unchanged for tx_ops. bcm_tx_setup()\nalways rejects ifindex 0, so clearing it would strand the op: neither a\nlater TX_SETUP (bcm_find_op()) nor TX_DELETE (bcm_delete_tx_op()) could\never find it again, since both require an exact ifindex match.","Type":"Description","Title":"can: bcm: fix stale rx/tx ops after device removal"}]}}}