CVE-2025-71285 (GCVE-0-2025-71285)

Vulnerability from cvelistv5 – Published: 2026-05-06 11:32 – Updated: 2026-05-11 21:57
VLAI?
Title
net: qrtr: Drop the MHI auto_queue feature for IPCR DL channels
Summary
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 'auto_queue' 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 'dl_callback' 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's 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's 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 'auto_queue' 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 'dl_callback' once they are consumed. This also warrants removing the setting of 'auto_queue' flag from controller drivers. Currently, this 'auto_queue' feature is only enabled for IPCR DL channel. So only the QRTR client driver requires the modification.
Severity ?
No CVSS data available.
Assigner
References
Impacted products
Vendor Product Version
Linux Linux Affected: 227fee5fc99eeb74d43bf68832f6d59d30ac07d8 , < 7bdff9b9b0c65ac7105416fe3a40686832515e20 (git)
Affected: 227fee5fc99eeb74d43bf68832f6d59d30ac07d8 , < 8c464e00e0754e016816b1860fa9592dcad80eb2 (git)
Affected: 227fee5fc99eeb74d43bf68832f6d59d30ac07d8 , < 51731792a25cb312ca94cdccfa139eb46de1b2ef (git)
Affected: c682fb70a7dfc25b848a4ff3a385b0471b470606 (git)
Create a notification for this product.
Linux Linux Affected: 5.17
Unaffected: 0 , < 5.17 (semver)
Unaffected: 6.18.17 , ≤ 6.18.* (semver)
Unaffected: 6.19.6 , ≤ 6.19.* (semver)
Unaffected: 7.0 , ≤ * (original_commit_for_fix)
Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/accel/qaic/mhi_controller.c",
            "drivers/bus/mhi/host/pci_generic.c",
            "drivers/net/wireless/ath/ath11k/mhi.c",
            "drivers/net/wireless/ath/ath12k/mhi.c",
            "net/qrtr/mhi.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "7bdff9b9b0c65ac7105416fe3a40686832515e20",
              "status": "affected",
              "version": "227fee5fc99eeb74d43bf68832f6d59d30ac07d8",
              "versionType": "git"
            },
            {
              "lessThan": "8c464e00e0754e016816b1860fa9592dcad80eb2",
              "status": "affected",
              "version": "227fee5fc99eeb74d43bf68832f6d59d30ac07d8",
              "versionType": "git"
            },
            {
              "lessThan": "51731792a25cb312ca94cdccfa139eb46de1b2ef",
              "status": "affected",
              "version": "227fee5fc99eeb74d43bf68832f6d59d30ac07d8",
              "versionType": "git"
            },
            {
              "status": "affected",
              "version": "c682fb70a7dfc25b848a4ff3a385b0471b470606",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/accel/qaic/mhi_controller.c",
            "drivers/bus/mhi/host/pci_generic.c",
            "drivers/net/wireless/ath/ath11k/mhi.c",
            "drivers/net/wireless/ath/ath12k/mhi.c",
            "net/qrtr/mhi.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "5.17"
            },
            {
              "lessThan": "5.17",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.17",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.19.*",
              "status": "unaffected",
              "version": "6.19.6",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.0",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.17",
                  "versionStartIncluding": "5.17",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.19.6",
                  "versionStartIncluding": "5.17",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.0",
                  "versionStartIncluding": "5.17",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionStartIncluding": "5.15.63",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: qrtr: Drop the MHI auto_queue feature for IPCR DL channels\n\nMHI stack offers the \u0027auto_queue\u0027 feature, which allows the MHI stack to\nauto queue the buffers for the RX path (DL channel). Though this feature\nsimplifies the client driver design, it introduces race between the client\ndrivers and the MHI stack. For instance, with auto_queue, the \u0027dl_callback\u0027\nfor the DL channel may get called before the client driver is fully probed.\nThis means, by the time the dl_callback gets called, the client driver\u0027s\nstructures might not be initialized, leading to NULL ptr dereference.\n\nCurrently, the drivers have to workaround this issue by initializing the\ninternal structures before calling mhi_prepare_for_transfer_autoqueue().\nBut even so, there is a chance that the client driver\u0027s internal code path\nmay call the MHI queue APIs before mhi_prepare_for_transfer_autoqueue() is\ncalled, leading to similar NULL ptr dereference. This issue has been\nreported on the Qcom X1E80100 CRD machines affecting boot.\n\nSo to properly fix all these races, drop the MHI \u0027auto_queue\u0027 feature\naltogether and let the client driver (QRTR) manage the RX buffers manually.\nIn the QRTR driver, queue the RX buffers based on the ring length during\nprobe and recycle the buffers in \u0027dl_callback\u0027 once they are consumed. This\nalso warrants removing the setting of \u0027auto_queue\u0027 flag from controller\ndrivers.\n\nCurrently, this \u0027auto_queue\u0027 feature is only enabled for IPCR DL channel.\nSo only the QRTR client driver requires the modification."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-05-11T21:57:14.720Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/7bdff9b9b0c65ac7105416fe3a40686832515e20"
        },
        {
          "url": "https://git.kernel.org/stable/c/8c464e00e0754e016816b1860fa9592dcad80eb2"
        },
        {
          "url": "https://git.kernel.org/stable/c/51731792a25cb312ca94cdccfa139eb46de1b2ef"
        }
      ],
      "title": "net: qrtr: Drop the MHI auto_queue feature for IPCR DL channels",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2025-71285",
    "datePublished": "2026-05-06T11:32:18.774Z",
    "dateReserved": "2026-05-06T11:31:45.509Z",
    "dateUpdated": "2026-05-11T21:57:14.720Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2025-71285",
      "date": "2026-05-22",
      "epss": "0.00013",
      "percentile": "0.02279"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2025-71285\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2026-05-06T12:16:27.613\",\"lastModified\":\"2026-05-12T21:25:04.157\",\"vulnStatus\":\"Analyzed\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nnet: qrtr: Drop the MHI auto_queue feature for IPCR DL channels\\n\\nMHI stack offers the \u0027auto_queue\u0027 feature, which allows the MHI stack to\\nauto queue the buffers for the RX path (DL channel). Though this feature\\nsimplifies the client driver design, it introduces race between the client\\ndrivers and the MHI stack. For instance, with auto_queue, the \u0027dl_callback\u0027\\nfor the DL channel may get called before the client driver is fully probed.\\nThis means, by the time the dl_callback gets called, the client driver\u0027s\\nstructures might not be initialized, leading to NULL ptr dereference.\\n\\nCurrently, the drivers have to workaround this issue by initializing the\\ninternal structures before calling mhi_prepare_for_transfer_autoqueue().\\nBut even so, there is a chance that the client driver\u0027s internal code path\\nmay call the MHI queue APIs before mhi_prepare_for_transfer_autoqueue() is\\ncalled, leading to similar NULL ptr dereference. This issue has been\\nreported on the Qcom X1E80100 CRD machines affecting boot.\\n\\nSo to properly fix all these races, drop the MHI \u0027auto_queue\u0027 feature\\naltogether and let the client driver (QRTR) manage the RX buffers manually.\\nIn the QRTR driver, queue the RX buffers based on the ring length during\\nprobe and recycle the buffers in \u0027dl_callback\u0027 once they are consumed. This\\nalso warrants removing the setting of \u0027auto_queue\u0027 flag from controller\\ndrivers.\\n\\nCurrently, this \u0027auto_queue\u0027 feature is only enabled for IPCR DL channel.\\nSo only the QRTR client driver requires the modification.\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\",\"baseScore\":5.5,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":1.8,\"impactScore\":3.6}]},\"weaknesses\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-476\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"5.15.63\",\"versionEndExcluding\":\"5.16\",\"matchCriteriaId\":\"60ACBB16-9DB7-4B68-AF39-342F3BA4775E\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"5.17\",\"versionEndExcluding\":\"6.18.17\",\"matchCriteriaId\":\"9E1D818B-7FC7-4E36-AC6B-517B11C9D765\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.19\",\"versionEndExcluding\":\"6.19.6\",\"matchCriteriaId\":\"373EEEDA-FAA1-4FB4-B6ED-DB4DD99DBE67\"}]}]}],\"references\":[{\"url\":\"https://git.kernel.org/stable/c/51731792a25cb312ca94cdccfa139eb46de1b2ef\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/7bdff9b9b0c65ac7105416fe3a40686832515e20\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/8c464e00e0754e016816b1860fa9592dcad80eb2\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]}]}}"
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.