CVE-2025-71285: net: qrtr: Drop the MHI auto_queue feature for IPCR DL channels
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.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue is a race in a Qualcomm-related messaging path. On affected systems, the kernel may call driver receive handling before the driver is ready, causing a NULL pointer crash. The public record specifically mentions boot impact on Qcom X1E80100 CRD machines.
Executive priority
Treat this as targeted operational risk, not broad internet-facing urgency. Prioritize fleets using affected Qualcomm Linux platforms because impact may be boot failure or kernel crash; otherwise monitor vendor kernel updates.
Technical view
The MHI auto_queue feature can invoke the IPCR DL channel callback before QRTR client driver structures are initialized. The resolved change removes auto_queue for this path, has QRTR queue and recycle RX buffers manually, and removes auto_queue flag use from controller drivers.
Likely exposure
Exposure appears limited to Linux kernels using the QRTR client driver with MHI IPCR DL channels. The source says auto_queue was only enabled for IPCR DL, and the reported impact was on Qcom X1E80100 CRD machines during boot.
Exploitation context
No active exploitation is supported by the supplied sources, and KEV is false. The record describes a reliability or denial-of-service style crash from a race condition, not a demonstrated attacker-controlled exploit path.
Researcher notes
The supplied record lacks CVSS, CWE, and exploitability detail. Analysis should stay scoped to the documented MHI auto_queue race, QRTR RX buffer handling change, and reported Qcom X1E80100 CRD boot failure.
Mitigation direction
Apply Linux stable updates containing the referenced QRTR/MHI fix commits.
Check distribution or device-vendor advisories for backported kernel packages.
Prioritize Qualcomm X1E80100 or QRTR-over-MHI platforms for update testing.
Avoid inventing local workarounds; follow kernel or vendor guidance if patching is delayed.
Validation and detection
Inventory Linux kernel versions and vendor patch levels across affected hardware.
Confirm whether systems use QRTR with MHI IPCR DL channels.
Review boot logs for NULL pointer dereference symptoms in QRTR or MHI paths.
Verify the referenced stable commits or vendor backports are present.
Run reboot regression tests on Qualcomm platforms after updating.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-71285 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
4Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
May 6, 2026, 11:32 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.