CVE-2026-0861
Public on
Last Modified:
Description
A flaw was found in the glibc library. Passing an excessively large alignment value to the memalign suite of functions, such as memalign, posix_memalign, aligned_alloc, valloc and pvalloc, an integer overflow can occur during internal size calculations due to improper overflow checks, causing an allocation of a small chunk of memory which is subsequently used for writing. This issue can result in an application crash or heap memory corruption.
Statement
To exploit this flaw, an attacker needs to find an application linked to the glibc library that is using one of the vulnerable functions (memalign, posix_memalign, aligned_alloc, valloc or pvalloc) in a way that the alignment parameter can be user-controlled, allowing an attacker to trigger the integer overflow. However, the alignment parameter used by the functions is usually hard-coded power of two and do not allow arbitrary values, specially values supplied by a user. There is no known application vulnerable to this issue.
Also, default Red Hat Enterprise Linux security features, including SELinux enforcement, Address Space Layout Randomization (ASLR) and memory protections significantly increase the difficult of achieving arbitrary code execution, limiting the impact of this vulnerability.
Due to these reasons, this vulnerability has been rated with a low severity.
Mitigation
Applications calling one of the vulnerable functions and allowing the alignment parameter to be set by user-controlled input can implement additional validations checks, ensuring the alignment value is a power of two and does not exceed a sane limit, for example the system page size or a maximum of 64KB. This prevents the excessively large value required to trigger the integer overflow.
Additional Information
- This content is not included.Bugzilla 2429771: glibc: Integer overflow in memalign leads to heap corruption
- Content from cwe.mitre.org is not included.CWE-190: Integer Overflow or Wraparound
- FAQ: Frequently asked questions about CVE-2026-0861
- Offline Security Data data is available for integration with other systems. See Offline Security Data API to get started.
External References
Content from www.cve.org is not included.https://www.cve.org/CVERecord?id=CVE-2026-0861
Content from nvd.nist.gov is not included.https://nvd.nist.gov/vuln/detail/CVE-2026-0861
Content from sourceware.org is not included.https://sourceware.org/bugzilla/show_bug.cgi?id=33796
Affected Packages and Issued Red Hat Security Errata
| Products / Services | Components | State | Errata |
|---|---|---|---|
| Cost Management 4 | costmanagement/costmanagement-metrics-rhel9-operator | Fixed | RHSA-2026:3228 |
| Red Hat Ceph Storage 8 | rhceph/rhceph-8-rhel9 | Fixed | RHSA-2026:5606 |
| Red Hat Discovery 2 | discovery/discovery-server-rhel9 | Fixed | RHSA-2026:4501 |
| Red Hat Discovery 2 | discovery/discovery-ui-rhel9 | Fixed | RHSA-2026:4501 |
| Red Hat Enterprise Linux 10 | glibc | Fixed | RHSA-2026:1334 |
| Red Hat Enterprise Linux 6 | compat-glibc | Not affected | |
| Red Hat Enterprise Linux 6 | glibc | Not affected | |
| Red Hat Enterprise Linux 7 | compat-glibc | Not affected | |
| Red Hat Enterprise Linux 7 | glibc | Not affected | |
| Red Hat Enterprise Linux 8 | glibc | Not affected | |
| Red Hat Enterprise Linux 9 | glibc | Fixed | RHSA-2026:2786 |
| Red Hat Insights proxy 1.5 | insights-proxy/insights-proxy-container-rhel9 | Fixed | RHSA-2026:4655 |
| Red Hat OpenShift Container Platform 4 | rhcos | Fix deferred | |
| Red Hat Update Infrastructure 5 | rhui5/cds-rhel9 | Fixed | RHSA-2026:4943 |
| Red Hat Update Infrastructure 5 | rhui5/haproxy-rhel9 | Fixed | RHSA-2026:4943 |
| Red Hat Update Infrastructure 5 | rhui5/installer-rhel9 | Fixed | RHSA-2026:4943 |
| Red Hat Update Infrastructure 5 | rhui5/rhua-rhel9 | Fixed | RHSA-2026:4943 |
Common Vulnerability Scoring System (CVSS) Score Details
Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authorities (CNA) source for its products and services (see Red Hat classifications ).
| CVSS v3 Score Breakdown | Red Hat | NVD |
|---|---|---|
| CVSS v3 Base Score | 8.1 | |
| Attack Vector | Network | |
| Attack Complexity | High | |
| Privileges Required | None | |
| User Interaction | None | |
| Scope | Unchanged | |
| Confidentiality Impact | High | |
| Integrity Impact | High | |
| Availability Impact | High |
CVSS v3 Vector
Red Hat CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Frequently Asked Questions
Why is Red Hat's CVSS v3 score or Impact different from other vendors?
For more information, see https://access.redhat.com/solutions/762393.
My product is listed as "Under investigation" or "Affected", when will Red Hat release a fix for this vulnerability?
- "Under investigation" doesn't necessarily mean that the product is affected by this vulnerability. It only means that our Analysis Team is still working on determining whether the product is affected and how it is affected.
- "Affected" means that our Analysis Team has determined that this product is affected by this vulnerability and might release a fix to address this in the near future.
What can I do if my product is listed as "Will not fix"?
Available options depend mostly on the Impact of the vulnerability and the current Life Cycle phase of your product. Overall, you have the following options:
- Upgrade to a supported product version that includes a fix for this vulnerability (recommended).
- Apply a mitigation (if one exists).
- Open a This content is not included.support case to request a prioritization of releasing a fix for this vulnerability.
What can I do if my product is listed as "Fix deferred"?
Available options depend mostly on the Impact of the vulnerability and the current Life Cycle phase of your product. Overall, you have the following options:
- Apply a mitigation (if one exists).
- Open a This content is not included.support case to request a prioritization of releasing a fix for this vulnerability.
- Red Hat Engineering focuses on addressing high-priority issues based on their complexity or limited lifecycle support. Therefore, lower-priority issues will not receive immediate fixes.
What is a mitigation?
I have a Red Hat product but it is not in the above list, is it affected?
Why is my security scanner reporting my product as vulnerable to this vulnerability even though my product version is fixed or not affected?
My product is listed as "Out of Support Scope". What does this mean?
Not sure what something means? Check out our Security Glossary.