USN-7467-2: libxml2 vulnerabilities

Publication date

28 April 2025

Overview

Several security issues were fixed in libxml2.


Packages

Details

USN-7467-1 fixed several vulnerabilities in libxml2. This update provides
the corresponding update for Ubuntu 16.04 LTS and Ubuntu 18.04 LTS.

Original advisory details:

It was discovered that the libxml2 Python bindings incorrectly handled
certain return values. An attacker could possibly use this issue to cause
libxml2 to crash, resulting in a denial of service. (CVE-2025-32414)

It was discovered that libxml2 incorrectly handled certain memory
operations. A remote attacker could possibly use this issue to cause
libxml2 to crash, resulting in a denial of service. (CVE-2025-32415)

USN-7467-1 fixed several vulnerabilities in libxml2. This update provides
the corresponding update for Ubuntu 16.04 LTS and Ubuntu 18.04 LTS.

Original advisory details:

It was discovered that the libxml2 Python bindings incorrectly handled
certain return values. An attacker could possibly use this issue to cause
libxml2 to crash, resulting in a denial of service. (CVE-2025-32414)

It was discovered that libxml2 incorrectly handled certain memory
operations. A remote attacker could possibly use this issue to cause
libxml2 to crash, resulting in a denial of service. (CVE-2025-32415)

Update instructions

In general, a standard system update will make all the necessary changes.

Learn more about how to get the fixes.

The problem can be corrected by updating your system to the following package versions:

Ubuntu Release Package Version
18.04 bionic libxml2 –  2.9.4+dfsg1-6.1ubuntu1.9+esm3  
python-libxml2 –  2.9.4+dfsg1-6.1ubuntu1.9+esm3  
python3-libxml2 –  2.9.4+dfsg1-6.1ubuntu1.9+esm3  
16.04 xenial libxml2 –  2.9.3+dfsg1-1ubuntu0.7+esm8  
python-libxml2 –  2.9.3+dfsg1-1ubuntu0.7+esm8  

Reduce your security exposure

Ubuntu Pro provides ten-year security coverage to 25,000+ packages in Main and Universe repositories, and it is free for up to five machines.


Have additional questions?

Talk to a member of the team ›