LiveActive security incident?Get immediate response
CVE Record

CVE-2024-46725: drm/amdgpu: Fix out-of-bounds write warning

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Fix out-of-bounds write warning Check the ring type value to fix the out-of-bounds write warning

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A flaw in the Linux AMD GPU driver can write outside an intended memory boundary when processing an invalid ring type. A local, low-privileged user may be able to trigger serious confidentiality, integrity, or availability impacts. Systems without the AMDGPU driver or affected kernel code are unlikely to be exposed.

Executive priority

Treat as a prompt patching priority for exposed AMD GPU systems, especially shared hosts where untrusted local users have accounts. It is not supported as an emergency internet-wide threat because exploitation requires local access and active exploitation is not documented.

Technical view

The drm/amdgpu code did not adequately validate a ring-type value, producing an out-of-bounds write warning. The kernel fix adds a ring-type check. CVSS 3.1 rates the issue 7.8: local access, low complexity, low privileges, no user interaction, and potentially high confidentiality, integrity, and availability impact.

Likely exposure

Prioritize Linux workstations, GPU compute hosts, and multi-user systems that load amdgpu while running affected kernel builds. The supplied version data does not establish complete distribution-specific package ranges, so compare the active kernel against vendor advisories and fixed commits.

Exploitation context

The supplied record does not identify CISA KEV listing or active exploitation. The CVSS vector describes local, low-privileged access rather than remote exploitation. No public exploit evidence is provided in the source bundle.

Researcher notes

The public description is terse and provides no reproducer, affected call path, CWE, or demonstrated impact. Multiple stable-tree commits indicate backports across kernel lines. Exact exposure should be established by commit or distribution package status, not version-string assumptions.

Mitigation direction

  • Install a vendor-supported kernel package containing the applicable upstream stable fix.
  • Reboot into the updated kernel so the corrected amdgpu code becomes active.
  • Prioritize shared or untrusted-user systems with AMD GPUs.
  • Consult distribution guidance where fixed package status is unclear.

Validation and detection

  • Record the running kernel version and distribution package revision.
  • Confirm whether the amdgpu module is present and loaded.
  • Compare the active package with vendor advisories and applicable stable commits.
  • After reboot, verify the patched kernel is running.
  • Review kernel logs for recurring amdgpu out-of-bounds warnings.
Prepared
Confidence
medium
Sources
10

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-46725 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.

1CVSS vectors
3Timeline events
2ADP providers
9Source links

SSVC decision data

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

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.

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

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2024-46725Attack 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
other:ssvc
CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxd38ceaf99ed015f2a0b9af3499791bd3a3daae21, d38ceaf99ed015f2a0b9af3499791bd3a3daae21, d38ceaf99ed015f2a0b9af3499791bd3a3daae21, d38ceaf99ed015f2a0b9af3499791bd3a3daae21, d38ceaf99ed015f2a0b9af3499791bd3a3daae21, d38ceaf99ed015f2a0b9af3499791bd3a3daae21unaffected
LinuxLinux4.2, 0, 5.10.226, 5.15.167, 6.1.109, 6.6.50, 6.10.9, 6.11affected
Weakness

CWE details

No CWE listed

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