Kernel memory disclosure via unchecked ATM traffic classes
Published Aug 15, 2026 · Updated Aug 15, 2026
Out-of-bounds read in the Linux kernel ATM module allows local users to disclose kernel memory through invalid QoS traffic classes. The check_tp() path accepts values above ATM_ANYCLASS, SO_ATMQOS stores them in vcc->qos, and pvc_info() later uses them to index class_name[]. Exploitation requires local low-privileged access to set ATM QoS and read /proc/net/atm/pvc; no memory write or code execution is reported.
Summary
What happened
Out-of-bounds read in the Linux kernel ATM module allows local users to disclose kernel memory through invalid QoS traffic classes. The check_tp() path accepts values above ATM_ANYCLASS, SO_ATMQOS stores them in vcc->qos, and pvc_info() later uses them to index class_name[]. Exploitation requires local low-privileged access to set ATM QoS and read /proc/net/atm/pvc; no memory write or code execution is reported.
The record
- CVE
- CVE-2026-72297
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-125
- Attack vector
- local
- Privileges
- authenticated
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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <15444b57fdc6fc3f3e22a87f791ae5be81e6ecf5
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1a6dda72455b399ce9c1a12695471dc4d5c61add
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2b3e241729e87afed13ac0f666472d5d6ca42e87
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <367acd288bc6255e247cb1a1efbf5c6567cab423
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <513f820b3f0cf4462e17d84c39ed3948d061a6ea
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <806b7b6edc8446e8b94b706807a7090a14d47b5c
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <cdf19f380e46192e7084be559638aab1f6ed86a2
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e62adb157c2eaad9ad4867ec6cd9af5b9a51b1c7
- Affected versionversion=2.6.12
What conditions does exploitation require?
What is affected?
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