Local kernel crash via unterminated uleds name
Published Aug 15, 2026 · Updated Aug 15, 2026
Buffer overread in Linux kernel uleds 4.10 and later allows local users to trigger an out-of-bounds read via a crafted LED name. The uleds write path passes a fixed-size, userspace-supplied name without a guaranteed null terminator to strchr() and the LED class device, so both can scan beyond the 64-byte name array. Exploitation requires local low-privileged access to /dev/uleds; Red Hat bounds its score to a kernel crash, while the upstream record does not demonstrate returned kernel memory.
Summary
What happened
Buffer overread in Linux kernel uleds 4.10 and later allows local users to trigger an out-of-bounds read via a crafted LED name. The uleds write path passes a fixed-size, userspace-supplied name without a guaranteed null terminator to strchr() and the LED class device, so both can scan beyond the 64-byte name array. Exploitation requires local low-privileged access to /dev/uleds; Red Hat bounds its score to a kernel crash, while the upstream record does not demonstrate returned kernel memory.
The record
- CVE
- CVE-2026-72241
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-125, T1499
- 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=4.10
- Affected versionversion=e381322b0190c1253d347de3f28b5c37756fb651 <263ccdd627caeda6e980ed3c6e32bb4fd6b380b1
- Affected versionversion=e381322b0190c1253d347de3f28b5c37756fb651 <5ad6f6c9209e5777b896def9876708853ae26d0d
- Affected versionversion=e381322b0190c1253d347de3f28b5c37756fb651 <5bb89e23729f3a59592d699a437bb001f24b8f67
- Affected versionversion=e381322b0190c1253d347de3f28b5c37756fb651 <6dd51d84a9502553e58beade72823258871b8111
- Affected versionversion=e381322b0190c1253d347de3f28b5c37756fb651 <8bf529571cca60fb8af65d6d034bdbbc99a9127c
- Affected versionversion=e381322b0190c1253d347de3f28b5c37756fb651 <a84c59121dfdc7b324f72dc5012aa8fe5e7d2d7b
- Affected versionversion=e381322b0190c1253d347de3f28b5c37756fb651 <a91ac9fdac7385cbc98aeae55b4e5302125497a2
- Affected versionversion=e381322b0190c1253d347de3f28b5c37756fb651 <c19fe864f667afc49d1391d764e20b66555bcf7a
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.
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