Look up another CVE · open CVE-2026-72298 in the interactive tracker
CVE-2026-72298
net: qrtr: fix 32-bit integer overflow in qrtr_endpoint_post()
Published 2026-08-15 (2 months ago) by the Linux kernel CNA. Subsystem net/qrtr. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2026-72298 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | fixed | 6.1.180-1 | Update the kernel and reboot. Fixed in 6.1.180-1. A running kernel keeps the old code until the machine restarts. |
| Debian 13trixie | fixed | 6.12.100-1 | Update the kernel and reboot. Fixed in 6.12.100-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.1.5-1 | Update the kernel and reboot. Fixed in 7.1.5-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.1.5-1 | Update the kernel and reboot. Fixed in 7.1.5-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
qrtr_endpoint_post() validates an incoming packet with if (!size || len != ALIGN(size, 4) + hdrlen) goto err; where size comes from the wire. On 32-bit, size_t is 32 bits and ALIGN(size, 4) wraps to 0 for size >= 0xfffffffd, so the check passes and skb_put_data(skb, data + hdrlen, size) writes past the hdrlen-sized skb and oopses the kernel. 64-bit is unaffected. This is the 32-bit residual of ad9d24c9429e2 ("net: qrtr: fix OOB Read in qrtr_endpoint_post"), which fixed only the 64-bit case. Reject any size that cannot fit the buffer before the ALIGN.
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
net/qrtr/af_qrtr.c
- What this is
- QUALCOMM IPC ROUTER (QRTR) DRIVERMAINTAINERS section matched on net/qrtr/ · linux-arm-msm@vger.kernel.org · Maintained
- Kernel module
- qrtr
Check it on the machine
grep -w CONFIG_QRTR /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
lsmod | grep -w qrtrPrints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.
Show whether Debian builds this, per release
Debian builds this, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed.
- bookwormMnot built on amd64/cloud-amd64, arm64/cloud-arm64
- trixieMnot built on amd64/cloud-amd64, arm64/cloud-arm64, armel/rpi, s390x/s390x
- forky, sidMnot built on amd64/cloud-amd64, arm64/cloud-arm64, s390x/s390x
- M
- a module where it is built at all; some flavours do not build it
- Build switch
- CONFIG_QRTR
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2026-08-15 (2 months ago)source
- CVSS
- 8.4 high
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.18%, higher than 7.6% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- net/qrtr
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 5.10.46 | 5.10.261 | 3665e644ea08 |
| 5.13 | 5.15.212 | b609f7f46916 |
| 5.13 | 6.1.178 | 242408b5b763 |
| 5.13 | 6.6.145 | d0597074e997 |
| 5.13 | 6.12.97 | 689b7267f863 |
| 5.13 | 6.18.40 | 22100a8f73d4 |
| 5.13 | 7.1.5 | 7f72c285f6d3 |
| 5.13 | 7.2 | 20054869770c |
| 4.19.196 | 0 | 0 |
| 5.4.128 | 0 | 0 |
| 5.12.13 | 0 | 0 |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:LAttack vector, local
- qrtr_endpoint_post() is only reachable via local injection paths—write()/io_submit to /dev/qrtr-tun or inbound SMD/MHI frames from the on-SoC modem/coprocessor; AF_QIPCRTR sendmsg never enters this function and QRTR is not an Internet-facing protocol.
- AC:LAttack complexity, low
- The attacker fully controls the wire size field and total packet length; on 32-bit kernels, setting size>=0xfffffffd with len equal to the header length deterministically wraps ALIGN() to bypass validation without races or special victim state.
- PR:NPrivileges required, none
- On Qualcomm deployments the primary path is QRTR_SMD/MHI, where the AP kernel accepts ipcrouter frames from the baseband without Linux credentials or QRTR authentication, so a malicious or compromised modem sender needs no AP privileges.
- UI:NUser interaction, none
- Exploitation requires delivering a single crafted QRTR packet to qrtr_endpoint_post(); no victim interaction such as mounting filesystems, opening files, or clicking prompts is needed.
- S:UScope, unchanged
- Impact is kernel heap corruption and denial of service on the application processor; it does not cross a VM/host boundary, IOMMU boundary, or other separate security authority.
- C:HConfidentiality impact, high
- Bypassing validation causes skb_put_data() to memcpy() ~4GB from a hdrlen-sized input buffer, performing slab out-of-bounds reads of adjacent kernel heap memory that can disclose sensitive data.
- I:HIntegrity impact, high
- The same skb_put_data() call performs skb_put() with the wrapped size, writing far beyond the len-sized skb allocation and corrupting adjacent slab objects, enabling potential control-flow hijacking.
- A:HAvailability impact, high
- The oversized skb_put_data() triggers skb_over_panic/kernel oops as documented in the fix commit, reliably crashing affected 32-bit kernels and causing denial of service.