Security readout for executives and security teams
Plain-English summary
A Linux AMD display-driver array was sized for surfaces per stream instead of planes per graphics chip. When more than three planes are present, the array can overflow. The supplied CVSS 3.1 score is 7.8, reflecting potentially serious confidentiality, integrity, and availability impact from a local, low-privileged attacker.
Executive priority
Treat this as a high-priority endpoint remediation issue, especially for AMD graphical workstations or shared systems where untrusted local users can obtain accounts. It is less urgent for systems without the relevant AMD display path. There is no supplied evidence of active exploitation, so prioritize by confirmed hardware, driver, and kernel exposure.
Technical view
The AMD DRM display code allocated mpc_combine using MAX_SURFACES although it records all planes per ASIC. Configurations exceeding three planes can overflow the array. The upstream correction sizes it with MAX_PLANES. The supplied record identifies affected Linux kernel versions beginning at 4.15 and includes versions through 6.7.6 and 6.8, but downstream backports may alter exposure.
Likely exposure
Exposure is most plausible on systems using affected Linux kernels, the AMD display subsystem, and display configurations capable of more than three planes. Servers without relevant AMD display hardware or driver use are less likely exposed. Confirm distribution-specific backports because kernel version strings alone may be inconclusive.
Exploitation context
The CVSS vector indicates local access, low attack complexity, low privileges, and no user interaction. The supplied record does not place this CVE in KEV and provides no evidence of active exploitation. The exact path from the array overflow to the scored impacts is not documented in the bundle.
Researcher notes
The core defect is a bounds mismatch: MAX_SURFACES is per stream, while mpc_combine tracks planes per ASIC and requires MAX_PLANES. The bundle does not identify a CWE, exploitation proof, crash signature, or affected distribution packages. Stable commit references support the correction, but researchers should account for downstream backports when determining vulnerable builds.
Mitigation direction
- Install a vendor-supported kernel containing the MAX_PLANES correction or an equivalent downstream backport.
- Review Linux distribution advisories for the exact fixed package version.
- Prioritize AMD graphical workstations and other systems using the affected display subsystem.
- Where immediate updating is impossible, consult vendor guidance for supported temporary mitigations.
Validation and detection
- Inventory Linux kernel versions and identify systems using AMD display hardware and drivers.
- Verify whether the installed kernel source or package includes either referenced stable correction.
- Check distribution security advisories and package changelogs for CVE-2024-26914 backports.
- Assess whether deployed display configurations can use more than three planes.
- After updating, confirm the system booted into the corrected kernel package.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2024-26914 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9LinuxVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/0bd8ef618a42d7e6ea3f701065264e15678025e3CVE reference, Linux
- https://git.kernel.org/stable/c/39079fe8e660851abbafa90cd55cbf029210661fCVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.