Skip to main content

Linux Kernel CVE-2026-68210

| EUVDEUVD-2026-55311 HIGH
2026-08-10 Linux GHSA-76fm-3jg5-qp3h
7.8
CVSS 3.1 · Vendor: Linux
Share

Severity by source

Vendor (Linux) 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

Reset control failure is a hardware-specific non-default condition warranting AC:H; local low-privilege access is required to interact with the driver module.

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

CVSS VectorVendor: Linux

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 14, 2026 - 03:34 vuln.today
CVSS changed
Aug 13, 2026 - 23:37 NVD
7.8 (HIGH)
Patch available
Aug 10, 2026 - 14:18 EUVD
CVE Published
Aug 10, 2026 - 12:00 cve.org
HIGH 7.8
CVE Published
Aug 10, 2026 - 12:00 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

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

media: stm32: dcmi: unregister notifier on probe failure

dcmi_graph_init() registers the async notifier before dcmi_probe() toggles the reset line. If reset_control_assert() or reset_control_deassert() fails afterwards, probe returns through err_cleanup and the driver core will not call dcmi_remove().

Unregister the notifier before cleaning it up on that error path, matching the successful remove path and the V4L2 async notifier lifetime rules.

[hverkuil: added Fixes tag]

AnalysisAI

Improper error-path cleanup in the Linux kernel STM32 DCMI driver leaves a V4L2 async notifier registered against kernel structures that may be freed or reused after a failed probe, creating a use-after-free condition. Systems running a vulnerable kernel with STM32 DCMI hardware where reset_control_assert() or reset_control_deassert() returns an error during driver initialization are susceptible to kernel memory corruption or crashes. No public exploit has been identified and EPSS sits at the 11th percentile, but CVSS rates the impact as High across confidentiality, integrity, and availability when the specific failure condition is met.

Technical ContextAI

The Linux kernel driver at drivers/media/platform/st/stm32/stm32-dcmi.c implements the STM32 Digital Camera Memory Interface, a video capture peripheral found in STMicroelectronics STM32 SoCs used in embedded and industrial systems. The V4L2 async notifier framework (v4l2_async_nf_register / v4l2_async_nf_unregister) allows camera drivers to register callbacks that fire asynchronously when subordinate devices such as image sensors become available. During dcmi_probe(), dcmi_graph_init() registers the notifier via v4l2_async_nf_register(), but if the immediately subsequent reset_control_assert() or reset_control_deassert() call fails, the function returns via err_cleanup without invoking v4l2_async_nf_unregister(). Because the driver core does not call dcmi_remove() on probe failure, the dangling notifier remains registered and can fire against freed or reused kernel memory - a classic use-after-free scenario arising from asymmetric error-path teardown. NVD did not assign a CWE, but the root cause maps to CWE-459 (Incomplete Cleanup) and CWE-416 (Use After Free). The vulnerability was introduced by commit d079f94c90469f413920b9f2b201537fac2ceb06 and is restricted to the stm32-dcmi module.

RemediationAI

The primary fix is to upgrade the Linux kernel to a patched stable release: 6.6.148, 6.12.101, 6.18.42, or 7.1.6 for users tracking LTS or stable branches, or 7.2-rc1 for mainline. Upstream fix commits are available for review and backporting at https://git.kernel.org/stable/c/37ff63c5d7119cbc5c6bacdcc658add6008a8e1f, https://git.kernel.org/stable/c/6c6f22b7e6cbc4e8c1e359fc9b190419391c3db7, https://git.kernel.org/stable/c/931abe1deb65b919d23fa203d7f6d6fbd4fccd8e, https://git.kernel.org/stable/c/4b7ee504969e074725e439c949f2483e5fa5572a, and https://git.kernel.org/stable/c/084973ebd67b28f0945c5d45408f86c58b540110. As a compensating control where immediate patching is not feasible, administrators may blacklist the stm32-dcmi module by adding 'blacklist stm32-dcmi' to /etc/modprobe.d/local.conf - this disables DCMI-based camera capture on affected hardware but fully prevents the vulnerable probe path from executing. Systems that do not operate STM32 DCMI camera hardware require no action.

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-68210 vulnerability details – vuln.today

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