PT-2026-37450 · Linux · Linux
Published
2026-05-06
·
Updated
2026-05-06
·
CVE-2025-71285
None
No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
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.
Found an issue in the description? Have something to add? Feel free to write us 👾
Related Identifiers
Affected Products
Linux