CVE-2025-40005: spi: cadence-quadspi: Implement refcount to handle unbind during busy

Published Oct 20, 2025
·
Updated

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

spi: cadence-quadspi: Implement refcount to handle unbind during busy

driver support indirect read and indirect write operation with assumption no force device removal(unbind) operation. However force device removal(removal) is still available to root superuser.

Unbinding driver during operation causes kernel crash. This changes ensure driver able to handle such operation for indirect read and indirect write by implementing refcount to track attached devices to the controller and gracefully wait and until attached devices remove operation completed before proceed with removal operation.

Affected Software

13 affected componentsFixes available
Linux Kernel
Microsoft azl3 kernel 6.6.104.2-4
Microsoft azl3 kernel 6.6.96.2-2
Microsoft azl3 kernel 6.6.112.1-2
Microsoft azl3 kernel 6.6.117.1-1
Linux Linux kernel>=5.9<6.6.125
Linux Linux kernel>=6.7<6.16.10
Linux Linux kernel=6.17-rc1
Linux Linux kernel=6.17-rc2
Linux Linux kernel=6.17-rc3
Linux Linux kernel=6.17-rc4
Microsoft azl3 kernel 6.6.121.1-1
Microsoft azl3 kernel 6.6.119.3-1

Event History

Oct 20, 2025
CVE Published
via MITRE·03:26 PM
Data Sourced
via MITRE·03:26 PM
Description
Data Sourced
via NVD·04:15 PM
RemedyDescriptionSeverityAffected Software
Oct 22, 2025
Data Sourced
via Microsoft·01:01 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·01:01 AM
Affected Software
Updated
via Microsoft·08:01 AM
DescriptionSeverity
Updated
via Microsoft·08:01 AM
Affected Software

Frequently Asked Questions

1

What is the severity of CVE-2025-40005?

CVE-2025-40005 has been classified with a medium severity level due to the potential for race conditions when unbinding busy devices.

2

How do I fix CVE-2025-40005?

To fix CVE-2025-40005, update your Linux kernel to the latest version where the vulnerability has been patched.

3

Which systems are affected by CVE-2025-40005?

CVE-2025-40005 affects various versions of the Linux kernel and specifically Microsoft azl3 kernels 6.6.104.2-4 and 6.6.96.2-2.

4

What type of vulnerability is CVE-2025-40005?

CVE-2025-40005 is a race condition vulnerability that can occur during the unbinding of devices that are still in use.

5

Is there a workaround for CVE-2025-40005?

The best approach for CVE-2025-40005 is to apply the recommended patches; however, avoiding forced removal of devices may provide a temporary workaround.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203