CVE-2025-71285 Details
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.
A vulnerability has been identified in the Linux kernel's QRTR (Qualcomm Remote Procedure Call Transport) driver, specifically related to the MHI (Mobile Host Interface) auto-queue feature for IPCR (Inter-Processor Communication Router) downlink channels. This feature, while simplifying driver design, creates a race condition where the 'dl_callback' may be invoked before the client driver is fully initialized, leading to a null pointer dereference. This issue has been reported on Qualcomm X1E80100 CRD machines during boot. The vulnerability arises because client drivers might call MHI queue APIs before their internal structures are ready, causing similar null pointer dereferences. To address this, the MHI auto-queue feature has been disabled, allowing the QRTR driver to manage received buffers manually. The fix involves removing the auto-queue flag from affected controller drivers and has been applied in the Linux kernel stable tree.
The vulnerability has been addressed by removing the MHI auto-queue feature for IPCR downlink channels, allowing the QRTR driver to manage received buffers manually. This fix is available in the latest version of the Linux kernel.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Nov 5, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-476 | NULL Pointer Dereference | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 5.15.63, < 5.16 >= 5.17, < 6.18.17 >= 6.19, < 6.19.6 |
CPE
Remediation
| |
Change History
7 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Nov 5, 2026 | CVE Modified | CISA-ADP |
| Oct 30, 2026 | CVE Modified | kernel.org |
| Oct 21, 2026 | CVE Modified | kernel.org |
| Oct 14, 2026 | CVE Translated | [email protected] |
| Jun 17, 2026 | CVE Modified | kernel.org |
| May 12, 2026 | Initial Analysis | [email protected] |
| May 6, 2026 | New CVE Received | kernel.org |