Skip to main content

Linux Kernel CVE-2026-72113

| EUVDEUVD-2026-59071 HIGH
2026-08-15 416baaa9-dc9f-4396-8d5f-8c081fb06d67 GHSA-q526-m4v6-prwf
7.8
CVSS 3.1 · Vendor: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Share

Severity by source

Vendor (416baaa9-dc9f-4396-8d5f-8c081fb06d67) PRIMARY
7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
7.0 HIGH

Race condition requiring precise concurrent NETDEV_UNREGISTER timing warrants AC:H; PR:L and AV:L confirmed by the local CAN socket requirement.

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
SUSE
4.7 MEDIUM
AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
Red Hat
5.5 MEDIUM
qualitative

Primary rating from Vendor (416baaa9-dc9f-4396-8d5f-8c081fb06d67).

CVSS VectorVendor: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

5
Analysis Generated
Aug 17, 2026 - 06:56 vuln.today
CVSS changed
Aug 17, 2026 - 06:22 NVD
7.8 (HIGH)
Patch available
Aug 15, 2026 - 07:20 EUVD
CVE Published
Aug 15, 2026 - 06:21 cve.org
HIGH 7.8
CVE Published
Aug 15, 2026 - 06:21 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

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

can: bcm: add missing device refcount for CAN filter removal

sashiko-bot remarked a problem with a concurrent device unregistration in isotp.c which also is present in the bcm.c code. A former fix for raw.c commit c275a176e4b6 ("can: raw: add missing refcount for memory leak fix") introduced a netdevice_tracker which solves the issue for bcm.c too.

bcm_release(), bcm_delete_rx_op() and bcm_notifier() relied on dev_get_by_index(ifindex) to re-find the device for an rx_op before unregistering its filter. If a concurrent NETDEV_UNREGISTER has already unlisted the device from the ifindex table, that lookup fails and can_rx_unregister() is silently skipped, leaving a stale CAN filter pointing at the soon-to-be-freed bcm_op/socket.

Hold a netdev_hold()/netdev_put() tracked reference on op->rx_reg_dev from the moment the rx filter is registered in bcm_rx_setup() until it is unregistered in bcm_rx_unreg(), and use that reference directly in bcm_release() and bcm_delete_rx_op() instead of re-looking the device up by ifindex.

AnalysisAI

Use-after-free race condition in the Linux kernel CAN BCM (Broadcast Manager) subsystem allows a local low-privileged attacker to trigger a stale filter pointer against freed memory, with potential full CIA impact on affected systems. The flaw exists from kernel 2.6.25 onward in net/can/bcm.c, where concurrent NETDEV_UNREGISTER events could silently bypass can_rx_unregister(), leaving dangling references to freed bcm_op and socket structures. No active exploitation is confirmed (not in CISA KEV), and EPSS sits at 0.21% (11th percentile), indicating very low real-world exploitation probability at this time.

Technical ContextAI

The vulnerability resides in the Linux kernel's CAN BCM socket implementation (net/can/bcm.c), which provides a broadcast manager interface for user-space CAN bus applications to register periodic transmission and receive filters. The root cause is a classic TOCTOU (Time-of-Check-Time-of-Use) race condition: bcm_release(), bcm_delete_rx_op(), and bcm_notifier() each re-looked up the network device by ifindex via dev_get_by_index() before calling can_rx_unregister(). If a concurrent NETDEV_UNREGISTER event had already removed the device from the ifindex table before this lookup, the re-lookup failed silently, can_rx_unregister() was skipped entirely, and the CAN filter was left with a stale pointer to the soon-to-be-freed bcm_op or socket. The fix mirrors the pattern established by commit c275a176e4b6 in can/raw.c, introducing a netdev_tracker via netdev_hold() at filter registration in bcm_rx_setup() and netdev_put() at deregistration in bcm_rx_unreg(), eliminating the re-lookup race entirely. CWE is not formally assigned but this is structurally CWE-362 (Concurrent Execution Using Shared Resource with Improper Synchronization) leading to CWE-416 (Use After Free). CPE data from EUVD identifies the affected product as the Linux kernel from version 2.6.25 through the respective patched stable releases.

RemediationAI

Upgrade the Linux kernel to a patched stable release: 6.6.148, 6.12.101, 6.18.42, 7.1.5, or 7.2-rc4 or later, applying the appropriate backport commit for your kernel series from https://git.kernel.org/stable/c/04d23061bbf18d5d81022eb21e9d32e99d24468d and related stable tree entries. For systems that cannot be immediately patched, the most effective compensating control is to unload or blacklist the can-bcm kernel module (modprobe -r can-bcm; echo 'blacklist can-bcm' >> /etc/modprobe.d/can-blacklist.conf) - this entirely eliminates the attack surface with no functional impact on non-CAN workloads. On systems requiring CAN bus functionality, restrict AF_CAN socket creation to authorized processes only using seccomp profiles, AppArmor socket rules, or SELinux policy to deny unprivileged access to socket(AF_CAN, SOCK_DGRAM, CAN_BCM); this limits exploitation to higher-privilege accounts, raising the effective PR level. Patch priority should be elevated for automotive, ICS, and embedded Linux platforms where CAN networking is actively used and local user accounts may be less controlled.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 16.0 Affected

Share

CVE-2026-72113 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy