Bug 2360768 (CVE-2025-32415)
| Summary: | CVE-2025-32415 libxml2: Out-of-bounds Read in xmlSchemaIDCFillNodeTables | ||
|---|---|---|---|
| Product: | [Other] Security Response | Reporter: | OSIDB Bzimport <bzimport> |
| Component: | vulnerability | Assignee: | Product Security DevOps Team <prodsec-dev> |
| Status: | NEW --- | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | unspecified | CC: | adudiak, caswilli, crizzo, csutherl, dfreiber, drow, jburrell, jclere, jmitchel, jtanner, kaycoth, kshier, omaciel, pjindal, plodge, stcannon, szappis, vkumar, yguenane |
| Target Milestone: | --- | Keywords: | Security |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | --- | |
| Doc Text: |
A flaw was found in the libxml2 library. A heap-based underflow can be triggered when a crafted XML document is validated against an XML schema with certain identity constraints or when a crafted XML schema is used, causing a crash to the application linked to the library and resulting in a denial of service.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 2360875, 2360876, 2360877, 2360878, 2360883, 2360884, 2360885, 2360886, 2360887, 2360888, 2360889, 2360890, 2360879, 2360880, 2360881, 2360882 | ||
| Bug Blocks: | |||
|
Description
OSIDB Bzimport
2025-04-17 18:01:13 UTC
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2025:13203 https://access.redhat.com/errata/RHSA-2025:13203 This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2025:13428 https://access.redhat.com/errata/RHSA-2025:13428 This issue has been addressed in the following products: Red Hat Enterprise Linux 10 Via RHSA-2025:13429 https://access.redhat.com/errata/RHSA-2025:13429 This issue has been addressed in the following products: Red Hat Enterprise Linux 9.4 Extended Update Support Via RHSA-2025:13677 https://access.redhat.com/errata/RHSA-2025:13677 This issue has been addressed in the following products: Red Hat Enterprise Linux 9.0 Update Services for SAP Solutions Via RHSA-2025:13684 https://access.redhat.com/errata/RHSA-2025:13684 This issue has been addressed in the following products: Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions Via RHSA-2025:13683 https://access.redhat.com/errata/RHSA-2025:13683 This issue has been addressed in the following products: Red Hat Enterprise Linux 8.2 Advanced Update Support Via RHSA-2025:13689 https://access.redhat.com/errata/RHSA-2025:13689 This issue has been addressed in the following products: Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support Red Hat Enterprise Linux 8.6 Update Services for SAP Solutions Red Hat Enterprise Linux 8.6 Telecommunications Update Service Via RHSA-2025:13688 https://access.redhat.com/errata/RHSA-2025:13688 This issue has been addressed in the following products: Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-On Via RHSA-2025:13788 https://access.redhat.com/errata/RHSA-2025:13788 This issue has been addressed in the following products: Red Hat Enterprise Linux 7 Extended Lifecycle Support Via RHSA-2025:13789 https://access.redhat.com/errata/RHSA-2025:13789 This issue has been addressed in the following products: Red Hat Enterprise Linux 8.8 Update Services for SAP Solutions Red Hat Enterprise Linux 8.8 Telecommunications Update Service Via RHSA-2025:13806 https://access.redhat.com/errata/RHSA-2025:13806 This issue has been addressed in the following products: Red Hat JBoss Core Services 2.4.62.SP1 Via RHSA-2025:13681 https://access.redhat.com/errata/RHSA-2025:13681 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.17 Via RHSA-2025:14059 https://access.redhat.com/errata/RHSA-2025:14059 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.19 Via RHSA-2025:14819 https://access.redhat.com/errata/RHSA-2025:14819 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.18 Via RHSA-2025:14818 https://access.redhat.com/errata/RHSA-2025:14818 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.14 Via RHSA-2025:14853 https://access.redhat.com/errata/RHSA-2025:14853 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.16 Via RHSA-2025:14858 https://access.redhat.com/errata/RHSA-2025:14858 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.12 Via RHSA-2025:15308 https://access.redhat.com/errata/RHSA-2025:15308 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.13 Via RHSA-2025:15672 https://access.redhat.com/errata/RHSA-2025:15672 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.15 Via RHSA-2025:16159 https://access.redhat.com/errata/RHSA-2025:16159 |