Skip to main content
Mallory
MediumVulnerability

CVE-2025-40005: Linux Cadence QSPI Driver Unbind Race Denial of Service

Published Oct 20, 2025 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS5.5Medium · v3.1
EPSS0.20%10th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Linux
IdentifiersCVE-2025-40005CWE-362

CVE-2025-40005 is a race condition in the Linux kernel Cadence QuadSPI SPI controller driver. The driver supported indirect read and indirect write operations without coordinating controller removal with devices actively attached to the controller. A forced driver unbind while either operation is in progress can cause the kernel to access removal-affected state and crash. The fix adds reference counting for attached devices and makes controller removal wait for attached-device removal activity to complete before proceeding.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

A successful trigger causes a kernel crash, resulting in a local denial of service. The available information does not establish arbitrary code execution, information disclosure, or privilege escalation for this specific flaw.

Mitigation

If you can’t patch tonight, do this now.

Restrict access to driver unbind and forced device-removal interfaces to trusted administrators. Do not unbind or remove the Cadence QuadSPI driver while indirect read or write operations are active, and use operational controls to prevent device removal during active controller I/O.

Remediation

Patch, then assume compromise.

Upgrade to a Linux kernel version supplied by the relevant vendor that includes the Cadence QuadSPI reference-counting fix for CVE-2025-40005. Reboot into the updated kernel after installation.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
LinuxLinux Kerneloperating_system
FAQ

Frequently asked questions

Is CVE-2025-40005 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2025-40005 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-40005?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2025-40005.
Is there a patch for CVE-2025-40005?
Upgrade to a Linux kernel version supplied by the relevant vendor that includes the Cadence QuadSPI reference-counting fix for CVE-2025-40005. Reboot into the updated kernel after installation.
What products are affected by CVE-2025-40005?
Linux Kernel.
How severe is CVE-2025-40005?
CVE-2025-40005 has a CVSS v3.1 score of 5.5 (Medium) and an EPSS score of 0.20% (10th percentile) as of Sep 25, 2026.
Activity feed

Recent activity

18 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.