cveboard RSS feed

CVE-2025-71285

CVE.org · Published

Historical CVEsJSONAI instructions

Record status
Published
Identifier year (not publication year)
2025
Source publication
Source updated
Imported by cveboard
Source snapshot
cve_2026-10-24_midnight_baseline ·

Plain text

CNA source text (English)

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.

Scoped product and version facts

Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.

Exploitation unknown; this catalogue does not assess exploitation.

Linux

Vendor
Linux
Product
Linux
Platforms
Unknown
Default status
unaffected
Linux · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
227fee5fc99eeb74d43bf68832f6d59d30ac07d8affectedgitab0bdaf7a7f4f83b947193563f2a483ab87f72dbUnavailableNone listed
227fee5fc99eeb74d43bf68832f6d59d30ac07d8affectedgit8e130ff078892fa5a6bf272ced7565af58d98a85UnavailableNone listed
227fee5fc99eeb74d43bf68832f6d59d30ac07d8affectedgit7bdff9b9b0c65ac7105416fe3a40686832515e20UnavailableNone listed
227fee5fc99eeb74d43bf68832f6d59d30ac07d8affectedgit8c464e00e0754e016816b1860fa9592dcad80eb2UnavailableNone listed
227fee5fc99eeb74d43bf68832f6d59d30ac07d8affectedgit51731792a25cb312ca94cdccfa139eb46de1b2efUnavailableNone listed
c682fb70a7dfc25b848a4ff3a385b0471b470606affectedgitUnavailableUnavailableNone listed
5.15.63affectedsemver5.16UnavailableNone listed

Linux

Vendor
Linux
Product
Linux
Platforms
Unknown
Default status
affected
Linux · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
5.17affectedUnavailableUnavailableUnavailableNone listed
0unaffectedsemver5.17UnavailableNone listed
6.6.160unaffectedsemverUnavailable6.6.*None listed
6.12.114unaffectedsemverUnavailable6.12.*None listed
6.18.17unaffectedsemverUnavailable6.18.*None listed
6.19.6unaffectedsemverUnavailable6.19.*None listed
7.0unaffectedoriginal_commit_for_fixUnavailable*None listed