CVE-2025-11234: Red Hat Enterprise Linux 10 · Use After Free
Affects Red Hat Enterprise Linux 10Source CVE Database V5
Not known to be exploited · CVSS 7.5 High : upgrade Red Hat Enterprise Linux 10 to 10.1.2 soon.
Data as of 26 Oct 2026, 15:59 UTC
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 58% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 10.1.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 3 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade qemu to 10.1.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| qemu | Affected
| Fixed in
|
AI-suggested
Red Hat has released official security updates addressing CVE-2025-11234 for affected products including Red Hat Enterprise Linux 9.4 Extended Update Support and OpenShift Container Platform 4.16.55. Users should apply these patches promptly following the vendor's instructions available at https://access.redhat.com/articles/11258 and the OpenShift update documentation at https://docs.redhat.com/en/documentation/openshift_container_platform/4.16/html-single/updating_clusters/index#updating-cluster-cli. Since patches are available, updating to the fixed versions is the recommended mitigation. No additional vendor-recommended mitigations or workarounds are indicated in the advisory.
Description
A flaw was found in QEMU. If the QIOChannelWebsock object is freed while it is waiting to complete a handshake, a GSource is leaked. This can lead to the callback firing later on and triggering a use-after-free in the use of the channel. This can be abused by a malicious client with network access to the VNC WebSocket port to cause a denial of service during the WebSocket handshake prior to the VNC client authentication.
References
- access.redhat.com/errata/RHSA-2025:23228 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:0326 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:0332 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:0702 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:1831 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:18772 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:22147 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:3077 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:3165 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:5578 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2025-11234 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2401209 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:59831 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:68513 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:69131 (opens in a new tab)