libxml2 before 2.12.10 and 2.13.x before 2.13.6 has a use-after-free in xmlSchemaIDCFillNodeTables and xmlSchemaBubbleIDCNodeTables in xmlschemas.c. To exploit this, a crafted XML document must be validated against an XML schema with certain identity constraints, or a crafted XML schema must be used.
This issue has been addressed in the following products: Red Hat Enterprise Linux 9.2 Extended Update Support Via RHSA-2025:2482 https://access.redhat.com/errata/RHSA-2025:2482
This issue has been addressed in the following products: Red Hat Enterprise Linux 9.0 Update Services for SAP Solutions Via RHSA-2025:2483 https://access.redhat.com/errata/RHSA-2025:2483
This issue has been addressed in the following products: Red Hat Enterprise Linux 8.8 Extended Update Support Via RHSA-2025:2507 https://access.redhat.com/errata/RHSA-2025:2507
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:2513 https://access.redhat.com/errata/RHSA-2025:2513
This issue has been addressed in the following products: Red Hat Enterprise Linux 8.2 Advanced Update Support Via RHSA-2025:2654 https://access.redhat.com/errata/RHSA-2025:2654
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 Update Services for SAP Solutions Red Hat Enterprise Linux 8.4 Telecommunications Update Service Via RHSA-2025:2660 https://access.redhat.com/errata/RHSA-2025:2660
This issue has been addressed in the following products: Red Hat Enterprise Linux 7 Extended Lifecycle Support Via RHSA-2025:2673 https://access.redhat.com/errata/RHSA-2025:2673
This issue has been addressed in the following products: Red Hat Enterprise Linux 9.4 Extended Update Support Via RHSA-2025:2678 https://access.redhat.com/errata/RHSA-2025:2678
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2025:2679 https://access.redhat.com/errata/RHSA-2025:2679
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2025:2686 https://access.redhat.com/errata/RHSA-2025:2686
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.13 Via RHSA-2025:2701 https://access.redhat.com/errata/RHSA-2025:2701
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.18 Via RHSA-2025:3066 https://access.redhat.com/errata/RHSA-2025:3066
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.15 Via RHSA-2025:3055 https://access.redhat.com/errata/RHSA-2025:3055
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.17 Via RHSA-2025:3059 https://access.redhat.com/errata/RHSA-2025:3059
This issue has been addressed in the following products: Red Hat JBoss Core Services Via RHSA-2025:3453 https://access.redhat.com/errata/RHSA-2025:3453
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.16 Via RHSA-2025:3301 https://access.redhat.com/errata/RHSA-2025:3301
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.14 Via RHSA-2025:3569 https://access.redhat.com/errata/RHSA-2025:3569
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.12 Via RHSA-2025:3573 https://access.redhat.com/errata/RHSA-2025:3573