Skip to main content

Linux Kernel CVE-2026-43275

| EUVDEUVD-2026-27673 MEDIUM
Race Condition (CWE-362)
2026-05-06 Linux GHSA-c8jc-4xgp-98r9
4.7
CVSS 3.1 · NVD
Share

Severity by source

NVD PRIMARY
4.7 MEDIUM
AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
vuln.today AI
4.7 MEDIUM

Local-only attack vector and high complexity reflect the UFS hardware requirement and precise race condition timing window; PR:L as suspend may be triggerable by low-privilege users; availability-only impact from kernel panic with no confidentiality or integrity loss.

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

Primary rating from NVD.

CVSS VectorNVD

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

Lifecycle Timeline

4
Analysis Generated
Jul 24, 2026 - 00:43 vuln.today
CVSS changed
May 08, 2026 - 19:37 NVD
4.7 (MEDIUM)
Patch available
May 06, 2026 - 13:32 EUVD
CVE Published
May 06, 2026 - 11:28 nvd
MEDIUM 4.7

DescriptionCVE.org

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

scsi: ufs: core: Flush exception handling work when RPM level is zero

Ensure that the exception event handling work is explicitly flushed during suspend when the runtime power management level is set to UFS_PM_LVL_0.

When the RPM level is zero, the device power mode and link state both remain active. Previously, the UFS core driver bypassed flushing exception event handling jobs in this configuration. This created a race condition where the driver could attempt to access the host controller to handle an exception after the system had already entered a deep power-down state, resulting in a system crash.

Explicitly flush this work and disable auto BKOPs before the suspend callback proceeds. This guarantees that pending exception tasks complete and prevents illegal hardware access during the power-down sequence.

AnalysisAI

Race condition in the Linux kernel UFS core driver causes a system crash during suspend when the runtime power management level is set to UFS_PM_LVL_0. At this PM level the device power mode and link state remain active, yet the driver previously skipped flushing pending exception event handling work before proceeding with suspend - allowing a workqueue job to access UFS host controller registers after the hardware has entered a deep power-down state. The resulting kernel panic yields a total denial of service. No public exploit has been identified and EPSS sits at 0.02% (7th percentile), indicating low near-term exploitation likelihood.

Technical ContextAI

The vulnerability resides in the Universal Flash Storage (UFS) core driver (drivers/ufs/core/) within the Linux kernel SCSI subsystem, introduced alongside UFS support around Linux 3.18. UFS is a high-speed storage protocol used primarily in mobile and embedded Linux platforms. The kernel defines multiple runtime PM levels (UFS_PM_LVL_0 through higher levels) that govern how aggressively device power mode and link state are modified during runtime suspend. At UFS_PM_LVL_0, both the device power mode and link state are intentionally left active, which previously caused the suspend path to bypass the workqueue flush step. CWE-362 (Concurrent Execution Using Shared Resource with Improper Synchronization) precisely describes the root cause: the exception event handling workqueue can be in flight when suspend proceeds, producing a time-of-check-to-time-of-use race where hardware register access occurs after power-down is already in progress. The fix explicitly flushes the exception handling work and disables auto BKOPs before the suspend callback completes, eliminating the race.

RemediationAI

The primary fix is to upgrade to a patched kernel version: 5.15.202, 6.1.165, 6.6.128, 6.12.75, 6.18.16, 6.19.6, or 7.0. Upstream stable backport commits are available at https://git.kernel.org/stable/c/d5c3a1a13f97355c397f9439d79cb04b182958a3, https://git.kernel.org/stable/c/5d186731bc335cc049d4e57ab9f563cfab95593e, https://git.kernel.org/stable/c/aa8d68d97c7f0ef966e51afc17fdbdc372700edf, https://git.kernel.org/stable/c/aac2fee7513dd25042a616f86a1469b4858d2c5c, https://git.kernel.org/stable/c/78d8e2d6352e8317686ee3a44811ac14c415a57d, https://git.kernel.org/stable/c/ab71c146c135f9af1614ef0fc29a0a3b84f1a373, and https://git.kernel.org/stable/c/f8ef441811ec413717f188f63d99182f30f0f08e. Ubuntu users should apply USN-8492-1. As a compensating control on unpatched systems, configuring the UFS runtime PM level to any value above UFS_PM_LVL_0 (so that device power mode or link state is modified on suspend) eliminates the vulnerable code path - trade-off is increased power consumption during runtime suspend on battery-constrained devices. Red Hat and SUSE subscribers should consult vendor-specific errata for their distribution versions.

Vendor StatusVendor

SUSE

Severity: Medium
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Fixed
SUSE Linux Enterprise Desktop 15 SP7 Fixed
SUSE Linux Enterprise High Availability Extension 15 SP7 Fixed
SUSE Linux Enterprise High Availability Extension 15 SP7 Fixed
SUSE Linux Enterprise High Performance Computing 15 SP7 Fixed

Share

CVE-2026-43275 vulnerability details – vuln.today

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