Kernel memory exhaustion via timestamp ring leak
Published Aug 15, 2026 · Updated Aug 15, 2026
Memory leak in the Linux kernel's octeontx2-pf driver allows local users with administrative access to exhaust kernel memory. When timestamping is enabled, otx2_free_sq_res() tears down a send queue without passing sq->timestamps to qmem_free(), so each teardown retains its timestamp ring. Exploitation requires compatible Marvell OcteonTX2 hardware and repeated interface shutdown or device removal, and the bounded consequence is gradual memory exhaustion rather than data access or code execution.
Summary
What happened
Memory leak in the Linux kernel's octeontx2-pf driver allows local users with administrative access to exhaust kernel memory. When timestamping is enabled, otx2_free_sq_res() tears down a send queue without passing sq->timestamps to qmem_free(), so each teardown retains its timestamp ring. Exploitation requires compatible Marvell OcteonTX2 hardware and repeated interface shutdown or device removal, and the bounded consequence is gradual memory exhaustion rather than data access or code execution.
The record
- CVE
- CVE-2026-72448
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-401, T1499.001
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Aug 15, 2026CVE publishedPublication date reported by the CVE source.
- Aug 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.10
- Affected versionversion=c9c12d339d93366732112d7ff472958834bfc3c5 <19d2d36e193c3fb515c052a56bfc83d8ac7b6764
- Affected versionversion=c9c12d339d93366732112d7ff472958834bfc3c5 <3d45d40b872aec0073d4cf08956a6c9b87c5e396
- Affected versionversion=c9c12d339d93366732112d7ff472958834bfc3c5 <452ec5058ea4ed63adae8d6beeac9ee687fe8061
- Affected versionversion=c9c12d339d93366732112d7ff472958834bfc3c5 <a056db30de92945ff8ee6033096678bfbae878e3
- Affected versionversion=c9c12d339d93366732112d7ff472958834bfc3c5 <c642a530aaaeb9a3e356cedfe77955e7f983380e
- Affected versionversion=c9c12d339d93366732112d7ff472958834bfc3c5 <d6c0b0c802d3c49b86cad665a7f3790dc55a0394
- Affected versionversion=c9c12d339d93366732112d7ff472958834bfc3c5 <e68ada66afcae0bc2a7c06b43c5a9a081d29e7b4
- Affected versionversion=c9c12d339d93366732112d7ff472958834bfc3c5 <e8e9dff204e8d8553495893e1a44d2b5021648de
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo