{
  "cveId": "CVE-2025-71285",
  "url": "https://patchblox.com/security/cve/CVE-2025-71285",
  "summary": "CVE-2025-71285 is fixed in linux on 1 platform, first by DEBIAN-CVE-2025-71285, released May 15, 2026. It is not reported as exploited. Patch Radar priority: Routine.",
  "title": "net: qrtr: Drop the MHI auto_queue feature for IPCR DL channels",
  "description": "In the Linux kernel, the following vulnerability has been resolved:  net: qrtr: Drop the MHI auto_queue feature for IPCR DL channels  MHI stack offers the \u0027auto_queue\u0027 feature, which allows the MHI stack to auto queue the buffers for the RX path (DL channel). Though this feature simplifies the client driver design, it introduces race between the client drivers and the MHI stack. For instance, with auto_queue, the \u0027dl_callback\u0027 for the DL channel may get called before the client driver is fully probed. This means, by the time the dl_callback gets called, the client driver\u0027s structures might not be initialized, leading to NULL ptr dereference.  Currently, the drivers have to workaround this issue by initializing the internal structures before calling mhi_prepare_for_transfer_autoqueue(). But even so, there is a chance that the client driver\u0027s internal code path may call the MHI queue APIs before mhi_prepare_for_transfer_autoqueue() is called, leading to similar NULL ptr dereference. This issue has been reported on the Qcom X1E80100 CRD machines affecting boot.  So to properly fix all these races, drop the MHI \u0027auto_queue\u0027 feature altogether and let the client driver (QRTR) manage the RX buffers manually. In the QRTR driver, queue the RX buffers based on the ring length during probe and recycle the buffers in \u0027dl_callback\u0027 once they are consumed. This also warrants removing the setting of \u0027auto_queue\u0027 flag from controller drivers.  Currently, this \u0027auto_queue\u0027 feature is only enabled for IPCR DL channel. So only the QRTR client driver requires the modification.",
  "published": "2026-05-06T12:16:27Z",
  "severity": "Moderate",
  "cvss": 5.5,
  "cvssVector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
  "cwe": "NULL Pointer Dereference",
  "epss": 0.00162,
  "epssPercentile": 0.05474,
  "priority": "Routine",
  "priorityTier": 4,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "vendorAdvisory": "https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-71285",
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 13.5 (trixie)",
      "fixedVersion": "6.12.115-2",
      "fix": "DEBIAN-CVE-2025-71285",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2025-71285",
      "released": "2026-05-15T16:01:09Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "6.19.6-1",
      "fix": "DEBIAN-CVE-2025-71285",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2025-71285",
      "released": "2026-05-15T16:01:09Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-08T13:06:02Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}