CVE-2025-6021

A flaw was found in libxml2's 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.

A flaw was found in libxml2's 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.

A flaw was found in libxml2's 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.

This library allows to manipulate XML files. It includes support to read, modify and write XML and HTML files. There is DTDs support this includes parsing and validation even with complex DtDs, either at parse time or later once the document has been modified. The output can be a simple SAX stream or and in-memory DOM like representations. In this case one can use the built-in XPath and XPointer implementation to select sub nodes or ranges. A flexible Input/Output mechanism is available, with existing HTTP and FTP modules and combined to an URI library.

Security Fix(es):

A flaw was found in libxml2's 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.(CVE-2025-6021)

This library allows to manipulate XML files. It includes support to read, modify and write XML and HTML files. There is DTDs support this includes parsing and validation even with complex DtDs, either at parse time or later once the document has been modified. The output can be a simple SAX stream or and in-memory DOM like representations. In this case one can use the built-in XPath and XPointer implementation to select sub nodes or ranges. A flexible Input/Output mechanism is available, with existing HTTP and FTP modules and combined to an URI library.

Security Fix(es):

A flaw was found in libxml2's 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.(CVE-2025-6021)

This library allows to manipulate XML files. It includes support to read, modify and write XML and HTML files. There is DTDs support this includes parsing and validation even with complex DtDs, either at parse time or later once the document has been modified. The output can be a simple SAX stream or and in-memory DOM like representations. In this case one can use the built-in XPath and XPointer implementation to select sub nodes or ranges. A flexible Input/Output mechanism is available, with existing HTTP and FTP modules and combined to an URI library.

Security Fix(es):

A flaw was found in libxml2's 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.(CVE-2025-6021)

This library allows to manipulate XML files. It includes support to read, modify and write XML and HTML files. There is DTDs support this includes parsing and validation even with complex DtDs, either at parse time or later once the document has been modified. The output can be a simple SAX stream or and in-memory DOM like representations. In this case one can use the built-in XPath and XPointer implementation to select sub nodes or ranges. A flexible Input/Output mechanism is available, with existing HTTP and FTP modules and combined to an URI library.

Security Fix(es):

A flaw was found in libxml2's 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.(CVE-2025-6021)

This library allows to manipulate XML files. It includes support to read, modify and write XML and HTML files. There is DTDs support this includes parsing and validation even with complex DtDs, either at parse time or later once the document has been modified. The output can be a simple SAX stream or and in-memory DOM like representations. In this case one can use the built-in XPath and XPointer implementation to select sub nodes or ranges. A flexible Input/Output mechanism is available, with existing HTTP and FTP modules and combined to an URI library.

Security Fix(es):

A flaw was found in libxml2's 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.(CVE-2025-6021)

This library allows to manipulate XML files. It includes support to read, modify and write XML and HTML files. There is DTDs support this includes parsing and validation even with complex DtDs, either at parse time or later once the document has been modified. The output can be a simple SAX stream or and in-memory DOM like representations. In this case one can use the built-in XPath and XPointer implementation to select sub nodes or ranges. A flexible Input/Output mechanism is available, with existing HTTP and FTP modules and combined to an URI library.

Security Fix(es):

A use-after-free vulnerability was found in libxml2. This issue occurs when parsing XPath elements under certain circumstances when the XML schematron has the <sch:name path="..."/> schema elements. This flaw allows a malicious actor to craft a malicious XML document used as input for libxml, resulting in the program's crash using libxml or other possible undefined behaviors.(CVE-2025-49794)

A NULL pointer dereference vulnerability was found in libxml2 when processing XPath XML expressions. This flaw allows an attacker to craft a malicious XML input to libxml2, leading to a denial of service.(CVE-2025-49795)

A vulnerability was found in libxml2. Processing certain sch:name elements from the input XML file can trigger a memory corruption issue. This flaw allows an attacker to craft a malicious XML input file that can lead libxml to crash, resulting in a denial of service or other possible undefined behavior due to sensitive data being corrupted in memory.(CVE-2025-49796)

A vulnerability was found in xmlsoft libxml2 (Document Processing Software) (version now known). It has been declared as critical.The CWE definition for the vulnerability is CWE-121. 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).As an impact it is known to affect confidentiality, integrity, and availability.There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-18175).(CVE-2025-6021)

The libxml2 library is a development toolbox providing the implementation of various XML standards.

Security Fix(es):

• libxml: Heap use after free (UAF) leads to Denial of service (DoS) (CVE-2025-49794)

• libxml: Null pointer dereference leads to Denial of service (DoS) (CVE-2025-49795)

• libxml: Type confusion leads to Denial of service (DoS) (CVE-2025-49796)

• libxml2: Integer Overflow in xmlBuildQName() Leads to Stack Buffer Overflow in libxml2 (CVE-2025-6021)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

The libxml2 library is a development toolbox providing the implementation of various XML standards.

Security Fix(es):

• libxml: Heap use after free (UAF) leads to Denial of service (DoS) (CVE-2025-49794)

• libxml: Type confusion leads to Denial of service (DoS) (CVE-2025-49796)

• libxml2: Integer Overflow in xmlBuildQName() Leads to Stack Buffer Overflow in libxml2 (CVE-2025-6021)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

