Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-71285net: 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 '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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 6 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-71285, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.16% · top 95% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 227fee5fc99eeb74d43bf68832f6d59d30ac07d8 – < b7874c74bcc224fd586679e51b9ded65f66edc2a
    • affected 227fee5fc99eeb74d43bf68832f6d59d30ac07d8 – < ab0bdaf7a7f4f83b947193563f2a483ab87f72db
    • affected 227fee5fc99eeb74d43bf68832f6d59d30ac07d8 – < 8e130ff078892fa5a6bf272ced7565af58d98a85
    • affected 227fee5fc99eeb74d43bf68832f6d59d30ac07d8 – < 7bdff9b9b0c65ac7105416fe3a40686832515e20
    • affected 227fee5fc99eeb74d43bf68832f6d59d30ac07d8 – < 8c464e00e0754e016816b1860fa9592dcad80eb2
    • affected 227fee5fc99eeb74d43bf68832f6d59d30ac07d8 – < 51731792a25cb312ca94cdccfa139eb46de1b2ef
    • affected c682fb70a7dfc25b848a4ff3a385b0471b470606
    • affected 5.15.63 – < 5.16
  • Linux · Linux

    • affected 5.17
    • unaffected < 5.17
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.17 – ≤ 6.18.*
    • unaffected 6.19.6 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-71285 badge
[![CVE-2025-71285](https://cveledger.app/badge/CVE-2025-71285.svg)](https://cveledger.app/cve/CVE-2025-71285)

Record last updated .