Application crash via Power8 strncasecmp one-byte overread
Published Sep 28, 2026 · Updated Sep 28, 2026
An out-of-bounds read in GNU C Library (glibc) 2.24 through 2.44 allows attackers to crash applications using Power8 strncasecmp. The Power8-optimized routine reads one byte beyond its input size limit when the compared strings match through that limit. A crash requires attacker-controlled strings at a page boundary with an unreadable neighboring page; exposure depends on an application passing those strings to the routine.
Summary
What happened
An out-of-bounds read in GNU C Library (glibc) 2.24 through 2.44 allows attackers to crash applications using Power8 strncasecmp. The Power8-optimized routine reads one byte beyond its input size limit when the compared strings match through that limit. A crash requires attacker-controlled strings at a page boundary with an unreadable neighboring page; exposure depends on an application passing those strings to the routine.
The record
- CVE
- CVE-2026-97399
- Published
- Sep 28, 2026
- Updated
- Sep 28, 2026
- Vendor
- CVS Home
- Product
- GNU C Library (glibc)
- Classifications
- T1499
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 28, 2026CVE publishedPublication date reported by the CVE source.
- Sep 28, 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=2.24 <2.45
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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.
Activity data is delayed. The latest report is Sep 28, 2026.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started