CVE-2026-0861: CWE-190 Integer Overflow or Wraparound in The GNU C Library glibc
Passing too large an alignment to the memalign suite of functions (memalign, posix_memalign, aligned_alloc) in the GNU C Library version 2.30 to 2.42 may result in an integer overflow, which could consequently result in a heap corruption. Note that the attacker must have control over both, the size as well as the alignment arguments of the memalign function to be able to exploit this. The size parameter must be close enough to PTRDIFF_MAX so as to overflow size_t along with the large alignment argument. This limits the malicious inputs for the alignment for memalign to the range [1<<62+ 1, 1<<63] and exactly 1<<63 for posix_memalign and aligned_alloc. Typically the alignment argument passed to such functions is a known constrained quantity (e.g. page size, block size, struct sizes) and is not attacker controlled, because of which this may not be easily exploitable in practice. An application bug could potentially result in the input alignment being too large, e.g. due to a different buffer overflow or integer overflow in the application or its dependent libraries, but that is again an uncommon usage pattern given typical sources of alignments.
AI Analysis
Technical Summary
This vulnerability involves an integer overflow or wraparound (CWE-190) triggered by passing a large alignment argument to memory allocation functions in glibc (memalign, posix_memalign, aligned_alloc) in versions 2.30 through 2.42. The overflow can lead to heap corruption if the attacker controls both the size and alignment parameters, with the size parameter close to PTRDIFF_MAX and alignment values in the range [1<<62+1, 1<<63]. Since alignment arguments are typically constrained and not attacker-controlled, exploitation is limited and uncommon. The vulnerability has a CVSS 3.1 score of 8.4, indicating high severity with impacts on confidentiality, integrity, and availability. No patch or vendor advisory details are provided in the input.
Potential Impact
Successful exploitation could lead to heap corruption, potentially allowing an attacker to compromise confidentiality, integrity, and availability of affected systems. However, exploitation is constrained by the requirement that the attacker must control both size and alignment parameters with very large values, which is uncommon in typical application usage. No known exploits in the wild have been reported.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Due to the complexity and constraints on exploitation, typical usage patterns may mitigate risk. Monitor official GNU C Library advisories for patches or updates addressing this issue.
CVE-2026-0861: CWE-190 Integer Overflow or Wraparound in The GNU C Library glibc
Description
Passing too large an alignment to the memalign suite of functions (memalign, posix_memalign, aligned_alloc) in the GNU C Library version 2.30 to 2.42 may result in an integer overflow, which could consequently result in a heap corruption. Note that the attacker must have control over both, the size as well as the alignment arguments of the memalign function to be able to exploit this. The size parameter must be close enough to PTRDIFF_MAX so as to overflow size_t along with the large alignment argument. This limits the malicious inputs for the alignment for memalign to the range [1<<62+ 1, 1<<63] and exactly 1<<63 for posix_memalign and aligned_alloc. Typically the alignment argument passed to such functions is a known constrained quantity (e.g. page size, block size, struct sizes) and is not attacker controlled, because of which this may not be easily exploitable in practice. An application bug could potentially result in the input alignment being too large, e.g. due to a different buffer overflow or integer overflow in the application or its dependent libraries, but that is again an uncommon usage pattern given typical sources of alignments.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability involves an integer overflow or wraparound (CWE-190) triggered by passing a large alignment argument to memory allocation functions in glibc (memalign, posix_memalign, aligned_alloc) in versions 2.30 through 2.42. The overflow can lead to heap corruption if the attacker controls both the size and alignment parameters, with the size parameter close to PTRDIFF_MAX and alignment values in the range [1<<62+1, 1<<63]. Since alignment arguments are typically constrained and not attacker-controlled, exploitation is limited and uncommon. The vulnerability has a CVSS 3.1 score of 8.4, indicating high severity with impacts on confidentiality, integrity, and availability. No patch or vendor advisory details are provided in the input.
Potential Impact
Successful exploitation could lead to heap corruption, potentially allowing an attacker to compromise confidentiality, integrity, and availability of affected systems. However, exploitation is constrained by the requirement that the attacker must control both size and alignment parameters with very large values, which is uncommon in typical application usage. No known exploits in the wild have been reported.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Due to the complexity and constraints on exploitation, typical usage patterns may mitigate risk. Monitor official GNU C Library advisories for patches or updates addressing this issue.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- glibc
- Date Reserved
- 2026-01-12T14:35:11.285Z
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 696807fbf809b25a9881d78a
Added to database: 1/14/2026, 9:17:47 PM
Last enriched: 4/30/2026, 2:02:46 AM
Last updated: 5/9/2026, 12:42:15 AM
Views: 1179
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.