CVE-2026-72298 — net: qrtr: fix 32-bit integer overflow in qrtr_endpoint_post()
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 960b08dd36de1e341e3eb43d1c547513e338f4f8 and < 3665e644ea081c4624a1637023b0de3b29f4ae04≥ ad9d24c9429e2159d1e279dc3a83191ccb4daf1d and < b609f7f46916c6b05585ca82455077198a23770f≥ ad9d24c9429e2159d1e279dc3a83191ccb4daf1d and < 242408b5b763c01288adf3113cbce84378a76e1a≥ ad9d24c9429e2159d1e279dc3a83191ccb4daf1d and < d0597074e99731fdad5593e4f6d056a3866f2cab≥ ad9d24c9429e2159d1e279dc3a83191ccb4daf1d and < 689b7267f8632b4661879dc323e26ebb60978afb≥ ad9d24c9429e2159d1e279dc3a83191ccb4daf1d and < 22100a8f73d4ae4f17697dae93d4e2e1d283a6ec≥ ad9d24c9429e2159d1e279dc3a83191ccb4daf1d and < 7f72c285f6d3bf63968a0344beee8ab1b370198b≥ ad9d24c9429e2159d1e279dc3a83191ccb4daf1d and < 20054869770c7df060c5ecee3e8bbf9029c47191 and 8 moreversion f8111c0d7ed42ede41a3d0d393b104de0730a8a6version 26b8d10703a9be45d6097946b2b4011f7dd2c56fversion 19892ab9c9d838e2e5a7744d36e4bb8b7c3292fe≥ 5.10.46 and < 5.10.261≥ 4.19.196 and < 4.20≥ 5.4.128 and < 5.5≥ 5.12.13 and < 5.13version 5.13 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 8.4 | CVSS 3.1 | High | 2.5 | 5.9 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database |
| 8.4 | CVSS 3.1 | High | — | — | Linux via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: 416baaa9-dc9f-4396-8d5f-8c081fb06d67) Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- Record published
- CVSS changed · 8.4
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/3665e644ea081c4624a1637023b0de3b29f4ae04
- git.kernel.org/stable/c/7f72c285f6d3bf63968a0344beee8ab1b370198b
- git.kernel.org/stable/c/20054869770c7df060c5ecee3e8bbf9029c47191
- git.kernel.org/stable/c/22100a8f73d4ae4f17697dae93d4e2e1d283a6ec
- git.kernel.org/stable/c/242408b5b763c01288adf3113cbce84378a76e1a
- git.kernel.org/stable/c/689b7267f8632b4661879dc323e26ebb60978afb
- git.kernel.org/stable/c/b609f7f46916c6b05585ca82455077198a23770f
- git.kernel.org/stable/c/d0597074e99731fdad5593e4f6d056a3866f2cab
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 12h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 12h
- Unknown CVE-2026-98428 ALSA: usb: 6fire: Avoid embedded URBs 1d
- Unknown CVE-2026-98431 RDMA/uverbs: Fix mmap_lock/disassociation_lock circular dependency 1d
- Unknown CVE-2026-98430 RDMA/efa: Keep admin queues alive while IRQ is registered 1d
- Unknown CVE-2026-98429 RDMA/efa: Keep EQ resources alive while IRQ is registered 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No FIRST EPSS score.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-72298 is "net: qrtr: fix 32-bit integer overflow in qrtr_endpoint_post()", rated High. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.4 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.