libxml2: Use After Free
CVE-2025-7425 is a high-severity use after free vulnerability in libxml2 from GNOME, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an unauthenticated attacker, without any action from a user. The record lists version 2.15.2 as the first without the flaw, so updating libxml2 to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.44% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update libxml2 to 2.15.2 or a later version.
- Update RUGGEDCOM ROX MX5000 to V2.17.1 or a later version.
- Update RUGGEDCOM ROX MX5000RE to V2.17.1 or a later version.
Affected products and versions
Version data comes from the organisation that assigned the CVE; 26 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- HighSuccess depends on conditions outside the attacker's control.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:H. Scored by CNA (redhat.com).
Official description
A flaw was found in libxslt where the attribute type, atype, flags are modified in a way that corrupts internal memory management. When XSLT functions, such as the key() process, result in tree fragments, this corruption prevents the proper cleanup of ID attributes. As a result, the system may access freed memory, causing crashes or enabling attackers to trigger heap corruption.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Use After Free
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.
How developers prevent this class of flaw
- Choose a language that provides automatic memory management.
- When freeing pointers, be sure to set them to NULL once they are freed. However, the utilization of multiple or complex data structures may lower the usefulness of this strategy.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other references
- access.redhat.com/errata/RHBA-2025:12345
- access.redhat.com/errata/RHSA-2025:12447
- access.redhat.com/errata/RHSA-2025:12450
- access.redhat.com/errata/RHSA-2025:13267
- access.redhat.com/errata/RHSA-2025:13308
- access.redhat.com/errata/RHSA-2025:13309
- access.redhat.com/errata/RHSA-2025:13310
- access.redhat.com/errata/RHSA-2025:13311
- access.redhat.com/errata/RHSA-2025:13312
- access.redhat.com/errata/RHSA-2025:13313
- access.redhat.com/errata/RHSA-2025:13314
- access.redhat.com/errata/RHSA-2025:13335
- access.redhat.com/errata/RHSA-2025:13464
- access.redhat.com/errata/RHSA-2025:13622
- access.redhat.com/errata/RHSA-2025:14059
Other vulnerabilities in libxml2
- 9.8 Critical severity
- 7.5 High severity
Recent Use After Free vulnerabilities
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.