LiveActive security incident?Get immediate response
CVE Record

CVE-2024-58091: drm/fbdev-dma: Add shadow buffering for deferred I/O

In the Linux kernel, the following vulnerability has been resolved: drm/fbdev-dma: Add shadow buffering for deferred I/O DMA areas are not necessarily backed by struct page, so we cannot rely on it for deferred I/O. Allocate a shadow buffer for drivers that require deferred I/O and use it as framebuffer memory. Fixes driver errors about being "Unable to handle kernel NULL pointer dereference at virtual address" or "Unable to handle kernel paging request at virtual address". The patch splits drm_fbdev_dma_driver_fbdev_probe() in an initial allocation, which creates the DMA-backed buffer object, and a tail that sets up the fbdev data structures. There is a tail function for direct memory mappings and a tail function for deferred I/O with the shadow buffer. It is no longer possible to use deferred I/O without shadow buffer. It can be re-added if there exists a reliably test for usable struct page in the allocated DMA-backed buffer object.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects DRM framebuffer DMA handling. Some graphics/framebuffer drivers could hit kernel memory faults because deferred I/O assumed DMA memory had normal page backing. The public record describes crashes or paging errors, not data theft, remote compromise, or active exploitation.

Executive priority

Treat this as a kernel stability and availability risk until vendor severity is clarified. It is not currently supported as an emergency internet-exposed exploitation issue by the supplied sources, but kernel fleet owners should include it in normal security patch cycles.

Technical view

The vulnerable path is drm/fbdev-dma deferred I/O. DMA-backed framebuffer memory may not have usable struct page backing, so deferred I/O can dereference invalid or missing page state. The fix adds a shadow buffer for deferred I/O and prevents deferred I/O without that buffer.

Likely exposure

Exposure appears limited to Linux systems running affected kernel builds with DRM fbdev DMA drivers that require deferred I/O. The supplied record lists Linux kernel versions/commits but does not identify specific distributions, devices, or remotely reachable attack surfaces.

Exploitation context

The source bundle does not show KEV listing, public exploitation, exploit maturity, attacker requirements, or a CVSS score. Based on the description, the known impact is kernel NULL pointer or paging-request errors in affected driver paths.

Researcher notes

The record is sparse: no CVSS, CWE, exploit conditions, or distribution mapping are provided. Analysis should focus on the upstream stable commits, affected kernel branches, and whether local driver configurations exercise drm_fbdev_dma deferred I/O.

Mitigation direction

  • Update to a Linux kernel build containing the referenced stable fixes.
  • Check Linux distribution advisories for packaged kernel availability and backport status.
  • Prioritize systems using affected DRM framebuffer DMA/deferred I/O functionality.
  • Monitor vendor guidance for any added severity, exploitability, or workaround details.

Validation and detection

  • Inventory Linux kernel versions across servers, endpoints, appliances, and embedded systems.
  • Identify systems using DRM fbdev DMA drivers or framebuffer deferred I/O paths.
  • Compare installed kernels with distribution advisories and referenced stable commits.
  • Review kernel logs for NULL pointer dereference or paging request errors in fbdev-dma paths.
Prepared
Confidence
medium
Sources
5

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-2024-58091 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

0CVSS vectors
3Timeline events
0ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux5ab91447aa13b8b98bc11f5326f33500b0ee2c48, 5ab91447aa13b8b98bc11f5326f33500b0ee2c48, 5ab91447aa13b8b98bc11f5326f33500b0ee2c48unaffected
LinuxLinux6.11, 0, 6.12.36, 6.13.6, 6.14affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.