Fedora Account System
Red Hat Associate
Red Hat Customer
A double-free vulnerability exists in the libarchive RAR5 reader subsystem within archive_read_support_format_rar5.c where the state tracking pointer rar->cstate.filtered_buf can be linked to a temporary filter output block during archive decompression. When the unpacking engine subsequently processes an adjacent file or resets its internal state layout via init_unpack(), it releases the allocation mapped to filtered_buf but fails to clear or nullify the underlying pointer variable. A specially crafted RAR5 archive can exploit this lingering dangling pointer by forcing a secondary release operation on the exact same memory address, triggering a standard memory-manager abort that immediately crashes the application and results in a Denial of Service (DoS).
This issue has been addressed in the following products: Red Hat Enterprise Linux 10 Via RHSA-2026:52675 https://access.redhat.com/errata/RHSA-2026:52675
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2026:52674 https://access.redhat.com/errata/RHSA-2026:52674
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.22 Via RHSA-2026:54769 https://access.redhat.com/errata/RHSA-2026:54769
This issue has been addressed in the following products: Red Hat Enterprise Linux 10.0 Extended Update Support Via RHSA-2026:56954 https://access.redhat.com/errata/RHSA-2026:56954
This issue has been addressed in the following products: Red Hat Enterprise Linux 9.6 Extended Update Support Via RHSA-2026:58558 https://access.redhat.com/errata/RHSA-2026:58558
This issue has been addressed in the following products: Red Hat Enterprise Linux 9.4 Update Services for SAP Solutions Via RHSA-2026:58573 https://access.redhat.com/errata/RHSA-2026:58573
This issue has been addressed in the following products: Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions Via RHSA-2026:58574 https://access.redhat.com/errata/RHSA-2026:58574
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.20 Via RHSA-2026:63100 https://access.redhat.com/errata/RHSA-2026:63100
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.21 Via RHSA-2026:63041 https://access.redhat.com/errata/RHSA-2026:63041
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.19 Via RHSA-2026:63044 https://access.redhat.com/errata/RHSA-2026:63044
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.14 Via RHSA-2026:62409 https://access.redhat.com/errata/RHSA-2026:62409
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.18 Via RHSA-2026:65851 https://access.redhat.com/errata/RHSA-2026:65851
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.13 Via RHSA-2026:65839 https://access.redhat.com/errata/RHSA-2026:65839
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.16 Via RHSA-2026:67935 https://access.redhat.com/errata/RHSA-2026:67935
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.15 Via RHSA-2026:67857 https://access.redhat.com/errata/RHSA-2026:67857
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.17 Via RHSA-2026:70586 https://access.redhat.com/errata/RHSA-2026:70586
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.18 Via RHSA-2026:70615 https://access.redhat.com/errata/RHSA-2026:70615