What is CVE-2026-72113?

CVE-2026-72113 is a High severity Linux kernel vulnerability with a CVSS score of 7.8 out of 10, affecting Linux kernel versions from 2.6.25 onward and patched in 5.10.265, 5.15.216, 6.1.183 and others. CVE-2026-72113 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2026-72113?

CVE-2026-72113 has a CVSS score of 7.8 out of 10, rated High severity. The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

Is there a patch available for CVE-2026-72113?

Yes, CVE-2026-72113 has been patched. Fixed versions include 5.10.265, 5.15.216, 6.1.183 and others. If you are running Linux kernel 2.6.25 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2026-72113 actively exploited?

CVE-2026-72113 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

CVE-2026-72113

High

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.

Package Linux Kernel

Published 2026-08-15

Last modified 2026-08-19

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

7.8

out of 10

High

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Vector string

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected versions

Linux kernel versions 2.6.25 and later are affected. Fixed in 5.10.265, 5.15.216, 6.1.183, 6.6.148, 6.12.101, 6.18.42, 7.1.5, 7.2 and their respective stable series.

Affected from

≥ 2.6.25

Fixed in

✓ 5.10.265 5.10.x ✓ 5.15.216 5.15.x ✓ 6.1.183 6.1.x ✓ 6.6.148 6.6.x ✓ 6.12.101 6.12.x ✓ 6.18.42 6.18.x ✓ 7.1.5 7.1.x ✓ 7.2

References

8 total

Showing 5 of 8 references View all on NVD

Details

CVE ID CVE-2026-72113

Severity High

CVSS score 7.8 / 10

CVSS version 3.1

Published 2026-08-15

Modified 2026-08-19

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2026-72113?

CVE-2026-72113 is a High severity Linux kernel vulnerability with a CVSS score of 7.8 out of 10 . It affects Linux kernel versions from 2.6.25 onward and has been patched in 5.10.265, 5.15.216, 6.1.183 and others. CVE-2026-72113 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2026-72113?

CVE-2026-72113 has a CVSS score of 7.8 out of 10, rated High severity (CVSS 3.1). The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
Is there a patch available for CVE-2026-72113?

Yes. CVE-2026-72113 has been patched. Fixed versions include 5.10.265, 5.15.216, 6.1.183 and others. If you are running Linux kernel 2.6.25 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2026-72113 actively exploited?

No. CVE-2026-72113 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.