Skip to main content

Linux Kernel CVE-2026-43430

| EUVDEUVD-2026-28736 MEDIUM
Race Condition (CWE-362)
2026-05-08 Linux GHSA-gvc8-8g78-x3hg
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
SUSE
MEDIUM
qualitative

Primary rating from NVD.

CVSS VectorNVD

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
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
May 20, 2026 - 18:39 vuln.today
CVSS changed
May 20, 2026 - 18:37 NVD
4.7 (MEDIUM)
Patch available
May 08, 2026 - 16:18 EUVD
CVE Published
May 08, 2026 - 14:22 nvd
UNKNOWN (no severity yet)

DescriptionCVE.org

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

usb: yurex: fix race in probe

The bbu member of the descriptor must be set to the value standing for uninitialized values before the URB whose completion handler sets bbu is submitted. Otherwise there is a window during which probing can overwrite already retrieved data.

AnalysisAI

Race condition in the Linux kernel's yurex USB driver probe function allows a local low-privileged attacker to cause a denial of service by triggering a timing window between URB submission and bbu member initialization. Affected are all kernel versions from the initial commit through the stable branch fix points (patched in 5.10.253, 5.15.203, 6.1.167, 6.6.130, 6.12.78, 6.18.19, 6.19.9, and 7.0). No public exploit exists and the issue is not listed in CISA KEV; EPSS of 0.02% (7th percentile) reflects negligible widespread exploitation probability.

Technical ContextAI

The yurex driver (drivers/usb/misc/yurex.c) handles the Yurex USB BBU (Bending and Boring Units) measurement device. USB Request Blocks (URBs) are the kernel's asynchronous I/O mechanism for USB communication; the completion callback fires asynchronously when the device responds. The root cause is CWE-362 (Race Condition / Improper Synchronization): the probe function submits the URB before setting the bbu descriptor member to its sentinel/uninitialized value. This creates a window where the URB completion handler correctly populates bbu with device data, then the still-running probe function overwrites it with an uninitialized value, discarding valid data and potentially destabilizing driver state. The CPE cpe:2.3:a:linux:linux:*:*:*:*:*:*:*:* confirms the issue spans the entire mainline Linux kernel codebase across multiple stable branches.

RemediationAI

Update to a patched stable kernel release: 5.10.253, 5.15.203, 6.1.167, 6.6.130, 6.12.78, 6.18.19, 6.19.9, or 7.0. Upstream fix commits are available at the following kernel.org stable references: https://git.kernel.org/stable/c/a7934d7202a39c3160aa30521c382c7b744ae4a2, https://git.kernel.org/stable/c/687d26d43a5aaf44323ce7d601cf242bb87e9559, https://git.kernel.org/stable/c/939e3d17b843b0bae70467fef4481069d73c8520, https://git.kernel.org/stable/c/3cec135415a89723e2d38e1c8cc5098203355965, and others listed in the CVE references. Where immediate patching is not possible, USB device authorization can be restricted on the affected bus via /sys/bus/usb/devices/usbX/authorized_default set to 0 to prevent the yurex driver probe from being triggered; note this disables enumeration of all USB devices on that bus and will break other USB peripherals. Alternatively, blacklisting the yurex kernel module (echo 'blacklist yurex' >> /etc/modprobe.d/blacklist.conf) prevents the driver from loading entirely with no impact on other USB functionality, at the cost of losing Yurex device support.

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

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