LiveActive security incident?Get immediate response
CVE Record

CVE-2024-50282: drm/amdgpu: add missing size check in amdgpu_debugfs_gprwave_read()

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: add missing size check in amdgpu_debugfs_gprwave_read() Avoid a possible buffer overflow if size is larger than 4K. (cherry picked from commit f5d873f5825b40d886d03bd2aede91d4cf002434)

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A missing bounds check in the Linux AMD GPU debug interface can allow a locally authenticated, low-privileged user to trigger a buffer overflow. Successful exploitation could seriously affect system confidentiality, integrity, or availability. Systems without the affected AMD GPU driver path are less likely to be exposed.

Executive priority

Treat as a high-priority local privilege-boundary risk on shared or untrusted-user AMD GPU systems. Patch those systems promptly through supported kernel channels. Internet-facing status alone does not increase direct reachability because the documented attack vector is local.

Technical view

CVE-2024-50282 is a CWE-120 buffer overflow in amdgpu_debugfs_gprwave_read(). The function could process a size larger than its 4 KiB buffer. The supplied CVSS 3.1 score is 7.8, with local access and low privileges required. Linux stable commits add the missing size check.

Likely exposure

Prioritize Linux systems using AMD GPUs and affected kernel builds, particularly multi-user workstations, compute nodes, and other hosts granting local accounts. Exposure depends on the amdgpu debugfs path being present and accessible. The supplied version data is ambiguous, so confirm status through distribution advisories and fix-commit provenance.

Exploitation context

The CVSS vector indicates a local, low-complexity attack requiring low privileges and no user interaction. The bundle marks this CVE as absent from KEV and provides no evidence of active exploitation or public weaponization. Real-world reachability and exploit reliability are not established by the supplied sources.

Researcher notes

The source describes an oversized read exceeding 4 KiB in an AMDGPU debugfs handler. The supplied affected-version representation contains ambiguous values and duplicated commit identifiers, preventing a reliable universal version range. Assess branches through stable fix commits and distribution backports. The sources do not establish exploitability beyond the possible overflow or specify a demonstrated exploitation outcome.

Mitigation direction

  • Install a vendor-supported kernel update that incorporates the applicable Linux stable fix.
  • Check your distribution's advisory for the exact fixed package and required reboot.
  • Until updated, limit untrusted local accounts on potentially affected AMD GPU systems.
  • Follow vendor guidance for any supported interim control; none is explicitly documented in the bundle.

Validation and detection

  • Inventory running kernel versions and identify systems where the amdgpu driver is active.
  • Map installed kernel packages against distribution advisories and the cited stable commits.
  • After updating, reboot and confirm the fixed kernel is running.
  • Verify vulnerability scanners use distribution backport status, not version strings alone.
Prepared
Confidence
medium
Sources
8

Public sources used

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.

cwe · low confidence lookup

CWE-120: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-50282 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
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

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.

2CVSS vectors
3Timeline events
2ADP providers
7Source links

SSVC decision data

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

CVSS vector scores

2 official scores

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.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2024-50282Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxd38ceaf99ed015f2a0b9af3499791bd3a3daae21, d38ceaf99ed015f2a0b9af3499791bd3a3daae21, d38ceaf99ed015f2a0b9af3499791bd3a3daae21, d38ceaf99ed015f2a0b9af3499791bd3a3daae21unaffected
LinuxLinux4.2, 0, 4.19.324, 6.6.61, 6.11.8, 6.12affected
Weakness

CWE details

CWE-120

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

CWE-120 · source CWE mapping

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs