Skip to main content

Linux Kernel EUVDEUVD-2026-24853

| CVE-2026-31487 MEDIUM
Improper Locking (CWE-667)
2026-04-22 416baaa9-dc9f-4396-8d5f-8c081fb06d67 GHSA-vq56-9rjp-57fc
5.5
CVSS 3.1 · NVD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain local shell access
  2. Delivery
    Write to sysfs driver_override node
  3. Exploit
    Trigger SPI device probe via hot-plug
  4. Execution
    Race condition reads freed pointer
  5. Persist
    Kernel UAF detected
  6. Impact
    Denial of service via kernel panic

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Proper locking
Exploitation Conditions

Exploitation requires local authenticated access (PR:L in CVSS) to write to sysfs driver_override node, a system with active SPI bus hardware or emulation, and precise timing to race the device probe operation. The vulnerability cannot be exploited remotely or by unauthenticated users. Systems without SPI subsystem compiled or with SPI drivers statically linked without hot-plug support are not vulnerable. The race window is inherently narrow and platform-dependent, requiring the attacker to repeatedly trigger device probe while manipulating driver_override, making reliable exploitation extremely difficult.

Impact

Real-world exploitation risk is low despite moderate CVSS score. The CVSS vector (AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H) indicates local attack vector requiring low privilege authentication and low complexity, but limited to local denial of service only - no confidentiality or integrity impact. The EPSS score of 0.02% at the 5th percentile strongly contradicts the CVSS rating, indicating security researchers assess actual exploitation probability as minimal. This discrepancy suggests the UAF condition requires precise timing or specific kernel configurations to trigger. No indicators confirm active exploitation (no KEV status, no POC identified). This is characteristic of memory safety issues that are difficult to weaponize reliably into consistent denial of service. Defense-in-depth through Linux distributions' standard security hardening (SMACK, SELinux, AppArmor) further constrains practical exploitation from low-privilege users.

Exploit ScenarioDerived

A local low-privilege user on a system with SPI hardware monitors device bind/unbind operations through sysfs. By rapidly writing to the driver_override sysfs node while triggering device probe via hot-plug or module load, the attacker creates a race condition where __driver_attach() reads a freed driver_override pointer, causing a kernel panic (denial of service). The attack succeeds only if timing aligns precisely with the probe callback execution window, which is why exploitation is unreliable and rarely observed in practice.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Apr 28, 2026

Use-after-free vulnerability in the Linux kernel SPI subsystem allows local authenticated attackers to cause denial of service by exploiting unsynchronized access to the driver_override field during device probe operations. The vulnerability occurs because __driver_attach() calls the bus match() callback without holding the device lock, creating a race condition when driver_override is accessed without proper synchronization. CVSS score of 5.5 reflects local attack vector with low complexity and high availability impact. EPSS exploitation probability is minimal at 0.02%, suggesting this is a localized memory safety issue rather than a widely-exploited attack vector.

RemediationAI

Apply the upstream kernel fix by updating to patched versions: Linux 6.18.21, 6.12.80, 6.19.11, or 7.0 final release. Administrators should prioritize patching systems with non-standard SPI hardware configurations. For systems unable to patch immediately, restrict local user access and shell accounts to trusted administrators only, as the vulnerability requires PR:L (low privilege authentication). Disable SPI driver probing via sysfs if the SPI subsystem is not actively used by applying device-tree or kernel command-line restrictions to unload unused SPI bus drivers. Monitor for UAF-related kernel warnings (KASAN, UBSAN if enabled) in kernel logs. Patches are available from Linux stable repositories at https://git.kernel.org/stable/c/ with the commit hashes listed above; verify the specific version number matches your kernel branch before applying.

Affected VersionsENISA

Linux patch: 6.18.21
Linux patch: 6.12.80
Linux patch: 6.19.11
Linux 5039563e7c25eccd7fec1de6706011009d1c5665 <eedf220442d13b6d97294e5b0ac8a2c38ee1a1a0
Linux 5039563e7c25eccd7fec1de6706011009d1c5665 <c73a58661a760373d08a6883af4f0bb5cc991a67
Linux patch: 7.0
Linux 4.20
Linux 5039563e7c25eccd7fec1de6706011009d1c5665 <cc34d77dd48708d810c12bfd6f5bf03304f6c824
Linux patch: 0
Linux 5039563e7c25eccd7fec1de6706011009d1c5665 <e0ae367a2de06c49aa1de6ec9b1ab6860bbb2cf0

Affected Packages

euvd linux no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The Linux kernel SPI bus subsystem manages device-to-driver binding through a probe mechanism that invokes match() callbacks. The vulnerability exists in the driver_override field handling, which is part of the device driver binding infrastructure. CWE-667 identifies this as an improper locking issue - specifically, the field is accessed without the device lock during __driver_attach() probe path, which is an intentional design choice for performance but creates a window for use-after-free (UAF) conditions. The fix migrates SPI to use the kernel's generic driver_override infrastructure from struct bus_type, which implements proper locking semantics internally. The SPI bus has a non-standard behavior of passing empty string instead of null to sysfs_emit() when driver_override is NULL, requiring special handling to maintain backward compatibility.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
SUSE MEDIUM
Red Hat 5.5 MEDIUM

Primary rating from NVD.

CVSS VectorNVD

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

Lifecycle Timeline

2
CVSS changed
Apr 28, 2026 - 13:07 NVD
5.5 (MEDIUM)
CVE Published
Apr 22, 2026 - 14:16 nvd
MEDIUM 5.5

DescriptionNVD

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

spi: use generic driver_override infrastructure

When a driver is probed through __driver_attach(), the bus' match() callback is called without the device lock held, thus accessing the driver_override field without a lock, which can cause a UAF.

Fix this by using the driver-core driver_override infrastructure taking care of proper locking internally.

Note that calling match() from __driver_attach() without the device lock held is intentional. [1]

Also note that we do not enable the driver_override feature of struct bus_type, as SPI - in contrast to most other buses - passes "" to sysfs_emit() when the driver_override pointer is NULL. Thus, printing "\n" instead of "(null)\n".

Threat Intelligence Overview

EPSS Score
0.0%
Top 95% exploitable
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation· derived
None
System Exposure· derived
Small
Automatable· derived
No
Human Impact· derived
Medium

Priority Score

28
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +28
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

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

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