Skip to main content

Linux Kernel CVE-2026-46225

| EUVDEUVD-2026-32852 MEDIUM
2026-05-28 416baaa9-dc9f-4396-8d5f-8c081fb06d67 GHSA-fqv4-j66g-hgpv
5.5
CVSS 3.1 · NVD
View

Attack ChainAIDerived

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

  1. Access
    Gain local authenticated access
  2. Delivery
    Load or identify active rspi kernel module
  3. Exploit
    Trigger driver unbind during active DMA transfer
  4. Execution
    DMA resources freed before controller deregistration
  5. Persist
    Kernel accesses freed memory
  6. Impact
    Kernel panic / system crash (DoS)

Vulnerability Assessment

Exploitation Conditions

Exploitation requires: (1) authenticated local access with at least low-privilege credentials (CVSS PR:L); (2) the target system must have Renesas SPI controller hardware present and the rspi kernel module loaded; (3) the attacker must be able to trigger driver unbind, either via module unload (typically requiring CAP_SYS_MODULE or root-equivalent) or a hotplug event. The attack is limited to availability impact (DoS/kernel panic) with no confidentiality or integrity exposure. Non-Renesas hardware environments are entirely unexposed. Systems where module unloading is restricted (e.g., locked-down kernels with module signing and no local root) significantly reduce exploitability below what the CVSS PR:L score implies.

Impact

Real-world risk is low. The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H) requires local system access with at least low-privilege credentials, and scope is unchanged - meaning exploitation cannot pivot to other components or systems. The EPSS score of 0.02% (5th percentile) reflects negligible exploitation interest from the threat intelligence community. There is no CISA KEV listing and no publicly available exploit code, further reducing urgency. The vulnerability is hardware-specific, limited to systems that physically host Renesas SPI controller hardware (embedded, automotive, and IoT contexts), which significantly narrows the exposed population. The primary consequence is a kernel panic (DoS) with no confidentiality or integrity impact, contradicting the 'Information Disclosure' tag in source metadata - defenders should not treat this as a data-exfiltration risk. For general-purpose server or workstation environments without Renesas SPI hardware, this CVE is not applicable. Priority should be reserved for embedded/IoT Linux deployments on affected Renesas hardware platforms.

Exploit ScenarioDerived

A local user with at least low-privilege access on an embedded Linux system hosting Renesas SPI hardware triggers driver unbind - for example, by initiating a device hotplug event or unloading the rspi kernel module - while SPI DMA transfers are in-flight. The freed DMA memory is accessed by the still-registered SPI controller, causing a kernel null-pointer dereference or use-after-free, resulting in an immediate kernel panic and system crash. No public exploit code exists at time of analysis, and exploitation requires physical or authenticated local access to the affected system.

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 – Jun 10, 2026

Improper resource deregistration ordering in the Linux kernel's spi/rspi (Renesas SPI controller) driver causes a local denial-of-service condition during driver unbind. The rspi driver releases DMA resources before deregistering the SPI controller, creating a window where in-flight controller operations can reference freed memory, resulting in a kernel crash or panic. With CVSS availability impact rated High and EPSS at 0.02% (5th percentile), this is a low-probability but locally exploitable stability issue affecting systems with Renesas SPI hardware. No public exploit code and no CISA KEV listing have been identified at time of analysis.

RemediationAI

Upstream-released patched kernel versions confirm the fix across all active stable branches: upgrade to Linux 6.12.90, 6.6.140, 6.18.32, 7.0.9, or 7.1-rc1 (or later). The specific fix commits are available at https://git.kernel.org/stable/c/c5090db1b31de3ef4db0cda7e822ab49cb572292, https://git.kernel.org/stable/c/77defd64b405b680db73d767313fce770d368368, https://git.kernel.org/stable/c/9944fa6726afb1e6eb7e2212764e7da0c97f2dcc, https://git.kernel.org/stable/c/aee76c1dd189562c6678313caec12761f78a9ef3, and https://git.kernel.org/stable/c/fee6abd9845c3edd217b0e429d09f764f9a5693e. For systems that cannot be patched immediately, a compensating control is to blacklist or prevent unloading of the rspi kernel module (e.g., via /etc/modprobe.d/blacklist-rspi.conf adding 'install rspi /bin/true'), which eliminates the driver unbind path; the trade-off is loss of SPI controller functionality. Systems without Renesas SPI hardware are not exposed and require no action.

Affected VersionsENISA

Linux patch: 7.0.9
Linux patch: 6.6.140
Linux patch: 7.1-rc1
Linux patch: 6.18.32
Linux patch: 0
Linux 9e03d05eee4ca45ed12749ef6c26bf616262cdd2 <c5090db1b31de3ef4db0cda7e822ab49cb572292
Linux 9e03d05eee4ca45ed12749ef6c26bf616262cdd2 <77defd64b405b680db73d767313fce770d368368
Linux 9e03d05eee4ca45ed12749ef6c26bf616262cdd2 <9944fa6726afb1e6eb7e2212764e7da0c97f2dcc
Linux 9e03d05eee4ca45ed12749ef6c26bf616262cdd2 <aee76c1dd189562c6678313caec12761f78a9ef3
Linux 9e03d05eee4ca45ed12749ef6c26bf616262cdd2 <fee6abd9845c3edd217b0e429d09f764f9a5690e
Linux 3.14
Linux patch: 6.12.90

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 affected component is the spi/rspi driver in the Linux kernel, which manages Renesas Serial Peripheral Interface (SPI) controllers. During driver unbind (e.g., module removal or device hotplug events), the cleanup sequence must deregister the SPI controller first to drain pending transfers before releasing underlying DMA channel resources. The bug inverts this order, allowing the SPI subsystem to continue referencing DMA structures that have already been freed. CPE data confirms the affected product as cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*, with the vulnerability introduced at commit 9e03d05eee4ca45ed12749ef6c26bf616262cdd2 and present since at least Linux 3.14. Although no CWE is formally assigned, the root cause class most closely aligns with improper resource cleanup ordering, analogous to CWE-459 (Incomplete Cleanup) or CWE-416 (Use After Free), as freed DMA memory can be accessed by the still-registered controller. The 'Information Disclosure' tag in the source data conflicts with the CVSS confidentiality impact of C:N - this tag appears to be a mis-tagging and should not be treated as a confirmed confidentiality risk.

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

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

4
CVSS changed
Jun 10, 2026 - 19:07 NVD
5.5 (MEDIUM)
Patch available
May 28, 2026 - 12:01 EUVD
CVE Published
May 28, 2026 - 10:16 nvd
MEDIUM 5.5
CVE Published
May 28, 2026 - 10:16 nvd
UNKNOWN (no severity yet)

DescriptionNVD

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

spi: rspi: fix controller deregistration

Make sure to deregister the controller before releasing underlying resources like DMA during driver unbind.

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: Moderate
Product Status
openSUSE Tumbleweed Fixed
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

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