CVE-2026-72241: Linux kernel · leds: uleds: Fix potential buffer overread
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in c19fe864f667afc49d1391d764e20b66555bcf7a : update Linux kernel when convenient.
Data as of 6 Nov 2026, 17:19 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-06.
- Patch
- Available – fixed in c19fe864f667afc49d1391d764e20b66555bcf7a, a91ac9fdac7385cbc98aeae55b4e5302125497a2, a84c59121dfdc7b324f72dc5012aa8fe5e7d2d7b +5
Exploitation evidence
Disclosed: evidence found.
CVE published 15 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
Description
In the Linux kernel, the following vulnerability has been resolved: leds: uleds: Fix potential buffer overread The name string supplied by userspace is not guaranteed to be null-terminated, so using strchr() on it might result in a buffer overread. The same thing will happen when said string is used by the LED class device. Fix this by using strnchr() instead and explicitly check that the name string is properly null-terminated.
References
- git.kernel.org/stable/c/a84c59121dfdc7b324f72dc5012aa8fe5e7d2d7b (opens in a new tab)
- git.kernel.org/stable/c/5bb89e23729f3a59592d699a437bb001f24b8f67 (opens in a new tab)
- git.kernel.org/stable/c/5ad6f6c9209e5777b896def9876708853ae26d0d (opens in a new tab)
- git.kernel.org/stable/c/8bf529571cca60fb8af65d6d034bdbbc99a9127c (opens in a new tab)
- git.kernel.org/stable/c/a91ac9fdac7385cbc98aeae55b4e5302125497a2 (opens in a new tab)
- git.kernel.org/stable/c/6dd51d84a9502553e58beade72823258871b8111 (opens in a new tab)
- git.kernel.org/stable/c/263ccdd627caeda6e980ed3c6e32bb4fd6b380b1 (opens in a new tab)
- git.kernel.org/stable/c/c19fe864f667afc49d1391d764e20b66555bcf7a (opens in a new tab)