In the Linux kernel, the following vulnerability has been resolved: leds: uleds: Fix potential buffer overread The name string supplied by userspace… (CVE-2026-72241)
A vulnerability in the Linux kernel's uleds component could cause a buffer overread due to improper handling of a userspace-supplied name string that may not be null-terminated. The issue arises from using strchr() on this string, which can read beyond the intended buffer. The vulnerability has been resolved by switching to strnchr() and explicitly checking for proper null-termination of the string.
AI Analysis
Technical Summary
CVE-2026-72241 addresses a buffer overread vulnerability in the Linux kernel's uleds driver. The root cause is that the name string provided by userspace is not guaranteed to be null-terminated, but the kernel code used strchr() to search this string, potentially reading beyond its allocated buffer. This same unsafe usage occurs when the string is used by the LED class device. The fix replaces strchr() with strnchr() and adds explicit checks to ensure the string is properly null-terminated, preventing buffer overread.
Potential Impact
The vulnerability could lead to a buffer overread in kernel space, which may cause information disclosure or kernel instability. However, no specific exploitation details or known active exploits are reported. The impact is limited to the Linux kernel's uleds subsystem handling of user-supplied strings.
Mitigation Recommendations
A fix has been implemented in the Linux kernel by replacing strchr() with strnchr() and adding explicit null-termination checks on the userspace-supplied name string. Users should apply the official kernel updates that include this fix once available. Patch status is not explicitly confirmed in the provided data; check the vendor or Linux kernel advisories for the exact fixed versions and update accordingly.
In the Linux kernel, the following vulnerability has been resolved: leds: uleds: Fix potential buffer overread The name string supplied by userspace… (CVE-2026-72241)
Description
A vulnerability in the Linux kernel's uleds component could cause a buffer overread due to improper handling of a userspace-supplied name string that may not be null-terminated. The issue arises from using strchr() on this string, which can read beyond the intended buffer. The vulnerability has been resolved by switching to strnchr() and explicitly checking for proper null-termination of the string.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-72241 addresses a buffer overread vulnerability in the Linux kernel's uleds driver. The root cause is that the name string provided by userspace is not guaranteed to be null-terminated, but the kernel code used strchr() to search this string, potentially reading beyond its allocated buffer. This same unsafe usage occurs when the string is used by the LED class device. The fix replaces strchr() with strnchr() and adds explicit checks to ensure the string is properly null-terminated, preventing buffer overread.
Potential Impact
The vulnerability could lead to a buffer overread in kernel space, which may cause information disclosure or kernel instability. However, no specific exploitation details or known active exploits are reported. The impact is limited to the Linux kernel's uleds subsystem handling of user-supplied strings.
Mitigation Recommendations
A fix has been implemented in the Linux kernel by replacing strchr() with strnchr() and adding explicit null-termination checks on the userspace-supplied name string. Users should apply the official kernel updates that include this fix once available. Patch status is not explicitly confirmed in the provided data; check the vendor or Linux kernel advisories for the exact fixed versions and update accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-p332-q22m-rchg
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-72241"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a808b73bf8831d5394fd6bf
Added to database: 08/15/2026, 15:53:23 UTC
Last enriched: 08/15/2026, 16:44:01 UTC
Last updated: 08/16/2026, 00:41:15 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.