CVE Vulnerabilities

CVE-2025-6021

Stack-based Buffer Overflow

Published: Jun 12, 2025 | Modified: Nov 29, 2025
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
RedHat/V2
RedHat/V3
7.5 MODERATE
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Ubuntu
MEDIUM
root.io logo minimus.io logo echo.ai logo

A flaw was found in libxml2s xmlBuildQName function, where integer overflows in buffer size calculations can lead to a stack-based buffer overflow. This issue can result in memory corruption or a denial of service when processing crafted input.

Weakness

A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).

Affected Software

NameVendorStart VersionEnd Version
Libxml2Xmlsoft*2.14.4 (excluding)
Red Hat Enterprise Linux 10RedHatlibxml2-0:2.12.5-7.el10_0*
Red Hat Enterprise Linux 7 Extended Lifecycle SupportRedHatlibxml2-0:2.9.1-6.el7_9.10*
Red Hat Enterprise Linux 8RedHatlibxml2-0:2.9.7-21.el8_10.1*
Red Hat Enterprise Linux 8RedHatlibxml2-0:2.9.7-21.el8_10.1*
Red Hat Enterprise Linux 8.2 Advanced Update SupportRedHatlibxml2-0:2.9.7-9.el8_2.3*
Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update SupportRedHatlibxml2-0:2.9.7-9.el8_4.6*
Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-OnRedHatlibxml2-0:2.9.7-9.el8_4.6*
Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update SupportRedHatlibxml2-0:2.9.7-13.el8_6.10*
Red Hat Enterprise Linux 8.6 Telecommunications Update ServiceRedHatlibxml2-0:2.9.7-13.el8_6.10*
Red Hat Enterprise Linux 8.6 Update Services for SAP SolutionsRedHatlibxml2-0:2.9.7-13.el8_6.10*
Red Hat Enterprise Linux 8.8 Telecommunications Update ServiceRedHatlibxml2-0:2.9.7-16.el8_8.9*
Red Hat Enterprise Linux 8.8 Update Services for SAP SolutionsRedHatlibxml2-0:2.9.7-16.el8_8.9*
Red Hat Enterprise Linux 9RedHatlibxml2-0:2.9.13-10.el9_6*
Red Hat Enterprise Linux 9RedHatlibxml2-0:2.9.13-10.el9_6*
Red Hat Enterprise Linux 9.0 Update Services for SAP SolutionsRedHatlibxml2-0:2.9.13-1.el9_0.5*
Red Hat Enterprise Linux 9.2 Update Services for SAP SolutionsRedHatlibxml2-0:2.9.13-3.el9_2.7*
Red Hat Enterprise Linux 9.4 Extended Update SupportRedHatlibxml2-0:2.9.13-10.el9_4*
Red Hat JBoss Core Services 2.4.62.SP2RedHatlibxml2*
Red Hat OpenShift Container Platform 4.12RedHatrhcos-412.86.202509030110-0*
Red Hat OpenShift Container Platform 4.13RedHatrhcos-413.92.202509030117-0*
Red Hat OpenShift Container Platform 4.14RedHatrhcos-414.92.202508041909-0*
Red Hat OpenShift Container Platform 4.15RedHatrhcos-415.92.202508192014-0*
Red Hat OpenShift Container Platform 4.16RedHatrhcos-416.94.202508050040-0*
Red Hat OpenShift Container Platform 4.17RedHatrhcos-417.94.202508141510-0*
Red Hat OpenShift Container Platform 4.18RedHatrhcos-418.94.202508060022-0*
Red Hat OpenShift Container Platform 4.19RedHatrhcos-4.19.9.6.202507230107-0*
Red Hat Discovery 2RedHatdiscovery/discovery-server-rhel9:sha256:ad07f55ee75fb20310c88f154a04665bd8465d138d66c665c300f61447858344*
Red Hat Insights proxy 1.5RedHatinsights-proxy/insights-proxy-container-rhel9:sha256:c26d589f12647890b67aaa986f54d3f7c6f7f2563fb5a73f38d559e6138739d7*
Libxml2Ubuntuesm-infra-legacy/trusty*
Libxml2Ubuntuesm-infra/bionic*
Libxml2Ubuntuesm-infra/focal*
Libxml2Ubuntuesm-infra/xenial*
Libxml2Ubuntujammy*
Libxml2Ubuntunoble*
Libxml2Ubuntuoracular*
Libxml2Ubuntuplucky*
Libxml2Ubuntuupstream*

Potential Mitigations

  • Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking.
  • D3-SFCV (Stack Frame Canary Validation) from D3FEND [REF-1334] discusses canary-based detection in detail.
  • Run or compile the software using features or extensions that randomly arrange the positions of a program’s executable and libraries in memory. Because this makes the addresses unpredictable, it can prevent an attacker from reliably jumping to exploitable code.
  • Examples include Address Space Layout Randomization (ASLR) [REF-58] [REF-60] and Position-Independent Executables (PIE) [REF-64]. Imported modules may be similarly realigned if their default memory addresses conflict with other modules, in a process known as “rebasing” (for Windows) and “prelinking” (for Linux) [REF-1332] using randomly generated addresses. ASLR for libraries cannot be used in conjunction with prelink since it would require relocating the libraries at run-time, defeating the whole purpose of prelinking.
  • For more information on these techniques see D3-SAOR (Segment Address Offset Randomization) from D3FEND [REF-1335].

References