CVE-2025-62230
Analyzed
Analyzed - Analysis Complete
BaseFortify
Vulnerability report for CVE-2025-62230, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.
Publication date: 2025-10-30
Last updated on: 2026-07-01
Assigner: Red Hat, Inc.
Description
Description
A flaw was discovered in the X.Org X server’s X Keyboard (Xkb) extension when handling client resource cleanup. The software frees certain data structures without properly detaching related resources, leading to a use-after-free condition. This can cause memory corruption or a crash when affected clients disconnect.
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| x.org | xwayland | to 24.1.9 (exc) |
| x.org | x_server | to 21.1.19 (exc) |
| ibm | vios | From 4.1.0 (inc) to 4.1.1.30 (exc) |
| ibm | vios | 4.1.2.0 |
| ibm | aix | From 7.2.5 (inc) to 7.2.5.12 (exc) |
| ibm | aix | From 7.3.2 (inc) to 7.3.3.3 (exc) |
| ibm | aix | 7.3.4 |
| debian | debian_linux | 11.0 |
| redhat | enterprise_linux | 8.0 |
| redhat | enterprise_linux_aus | 8.2 |
| redhat | enterprise_linux_aus | 8.4 |
| redhat | enterprise_linux_eus | 8.4 |
| redhat | enterprise_linux | 9.0 |
| redhat | enterprise_linux_tus | 8.6 |
| redhat | enterprise_linux_aus | 8.6 |
| redhat | enterprise_linux_tus | 8.8 |
| redhat | enterprise_linux_update_services_for_sap_solutions | 8.6 |
| redhat | enterprise_linux_update_services_for_sap_solutions | 8.8 |
| redhat | enterprise_linux_update_services_for_sap_solutions | 9.2 |
| redhat | enterprise_linux_update_services_for_sap_solutions | 9.0 |
| redhat | enterprise_linux_eus | 9.4 |
| redhat | enterprise_linux | 10.0 |
| redhat | enterprise_linux_els | 7.0 |
| redhat | enterprise_linux_els | 6.0 |
Helpful Resources
Exploitability
CWE
KEV
| CWE ID | Description |
|---|---|
| CWE-416 | The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. |
