glibc Vulnerable to Memory Corruption via Heap-Based Buffer Overflow in 'malloc.ca' File (CVE-2026-0861)
39129
06 October 2026
06 October 2026
CLOSED
MEDIUM
8.4 HIGH - Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVE-2026-0861
|
Brocade Security Advisory ID |
BSA-2026-3478 |
|
Component |
glibc |
|
CWE |
CWE-190: Integer Overflow or Wraparound |
|
|
|
Summary
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.
Products Affected
- Brocade Fabric OS versions 9.2.0 through 10.0.0a1
Products Not Affected
- Brocade Fabric OS versions before 9.2.0
[VEX Justification: Code_not_present] - Brocade SANnav is not affected by this vulnerability
[VEX Justification: Vulnerable_code_cannot_be_contolled_by_adversary ] - Brocade ASCG is not affected by this vulnerability
[VEX Justification: Component_not_present]
Solution
- Security update provided in Brocade Fabric OS versions 9.2.2d and 10.0.1
Revision History
|
Version |
Change |
Date |
|
1.0 |
Initial Publication |
10/06/2026 |
Disclaimer
THIS DOCUMENT IS PROVIDED ON AN AS-IS BASIS SOLELY FOR INFORMATIONAL PURPOSES AND DOES NOT IMPLY ANY KIND OF GUARANTY OR WARRANTY, INCLUDING THE WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. YOUR USE OF THE INFORMATION CONTAINED HEREIN IS AT YOUR OWN RISK. ALL INFORMATION PROVIDED HEREIN IS BASED ON BROCADE'S CURRENT KNOWLEDGE AND UNDERSTANDING OF THE VULNERABILITY AND IMPACT TO BROCADE HARDWARE AND SOFTWARE PRODUCTS. BROCADE RESERVES THE RIGHT TO CHANGE OR UPDATE THIS DOCUMENT AT ANY TIME.