# CVE-2026-72298: net: qrtr: fix 32-bit integer overflow in qrtr_endpoint_post()

> A 32-bit integer overflow in the Linux kernel QRTR network module allows remote attackers to cause a kernel crash via crafted packets.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 16 Oct 2026
- **Also known as:** BELL-CVE-2026-72298, DEBIAN-CVE-2026-72298, GHSA-3c34-q5w8-c59m, UBUNTU-CVE-2026-72298

## What is CVE-2026-72298?

CVE-2026-72298 is a high-severity vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

net: qrtr: fix 32-bit integer overflow in qrtr_endpoint_post()

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.

## Which versions are affected by CVE-2026-72298?


## How do I fix CVE-2026-72298?

Apply the vendor's patch.

## Is CVE-2026-72298 being exploited?

There is no known exploitation of CVE-2026-72298 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-72298 and fix it if it is affected.

What it is: CVE-2026-72298 is a high-severity vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-72298 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-72298/ (Markdown: https://insights.sbomify.com/CVE-2026-72298/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-72298
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-72298
- OSV: https://osv.dev/vulnerability/CVE-2026-72298

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-72298/
Summaries are generated and may contain mistakes; the official description above is the record.