CVE-2025-71285 json
net: qrtr: Drop the MHI auto_queue feature for IPCR DL channels
published 2026-05-06 6 mo ago modified 2026-11-05 3 d ago also EUVD-2025-209675
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 5%
- public exploits
- 0
- none known
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.
Patch / fix
- Linux Linux 5.16, 6.1.191, 6.6.160, 6.12.114, 6.18.17, 6.19.6, 7.0
- linux Debian 13 6.12.115-2
- linux Debian 14 6.19.6-1
debian advisories DEBIAN-CVE-2025-71285
- git.kernel.org/stable/c/b7874c74bcc224fd586679e51b9ded65f66edc2a commit
- git.kernel.org/stable/c/ab0bdaf7a7f4f83b947193563f2a483ab87f72db commit
- git.kernel.org/stable/c/8e130ff078892fa5a6bf272ced7565af58d98a85 commit
- git.kernel.org/stable/c/7bdff9b9b0c65ac7105416fe3a40686832515e20 commit
- git.kernel.org/stable/c/8c464e00e0754e016816b1860fa9592dcad80eb2 commit
- git.kernel.org/stable/c/51731792a25cb312ca94cdccfa139eb46de1b2ef commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-71285 updated cvss 5.5
kernel: net: qrtr: Drop the MHI auto_queue feature for IPCR DL channels
-
Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelaffected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 3 d ago
Exploit prediction
0.16% chance of exploitation in the next 30 days, higher than 5% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-476 NULL Pointer Dereference
- Technology feeds
References
- git.kernel.org /stable/c/b7874c74bcc224fd586679e51b9ded65f66edc2a
- git.kernel.org /stable/c/ab0bdaf7a7f4f83b947193563f2a483ab87f72db
- git.kernel.org /stable/c/8e130ff078892fa5a6bf272ced7565af58d98a85
-
git.kernel.org
/stable/c/7bdff9b9b0c65ac7105416fe3a40686832515e20
patch
-
git.kernel.org
/stable/c/8c464e00e0754e016816b1860fa9592dcad80eb2
patch
-
git.kernel.org
/stable/c/51731792a25cb312ca94cdccfa139eb46de1b2ef
patch
Sources
- CVE List CVE-2025-71285
- NVD CVE-2025-71285
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.