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.
Security readout for executives and security teams
Plain-English summary
A Linux graphics framebuffer flaw can trigger kernel invalid-memory faults when deferred display updates use DMA memory lacking normal page metadata. The supplied CVSS score is 7.8 because a locally authenticated user may potentially affect confidentiality, integrity, and availability. Actual risk depends on the graphics driver, hardware, and deferred-I/O path being used.
Executive priority
Treat as high priority on exposed multi-user systems using the relevant graphics path, especially where local users are not fully trusted. Patch through supported kernel or distribution channels. Systems without the affected driver and deferred-I/O combination are lower priority, but should be validated rather than assumed safe.
Technical view
The DRM fbdev DMA implementation assumed DMA-backed framebuffer memory had usable struct page metadata for deferred I/O. That assumption can cause NULL-pointer dereferences or kernel paging requests. The referenced fix allocates a shadow framebuffer for deferred I/O and separates direct-mapping setup from shadow-buffer setup, preventing deferred I/O without the shadow buffer.
Likely exposure
Exposure is limited to Linux systems using affected DRM fbdev DMA drivers with deferred I/O. The bundle identifies 6.11, 6.12.36, 6.13.6, and 6.14 among affected version data, but also contains an ambiguous "0" entry. It does not establish that every installation of these kernels is vulnerable.
Exploitation context
The CVSS vector requires local access, low privileges, low complexity, and no user interaction. The CVE is not listed as KEV in the supplied bundle, and no cited evidence establishes public or active exploitation. Reported outcomes are kernel NULL-pointer dereferences and paging faults.
Researcher notes
The source bundle supplies no CWE, exploit evidence, or reproduction details. Although CVSS records high confidentiality, integrity, and availability impacts, the description directly documents invalid-memory kernel faults rather than demonstrated data compromise. Exact vulnerable and fixed release boundaries remain insufficiently clear; validate against the referenced commits and distributor backports.
Mitigation direction
Apply a Linux stable update or distribution backport containing the referenced shadow-buffer fix.
Check Linux distributor guidance for exact fixed packages and supported release mappings.
Prioritize systems where untrusted local users can access the affected graphics environment.
If updates are delayed, reduce untrusted local access; no product-specific workaround is supplied.
Validation and detection
Record the running kernel release and compare it with vendor-specific affected and fixed version guidance.
Determine whether the system uses a DRM fbdev DMA driver with deferred I/O.
Verify the installed kernel contains the applicable referenced fix or an equivalent distributor backport.
Review kernel logs for NULL-pointer dereferences or paging requests associated with the graphics path.
After updating, retest affected display workloads and confirm the fault no longer occurs.
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.
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
4Source 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.