[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025102000-CVE-2025-40005-b351@gregkh>
Date: Mon, 20 Oct 2025 17:27:01 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-40005: spi: cadence-quadspi: Implement refcount to handle unbind during busy
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
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.
The Linux kernel CVE team has assigned CVE-2025-40005 to this issue.
Affected and fixed versions
===========================
Fixed in 6.16.10 with commit b7ec8a2b094a33d0464958c2cbf75b8f229098b0
Fixed in 6.17 with commit 7446284023e8ef694fb392348185349c773eefb3
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2025-40005
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/spi/spi-cadence-quadspi.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/b7ec8a2b094a33d0464958c2cbf75b8f229098b0
https://git.kernel.org/stable/c/7446284023e8ef694fb392348185349c773eefb3
Powered by blists - more mailing lists