Answer in brief
CVE-2025-39921 records a Medium severity (CVSS 5.5) vulnerability in spi: microchip-core-qspi: stop checking viability of op->max_freq in supports_op callback. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=d29f749d5202605dbb7480791e6841487d8afb77 <4ad071e3d57967f7ab483aed0687468bc1d9e9ce || >=13529647743d906ed3cf991f1d77727e7ff1fb6f <ac8a13f35d5b8996582b3f97b924838a5c570c18 || >=13529647743d906ed3cf991f1d77727e7ff1fb6f <89e7353f522f5cf70cb48c01ce2dcdcb275b8022 | 4ad071e3d57967f7ab483aed0687468bc1d9e9ce, ac8a13f35d5b8996582b3f97b924838a5c570c18, 89e7353f522f5cf70cb48c01ce2dcdcb275b8022 |
| Linux/Linuxgeneric | 6.14 | Not reported |
Published upstream
Oct 1, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 21, 2026
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.
Quoted source text, attributed separately from HOL analysis.