CVE-2026-43497: fbdev: udlfb: add vm_ops to dlfb_ops_mmap to prevent use-after-free
In the Linux kernel, the following vulnerability has been resolved:
fbdev: udlfb: add vm_ops to dlfb_ops_mmap to prevent use-after-free
dlfb_ops_mmap() uses remap_pfn_range() to map vmalloc framebuffer pages
to userspace but sets no vm_ops on the VMA. This means the kernel cannot
track active mmaps. When dlfb_realloc_framebuffer() replaces the backing
buffer via FBIOPUT_VSCREENINFO, existing mmap PTEs are not invalidated.
On USB disconnect, dlfb_ops_destroy() calls vfree() on the old pages
while userspace PTEs still reference them, resulting in a use-after-free:
the process retains read/write access to freed kernel pages.
Add vm_operations_struct with open/close callbacks that maintain an
atomic mmap_count on struct dlfb_data. In dlfb_realloc_framebuffer(),
check mmap_count and return -EBUSY if the buffer is currently mapped,
preventing buffer replacement while userspace holds stale PTEs.
Tested with PoC using dummy_hcd + raw_gadget USB device emulation.
Security readout for executives and security teams
Plain-English summary
A flaw in Linux's USB DisplayLink framebuffer driver can leave applications connected to memory after the kernel frees it. A local user could potentially read or alter sensitive kernel memory or crash the system. Exposure depends on the udlfb driver being used and a specific framebuffer replacement and USB-disconnection condition occurring.
Executive priority
Prioritize systems that use USB DisplayLink graphics, permit untrusted local users, or expose framebuffer devices broadly. Patch through normal urgent kernel-maintenance channels. Fleet-wide emergency action is less justified where udlfb is absent, but inventory promptly because successful exploitation could compromise confidentiality, integrity, and availability.
Technical view
dlfb_ops_mmap() mapped vmalloc framebuffer pages without VMA callbacks, preventing tracking and invalidation of active mappings. Buffer reallocation followed by USB disconnect could free pages still referenced by userspace PTEs, causing kernel-memory use-after-free. The stable fixes add mapping reference tracking and reject reallocation with EBUSY while mappings remain active.
Likely exposure
Likely exposure is limited to Linux systems using the udlfb USB DisplayLink framebuffer driver where a locally privileged-enough process can access the framebuffer device. The supplied CVSS requires local access, low complexity, low privileges, and user interaction. The version data lists affected kernels from 4.19 through 7.1, but administrators should confirm distribution-specific status.
Exploitation context
The sources describe a proof of concept tested with emulated USB hardware, demonstrating technical feasibility. No supplied source establishes malicious exploitation in the wild, and the bundle marks the CVE as absent from KEV. Successful abuse requires local access and interaction with the affected framebuffer and USB-device lifecycle.
Researcher notes
The flaw is a stale userspace mapping to freed vmalloc-backed kernel pages. The corrective design tracks VMA open and close operations with an atomic mapping count and blocks framebuffer replacement while mapped. The source bundle identifies stable commits but does not provide distribution package mappings or evidence of real-world attacks.
Mitigation direction
Install a vendor kernel update containing the applicable referenced stable fix.
Check distribution guidance to identify the corrected package for each deployed kernel branch.
Until patched, restrict untrusted access to affected framebuffer devices and DisplayLink USB workflows.
If udlfb is unnecessary, ask the platform vendor whether disabling it is an appropriate temporary control.
Validation and detection
Inventory systems for affected kernel versions and the udlfb driver.
Determine whether USB DisplayLink framebuffer devices are deployed or permitted.
Verify the installed kernel includes the distribution's backport of the referenced fix.
Review framebuffer device permissions for unnecessary local-user access.
After updating, confirm systems booted into the corrected kernel.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-43497 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
9Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.