Gcc-toolset-15-gcc: gcc: gcc-toolset-16: gcc: denial of service via use-after-free in binary heap erase_if
Lists Red Hat Enterprise Linux 6 through 10, Hardened Images, and OpenShift Container Platform gcc packages, with no version ranges given. No vendor rating is given. The listed fix is gcc-8.5.0-30.el8_10 for RHEL 8.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Fix
- Fixed in 8.5.0-30.el8_10
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
A flaw was found in GCC. When an application calls the erase_if function on a binary heap priority queue in libstdc++, the library reallocates storage but fails to update its internal entry pointer. An attacker capable of triggering this operation can exploit this use-after-free condition, leading to a Denial of Service (DoS) via an application crash or potential memory corruption.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- gcc-toolset-15-gcc
Version range not reported
- gcc
Version range not reported
- gcc-toolset-15-gcc
Version range not reported
- gcc13-main
Version range not reported
- gcc-main
Version range not reported
- gcc
Version range not reported
- gcc-toolset-16
Version range not reported
- gcc-toolset-16-gcc
Version range not reported
- mingw-gcc
Version range not reported
- compat-gcc-295
Version range not reported
- compat-gcc-296
Version range not reported
- compat-gcc-32
Version range not reported
- compat-gcc-34
Version range not reported
- gcc
Version range not reported
- compat-gcc-32
Version range not reported
- compat-gcc-34
Version range not reported
- compat-gcc-44
Version range not reported
- gcc
Version range not reported
- gcc-toolset-14-gcc
Version range not reported
- mingw-gcc
Version range not reported
- rteval-loads
Version range not reported
- gcc
Version range not reported
- gcc-toolset-14-gcc
Version range not reported
- gcc-toolset-15-gcc
Version range not reported
- gcc-toolset-16
Version range not reported
- gcc-toolset-16-gcc
Version range not reported
- mingw-gcc
Version range not reported
- openshift/ose-rhel-coreos-8
Version range not reported
- openshift/ose-rhel-coreos-9
Version range not reported
- openshift/ose-rhel-coreos-9
Version range not reported
References 7
Questions about CVE-2026-102010
What does this mean?
A flaw in the GCC binary heap erase_if code frees memory that is still in use, so a program using it can crash, and the memory may be corrupted. The impact is a denial of service.Source: access.redhat.com
Am I affected, and how do I check?
The advisory lists Red Hat Enterprise Linux 6, 7, 8, 9 and 10, Red Hat Hardened Images, and OpenShift Container Platform 4 and 5 without version ranges. To check a system, run rpm -q gcc or gcc --version and compare the result with the fixed build for that product.Source: access.redhat.com
What should I do about it?
For RHEL 8 the listed fix is gcc-8.5.0-30.el8_10, so update the gcc packages to that build or later. Fixed builds for the other listed products are not given in the facts, so use the vendor's update channel for each.Source: access.redhat.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data