CVE-2026-99305

Description

A flaw was found in the Linux kernel's udlfb (DisplayLink framebuffer) driver. When updating display modes, the driver destroys the existing mode list before verifying whether the framebuffer is currently in use. A local unprivileged user can exploit this vulnerability by writing to the device's sysfs interface, leaving dangling references to memory that has already been freed. Subsequent console switching accesses this freed memory, resulting in a use-after-free condition that can lead to a system crash and Denial of Service (DoS).

Statement

This vulnerability is rated as Moderate because it requires local system access with permissions to interact with the sysfs interface and relies on the presence of specific DisplayLink USB display hardware. The flaw is confined to the udlfb framebuffer driver, which is typically not loaded or utilized on default enterprise server installations unless specialized DisplayLink video devices are connected. Successful exploitation by an unprivileged local user results in a kernel crash, causing a denial of service without compromising system confidentiality or data integrity.

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 HatNVDcve.org
Base Score5.5N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityLowN/AN/A
Privileges RequiredLowN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityNoneN/AN/A
Integrity ImpactNoneN/AN/A
Availability ImpactHighN/AN/A

Vector

Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory

If the expired pointer is used in a read operation, an attacker might be able to control data read in by the application.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If the expired pointer references a memory location that is not accessible to the product, or points to a location that is "malformed" (such as NULL) or larger than expected by a read or write operation, then a crash may occur.

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If the expired pointer is used in a function call, or points to unexpected data in a write operation, then code execution may be possible.

Frequently Asked Questions

Want to get errata notifications? Sign up here.