CVE-2026-99753
Description
A flaw was found in the Linux kernel's Loongson display controller driver. When buffer object initialization fails, the driver improperly attempts to release the same memory allocation twice. A local user could exploit this flaw to cause memory corruption, resulting in a system crash and Denial of Service (DoS).
Statement
This vulnerability is rated as Moderate severity because exploitation requires authenticated local access to the graphics subsystem, and the primary impact is limited to a denial of service via system crash. The flaw resides in the Loongson display driver, which is specific to hardware architectures that are rarely deployed in standard Red Hat enterprise environments. Additionally, triggering the double-free condition relies on inducing a synchronous failure during buffer object initialization, further constraining practical exploitability.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 4.7 | N/A | N/A |
| Attack Vector | Local | N/A | N/A |
| Attack Complexity | High | N/A | N/A |
| Privileges Required | Low | N/A | N/A |
| User Interaction | None | N/A | N/A |
| Scope | Unchanged | N/A | N/A |
| Confidentiality | None | N/A | N/A |
| Integrity Impact | None | N/A | N/A |
| Availability Impact | High | N/A | N/A |
Vector
Red Hat: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
Understanding the Weakness (CWE)
Availability,Integrity
Technical Impact: DoS: Crash, Exit, or Restart
Integrity
Technical Impact: Modify Memory; Modify Application Data
Depending on the type of resource and the expected API behavior, this could lead to memory corruption, data corruption, or execution path corruption.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.