CVE-2026-72113

Last refreshed2026-10-17

Status: UPDATED | Advisory ID: CVE-2026-72113

Key Details

CVE	CVE-2026-72113
CVSS Score / Version	7.8 (High) / CVSS v3.1
Updated	2026-10-16
CVSS Vector	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`
CVSS Prose	attack vector is local; attack complexity is low; privileges required is low; user interaction is none; scope is unchanged; confidentiality impact is high; integrity impact is high; availability impact is high.
Affected products	Linux Kernel

Vendor	Product	Affected Versions	Patch Status
Linux	Linux Kernel

Vendor

Product

Affected Versions

Patch Status

Linux

Linux Kernel

Subsystems	OT Supporting Infrastructure
Sectors	All Sectors

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. (NVD)

Monitor Linux's web page for any future patch releases.

Source	Reference
NVD	https://nvd.nist.gov/vuln/detail/CVE-2026-72113
CVE	https://www.cve.org/CVERecord?id=CVE-2026-72113

Source

Reference

NVD

CVE