The libxml2 library is a development toolbox providing the implementation of various XML standards.

Security Fix(es):

• libxml: Heap use after free (UAF) leads to Denial of service (DoS) (CVE-2025-49794)

• libxml: Type confusion leads to Denial of service (DoS) (CVE-2025-49796)

• libxml2: Integer Overflow in xmlBuildQName() Leads to Stack Buffer Overflow in libxml2 (CVE-2025-6021)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

A flaw was found in libxml2's 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.

The libxml2 library is a development toolbox providing the implementation of various XML standards.

Security Fix(es):

• libxml: Heap use after free (UAF) leads to Denial of service (DoS) (CVE-2025-49794)
• libxml: Null pointer dereference leads to Denial of service (DoS) (CVE-2025-49795)
• libxml: Type confusion leads to Denial of service (DoS) (CVE-2025-49796)
• libxml2: Integer Overflow in xmlBuildQName() Leads to Stack Buffer Overflow in libxml2 (CVE-2025-6021)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

The libxml2 library is a development toolbox providing the implementation of various XML standards.

Security Fix(es):

• libxml: Heap use after free (UAF) leads to Denial of service (DoS) (CVE-2025-49794)
• libxml: Type confusion leads to Denial of service (DoS) (CVE-2025-49796)
• libxml2: Integer Overflow in xmlBuildQName() Leads to Stack Buffer Overflow in libxml2 (CVE-2025-6021)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

The libxml2 library is a development toolbox providing the implementation of various XML standards.

Security Fix(es):

• libxml: Heap use after free (UAF) leads to Denial of service (DoS) (CVE-2025-49794)
• libxml: Type confusion leads to Denial of service (DoS) (CVE-2025-49796)
• libxml2: Integer Overflow in xmlBuildQName() Leads to Stack Buffer Overflow in libxml2 (CVE-2025-6021)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

A flaw was found in libxml2's 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.

A flaw was found in libxml2's 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.

A flaw was found in libxml2's 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.

A flaw was found in libxml2's 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.

A flaw was found in libxml2's 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.

• CVE-2025-49794: fix use-after-free issue triggered by processing certain <sch:name path="..."/> elements in input XML file.
• CVE-2025-49796: fix memory corruption issue triggered by processing certain sch:name elements from input XML file
• CVE-2025-6021: fix integer overflow in buffer size calculations to prevent stack-based buffer overflow

• CVE-2025-49794: fix use-after-free issue triggered by processing certain <sch:name path="..."/> elements in input XML file.
• CVE-2025-49796: fix memory corruption issue triggered by processing certain sch:name elements in input XML file.
• CVE-2025-6021: fix integer overflow in buffer size calculations to prevent stack-based buffer overflow

• CVE-2025-49794: fix use-after-free issue triggered by processing certain <sch:name path="..."/> elements in input XML file.
• CVE-2025-49796: fix memory corruption issue triggered by processing certain sch:name elements in input XML file.
• CVE-2025-6021: fix integer overflow in buffer size calculations to prevent stack-based buffer overflow

• CVE-2025-6021: fix buffer overflow in xmlBuildQName function

• SECURITY UPDATE: stack-based buffer overflow via integer overflows in buffer size calculations in xmlBuildQName function
  • debian/patches/CVE-2025-6021.patch: Fix integer overflow in xmlBuildQName that affects memory safety
  • CVE-2025-6021

• SECURITY UPDATE: stack-based buffer overflow vulnerability
  • debian/patches/CVE-2025-6021.patch: Fix integer overflow in xmlBuildQName to improve memory safety
  • CVE-2025-6021

• CVE-2025-7425: fix heap-use-after-free in xmlFreeID caused by 'atype' corruption
• CVE-2025-6021: fix integer overflows in buffer size calculations

• CVE-2025-7425: fix heap-use-after-free in xmlFreeID caused by 'atype' corruption
• CVE-2025-6021: fix integer overflows in buffer size calculations

• CVE-2025-7425: fix heap-use-after-free in xmlFreeID caused by 'atype' corruption
• CVE-2025-6021: fix integer overflows in buffer size calculations

• SECURITY UPDATE: stack-based buffer overflow vulnerability in xmlBuildQName function
  • debian/patches/CVE-2025-6021.patch: fix integer overflow in xmlBuildQName causing memory safety issue
  • CVE-2025-6021

• CVE-2025-6021: fix integer overflows in buffer size calculations

• CVE-2025-6021: fix integer overflows in buffer size calculations

Heap use after free (UAF) leads to Denial of service (DoS). (CVE-2025-49794) Null pointer dereference leads to Denial of service (DoS). (CVE-2025-49795) Type confusion leads to Denial of service (DoS). (CVE-2025-49796) Integer Overflow Leading to Buffer Overflow in xmlBuildQName(). (CVE-2025-6021) Stack-based Buffer Overflow in xmllint Shell. (CVE-2025-6170) Type confusion in xmlNode.psvi between stylesheet and source nodes. (CVE-2025-7424) Heap-use-after-free in xmlFreeID caused by atype corruption. (CVE-2025-7425)

These are all security issues fixed in the libxml2-2-2.13.8-2.1 package on the GA media of openSUSE Tumbleweed.