LiveActive security incident?Get immediate response
CVE Record

CVE-2024-42227: drm/amd/display: Fix overlapping copy within dml_core_mode_programming

In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix overlapping copy within dml_core_mode_programming [WHY] &mode_lib->mp.Watermark and &locals->Watermark are the same address. memcpy may lead to unexpected behavior. [HOW] memmove should be used.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects AMD display code and was fixed by changing an unsafe memory copy to an overlap-safe copy. The public sources do not provide severity, CVSS, attacker prerequisites, or business impact. Treat it as a kernel maintenance risk, especially for systems using AMD graphics/display functionality.

Executive priority

Schedule remediation through normal kernel patching unless your environment depends heavily on AMD display systems or vendor advisories raise severity. Current public evidence does not support emergency treatment, but incomplete severity data means exposure should still be tracked.

Technical view

In drm/amd/display dml_core_mode_programming, the source notes that mode_lib->mp.Watermark and locals->Watermark can be the same address. Using memcpy on overlapping memory may produce unexpected behavior. The stated fix is to use memmove. No CWE, CVSS, or detailed impact is provided.

Likely exposure

Exposure appears limited to Linux kernels carrying the affected AMD display code and versions identified in the CVE bundle. Practical exposure is most relevant where AMD GPU/display functionality is present. The sources do not define remote, local, authenticated, or hardware-specific attack requirements.

Exploitation context

The source bundle marks KEV as false and provides no evidence of active exploitation. The public description does not describe exploitability, attacker control, or security impact beyond unexpected behavior from overlapping memory copy. Avoid assuming exploit status or impact severity.

Researcher notes

The useful technical signal is narrow: overlapping memcpy in AMD display mode programming, fixed with memmove. The public record lacks impact analysis, reachable call paths, privilege boundary, and exploitability details. Validation should focus on source or package-level presence of the stable fix.

Mitigation direction

  • Update affected Linux kernels to vendor releases containing the referenced stable fixes.
  • Prioritize systems using AMD GPU or display functionality.
  • Track Linux distribution advisories for backported kernel packages and reboot requirements.
  • For custom kernels, verify the referenced memmove fix is included.
  • If updates are unavailable, follow vendor guidance rather than applying unsupported workarounds.

Validation and detection

  • Inventory Linux kernel versions and identify hosts using AMD display drivers.
  • Check whether kernel packages include the referenced stable commits or downstream backports.
  • Review distribution security advisories for CVE-2024-42227 applicability.
  • Confirm updated systems reboot into the fixed kernel.
  • Document any systems deferred from patching and their AMD display exposure.
Prepared
Confidence
medium
Sources
4

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-42227 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
2ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux7966f319c66d9468623c6a6a017ecbc0dd79be75, 7966f319c66d9468623c6a6a017ecbc0dd79be75unaffected
LinuxLinux6.7, 0, 6.9.9, 6.10affected
Weakness

CWE details

No CWE listed

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