Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CVE-2025-71285 — kernel

🟡 CVSS 5.5 — Medium ✅ No Known Exploit NVD
5.5
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

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.

How this vulnerability can be exploited

This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability high.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

  • Attack vector: Local — a local account, shell or session on the host is needed.
  • Attack complexity: Low — the attack works reliably, with no preparation.
  • Privileges required: Low — an ordinary user account is enough.
  • User interaction: None — nobody has to be tricked into anything.
  • Scope: Unchanged — the damage stays inside the vulnerable component.
  • Confidentiality impact: None.
  • Integrity impact: None.
  • Availability impact: High — total loss, or loss the attacker controls.

Affected software

CVE-2025-71285 is recorded against 2 packages.

  • kernel (from 6.19.0 up to 6.19.6)
  • linux-kernel (from 6.19 up to 6.19.6)

Timeline and source

Published on 6 May 2026 and last revised on 12 August 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.

References

git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
github.com (Advisory)
nvd.nist.gov (Advisory)
git.kernel.org (Package)

Other advisories for this package

kernel has other advisories on record. If you are patching this one, these are worth checking on the same host:

Details

Severity Medium
CVSS Score 5.5
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE N/A
Public Exploit ✅ No
Source NVD
Published 2026-05-06
Updated 2026-08-20
Modified 2026-08-12

Affected Packages

Software From version Fixed in
kernel 6.19.0 6.19.6
linux-kernel 6.19 6.19.6

Similar Threats

Vulnerability Monitoring

Track new vulnerabilities in kernel

CVE-2025-71285 is rated CVSS 5.5 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.

Set Up Free Alerts →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2025
✓