In the Linux kernel, the following vulnerability has been resolved:
drm/buddy: Fix alloc_range() error handling code
Few users have observed display corruption when they boot
the machine to KDE Plasma or playing games. We have root
caused the problem that whenever alloc_range() couldn't
find the required memory blocks the function was returning
SUCCESS in some of the corner cases.
The right approach would be if the total allocated size
is less than the required size, the function should
return -ENOSPC.
Security readout for executives and security teams
Plain-English summary
A Linux graphics-memory allocator could report success even when it failed to reserve enough memory. Users observed display corruption during KDE Plasma startup and gaming. The supplied record rates the issue high, but the public description does not independently demonstrate the claimed confidentiality, integrity, and availability impacts.
Executive priority
Treat as a high-priority maintenance update for affected Linux graphical systems, especially where untrusted local users exist. Immediate emergency response is not supported by the supplied evidence because active exploitation is unconfirmed and observed impact is display corruption. Resolve exact exposure through distribution-specific advisories.
Technical view
In drm/buddy alloc_range(), some corner cases returned success when total allocated memory was below the requested size. The correction returns -ENOSPC for an incomplete allocation. The supplied CVSS 3.1 vector is 7.8 and describes local, low-privilege exploitation without user interaction, although the sources provided do not explain a proven security exploitation path.
Likely exposure
Potential exposure is limited to systems running affected Linux kernel versions and exercising the DRM buddy allocator, particularly graphical or gaming workloads. The bundle names 6.7, 6.7.6, and 6.8, but its flattened version data does not clearly express exact affected and fixed ranges. Distribution backports may alter exposure.
Exploitation context
CISA KEV status is false, and the supplied sources provide no evidence of active exploitation or a public exploit. Reported real-world symptoms are display corruption. Although the CVSS vector indicates a local, low-privilege attack scenario, the provided material does not establish how an attacker could reliably trigger or weaponize the condition.
Researcher notes
The key invariant is that alloc_range() must fail when total allocated size is below the request. Review callers for unsafe assumptions after a false success. The supplied 7.8 CVSS claims high confidentiality, integrity, and availability impact, but the narrative and commits presented here primarily substantiate allocation error handling and display corruption; additional impact evidence is incomplete.
Mitigation direction
Apply a vendor-supported kernel update containing the applicable stable fix.
Check distribution advisories for backports and precise affected package versions.
Prioritize graphical workstations or gaming systems showing display corruption.
Use vendor guidance if an immediate kernel update is unavailable.
Validation and detection
Record the running kernel and distribution package release.
Compare package changelogs against both cited stable fix commits.
Confirm vendor advisories identify the installed build as fixed or unaffected.
Monitor affected systems for recurring display corruption after updating.
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-26911 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.
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.