{
  "cveId": "CVE-2025-39921",
  "url": "https://patchblox.com/security/cve/CVE-2025-39921",
  "summary": "CVE-2025-39921 is fixed in linux on 1 platform by DEBIAN-CVE-2025-39921 (version 6.16.6-1), released October 1, 2025. It is not reported as exploited. Patch Radar priority: Routine.",
  "title": "linux: In the Linux kernel, the following vulnerability has been resolved:  spi: microchip-core-qspi: stop checking viabilit...",
  "description": "In the Linux kernel, the following vulnerability has been resolved:  spi: microchip-core-qspi: stop checking viability of op-\u003Emax_freq in supports_op callback  In commit 13529647743d9 (\u0022spi: microchip-core-qspi: Support per spi-mem operation frequency switches\u0022) the logic for checking the viability of op-\u003Emax_freq in mchp_coreqspi_setup_clock() was copied into mchp_coreqspi_supports_op(). Unfortunately, op-\u003Emax_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.",
  "published": "2025-10-01T08:15:35Z",
  "severity": "medium",
  "cvss": 5.5,
  "cvssVector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
  "epss": 0.00187,
  "epssPercentile": 0.0836,
  "priority": "Routine",
  "priorityTier": 4,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "6.16.6-1",
      "fix": "DEBIAN-CVE-2025-39921",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2025-39921",
      "released": "2025-10-01T08:15:35Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-10T01:44:33Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}