Skip to main content

Linux Kernel CVE-2026-72114

| EUVDEUVD-2026-59072 HIGH
2026-08-15 416baaa9-dc9f-4396-8d5f-8c081fb06d67 GHSA-fxhv-rjvf-632g
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.8 HIGH

Local CAN socket access requires low privileges; no pre-conditions beyond module availability; unvalidated kernel write yields full C/I/A impact within unchanged scope.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
SUSE
5.5 MEDIUM
AV:L/AC:L/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:58 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: validate frame length in bcm_rx_setup() for RTR replies

bcm_tx_setup() validates cf->len against the CAN/CAN FD DLC limits before installing frames for TX_SETUP, but bcm_rx_setup() never did the same for the RTR-reply frame configured via RX_SETUP with RX_RTR_FRAME.

AnalysisAI

Missing frame length validation in the Linux kernel CAN Broadcast Manager (BCM) subsystem allows a local low-privileged user to trigger kernel memory corruption by supplying a malformed RTR-reply frame via RX_SETUP with the RX_RTR_FRAME flag. While bcm_tx_setup() correctly enforces DLC bounds on TX_SETUP frames, the equivalent check was absent in bcm_rx_setup(), creating an asymmetric validation gap reachable through the CAN socket interface. The CVSS 3.1 score is 7.8 HIGH with full C/I/A impact; no public exploit has been identified and the vulnerability is not listed in the CISA KEV catalog, but patched stable releases are available across multiple kernel branches.

Technical ContextAI

The CAN (Controller Area Network) Broadcast Manager (BCM) is a Linux kernel network subsystem providing automated message scheduling and filtering for CAN bus communications, widely used in automotive and industrial embedded environments. The RTR (Remote Transmission Request) frame type allows a node to solicit data from another CAN participant; in the BCM, RX_SETUP with RX_RTR_FRAME installs a reply frame that is transmitted automatically in response to incoming RTR requests. The vulnerability arises because bcm_rx_setup() omits the cf->len bounds check against CAN DLC limits (max 8 bytes) and CAN FD DLC limits (max 64 bytes) that bcm_tx_setup() correctly enforces, consistent with an improper input validation root cause (analogous to CWE-20, though no CWE was formally assigned). A malformed length value can therefore propagate into kernel memory operations, potentially resulting in out-of-bounds reads or writes within kernel structures. The affected code traces back to commit ffd980f976e7fd666c2e61bf8ab35107efd11828, corresponding to Linux 2.6.25, meaning the flaw has persisted across approximately 17 years of kernel development.

RemediationAI

Upgrade the Linux kernel to a patched stable release: 6.6.148 or later for the 6.6 LTS branch, 6.12.101 or later for the 6.12 LTS branch, 6.18.42 or later for the 6.18 branch, or 7.1.5 or later for the 7.1 branch; all patch commits are available at the kernel.org stable repository links listed in the affected products section. If an immediate kernel upgrade is not operationally feasible, restrict CAN BCM socket access by enforcing the CAP_NET_RAW capability boundary - verify this is enforced via seccomp profiles, SELinux policy, or AppArmor confinement, as permissive network namespaces may otherwise allow unprivileged socket creation. For systems that do not require CAN Broadcast Manager functionality at all, blacklisting the can-bcm kernel module in /etc/modprobe.d/ and unloading it with rmmod eliminates the attack surface entirely; the trade-off is that legitimate CAN filtering and automated frame scheduling features become unavailable. Distributions such as those based on Debian, Ubuntu, RHEL, and SUSE should be monitored for vendor-specific kernel update advisories that backport these fixes to their supported kernel versions.

Vendor StatusVendor

SUSE

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

Share

CVE-2026-72114 vulnerability details – vuln.today

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