Medium 5.5Published May 6, 2026

CVE-2025-71285net: qrtr: Drop the MHI auto_queue feature for IPCR DL channels

Updated under an hour ago (Oct 26, 2026, 9:00 PM ET)

Does this affect you?

It affects Linux and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for Linux

Exploited in the last 30 days

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.

CVSS: 5.5 MEDIUM (v3.1, NVD)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness (CWE): Not given
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: Linux
NVD analysis: Modified
Record last updated: Oct 21, 2026
First seen by InfoSec Signals: Oct 9, 2026

Affected products

Affected products

Linux Linux linux:linux (from the name)	from 227fee5fc99eeb74d43bf68832f6d59d30ac07d8 before ab0bdaf7a7f4f83b947193563f2a483ab87f72db; 227fee5fc99eeb74d43bf68832f6d59d30ac07d8 builds before 8e130ff078892fa5a6bf272ced7565af58d98a85; 227fee5fc99eeb74d43bf68832f6d59d30ac07d8 builds before 7bdff9b9b0c65ac7105416fe3a40686832515e20; 227fee5fc99eeb74d43bf68832f6d59d30ac07d8 builds before 8c464e00e0754e016816b1860fa9592dcad80eb2; from 227fee5fc99eeb74d43bf68832f6d59d30ac07d8 before 51731792a25cb312ca94cdccfa139eb46de1b2ef; c682fb70a7dfc25b848a4ff3a385b0471b470606; from 5.15.63 before 5.16	CNA record
linux linux_kernel linux:linux_kernel	from 5.15.63 before 5.16; from 5.17 before 6.18.17; from 6.19 before 6.19.6	NVD

References

References

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

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.