CVE-2025-39921
Last modified
CVE-2025-39921 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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.. EPSS estimates a 0.12% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.14, < 6.16.6 | — |
| Linux | Linux Kernel | 6.17 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2025-39921?
How severe is CVE-2025-39921?
How do I fix CVE-2025-39921?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-39916In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-39917In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-39918In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-39919In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-3992A vulnerability has been found in TOTOLINK N150RT 3.4.0-B201…8.8
- CVE-2025-39920In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-39922In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2025-39923In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-39924In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-39925In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-39926In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-39927In the Linux kernel, the following vulnerability has been re…4.7
Are you affected by CVE-2025-39921?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
