spi: microchip-core-qspi: stop checking viability of op->max_freq in supports_op callback
In the Linux kernel, the following vulnerability has been resolved: spi: microchip-core-qspi: stop checking viability of op->max_freq in supports_op callback In commit 13529647743d9 ("spi: microchip-core-qspi: Support per spi-mem operation frequency switches") the logic for checking the viability of op->max_freq in mchp_coreqspi_setup_clock() was copied into mchp_coreqspi_supports_op(). Unfortunately, op->max_freq is not valid when this function is called during probe but is instead zero. Accordingly, baud_rate_val is calculated to be INT_MAX due to division by zero, causing probe of the attached memory device to fail. Seemingly spi-microchip-core-qspi was the only driver that had such a modification made to its supports_op callback when the per_op_freq capability was added, so just remove it to restore prior functionality.
CVE-2025-39921
Primary source · Revision 1
Imported from structured advisory data. Source references identify upstream records or fields; verify affected versions and your deployed configuration.
Security context
Source reference: cve:CVE-2025-39921
Linux
Source reference: /containers/cna/affected/0/product
- Affected versions
- Not stated in this record
- Fixed versions
- Not stated in this record
- Prerequisites
- Not stated in this record
Linux
Source reference: /containers/cna/affected/1/product
- Affected versions
- Not stated in this record
- Fixed versions
- Not stated in this record
- Prerequisites
- Not stated in this record
Structured affected-version data
Original package identities and version rules from this source.
[
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"product": "Linux",
"versions": [
{
"status": "affected",
"version": "d29f749d5202605dbb7480791e6841487d8afb77",
"lessThan": "4ad071e3d57967f7ab483aed0687468bc1d9e9ce",
"versionType": "git"
},
{
"status": "affected",
"version": "13529647743d906ed3cf991f1d77727e7ff1fb6f",
"lessThan": "ac8a13f35d5b8996582b3f97b924838a5c570c18",
"versionType": "git"
},
{
"status": "affected",
"version": "13529647743d906ed3cf991f1d77727e7ff1fb6f",
"lessThan": "89e7353f522f5cf70cb48c01ce2dcdcb275b8022",
"versionType": "git"
}
],
"programFiles": [
"drivers/spi/spi-microchip-core-qspi.c"
],
"defaultStatus": "unaffected"
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"product": "Linux",
"versions": [
{
"status": "affected",
"version": "6.14"
},
{
"status": "unaffected",
"version": "0",
"lessThan": "6.14",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "6.16.6",
"versionType": "semver",
"lessThanOrEqual": "6.16.*"
},
{
"status": "unaffected",
"version": "6.17",
"versionType": "original_commit_for_fix",
"lessThanOrEqual": "*"
}
],
"programFiles": [
"drivers/spi/spi-microchip-core-qspi.c"
],
"defaultStatus": "affected"
}
]- Related CVEs
- CVE-2025-39921
Source reference:
/cveMetadata/cveId
Publisher severity
No explicit severity was provided.
- Event
- #46030 · Revision 1
- Added to Heist Feed
- Publisher date