Skip to main content
VulnerabilityPublished Updated

CVE-2026-72241: Linux kernel · leds: uleds: Fix potential buffer overread

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in c19fe864f667afc49d1391d764e20b66555bcf7a : update Linux kernel when convenient.

Data as of 6 Nov 2026, 17:19 UTC

Severity
Unrated

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

  1. Disclosed: evidence found.

    CVE published 15 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ e381322b0190c1253d347de3f28b5c37756fb651, < c19fe864f667afc49d1391d764e20b66555bcf7a
Fixed in
  • c19fe864f667afc49d1391d764e20b66555bcf7a
LinuxLinuxAffected
  • ≥ e381322b0190c1253d347de3f28b5c37756fb651, < a91ac9fdac7385cbc98aeae55b4e5302125497a2
Fixed in
  • a91ac9fdac7385cbc98aeae55b4e5302125497a2
LinuxLinuxAffected
  • ≥ e381322b0190c1253d347de3f28b5c37756fb651, < a84c59121dfdc7b324f72dc5012aa8fe5e7d2d7b
Fixed in
  • a84c59121dfdc7b324f72dc5012aa8fe5e7d2d7b
LinuxLinuxAffected
  • ≥ e381322b0190c1253d347de3f28b5c37756fb651, < 263ccdd627caeda6e980ed3c6e32bb4fd6b380b1
Fixed in
  • 263ccdd627caeda6e980ed3c6e32bb4fd6b380b1
LinuxLinuxAffected
  • ≥ e381322b0190c1253d347de3f28b5c37756fb651, < 8bf529571cca60fb8af65d6d034bdbbc99a9127c
Fixed in
  • 8bf529571cca60fb8af65d6d034bdbbc99a9127c
LinuxLinuxAffected
  • ≥ e381322b0190c1253d347de3f28b5c37756fb651, < 6dd51d84a9502553e58beade72823258871b8111
Fixed in
  • 6dd51d84a9502553e58beade72823258871b8111

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

Community reviews

Loading reviews…