LiveActive security incident?Get immediate response
CVE Record

CVE-2026-46218: drm/amdgpu: Add bounds checking to ib_{get,set}_value

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Add bounds checking to ib_{get,set}_value The uvd/vce/vcn code accesses the IB at predefined offsets without checking that the IB is large enough. Check the bounds here. The caller is responsible for making sure it can handle arbitrary return values. Also make the idx a uint32_t to prevent overflows causing the condition to fail.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A flaw in Linux’s AMD GPU driver can let a locally authenticated, low-privilege user trigger memory access outside an expected command buffer. The supplied CVSS assessment indicates possible exposure of sensitive information and system disruption, but no integrity impact. This is primarily a concern for multi-user or workload-hosting systems with affected AMD graphics hardware and drivers.

Executive priority

Treat as a high-priority local privilege-boundary issue, especially on shared Linux systems with AMD GPUs. It does not warrant remote-emergency handling based on current evidence, but confidentiality and availability impacts justify timely patching. Ask infrastructure teams to identify AMDGPU exposure and confirm vendor-fixed kernels rather than relying only on version strings.

Technical view

AMDGPU UVD, VCE, and VCN code accessed indirect buffers at predefined offsets without first confirming sufficient buffer length. The correction adds bounds checks to ib_get_value and ib_set_value and changes the index to uint32_t, preventing overflow from defeating validation. CVSS 3.1 is 7.1: local, low complexity, low privileges, no user interaction, with high confidentiality and availability impact.

Likely exposure

Likely exposure is limited to Linux systems using the AMDGPU driver and relevant UVD, VCE, or VCN paths on affected kernel branches. The supplied affected-version list spans multiple kernel lines but does not clearly express every fixed boundary. Distribution backports may also change exposure, so kernel version alone is insufficient.

Exploitation context

The supplied assessment requires local access and low privileges; it does not describe remote exploitation. CVE-2026-46218 is not listed as KEV in the bundle, and no supplied source reports active exploitation or a public exploit. Practical exploitability and prerequisites beyond the affected driver paths remain unconfirmed.

Researcher notes

Review the UVD, VCE, and VCN call paths reaching ib_get_value and ib_set_value, including caller handling of arbitrary return values. The source identifies missing bounds checks and index-overflow hardening but provides no demonstrated crash, disclosure primitive, exploit chain, or affected-hardware matrix. Exact distribution exposure requires backport analysis.

Mitigation direction

  • Upgrade to a vendor-supported kernel containing the applicable upstream stable fix.
  • Check distribution security advisories because fixes may be backported without changing to an obvious upstream version.
  • Prioritize shared, multi-user, or workload-hosting systems that load AMDGPU.
  • Follow Linux or distribution guidance if an upgrade cannot be deployed promptly.

Validation and detection

  • Inventory Linux hosts with AMD graphics hardware and the AMDGPU module loaded.
  • Record running kernel builds and map them to distribution advisories or supplied stable commits.
  • Confirm the installed kernel package includes the bounds-checking fix or an equivalent backport.
  • After remediation, reboot where required and verify the intended fixed kernel is running.
Prepared
Confidence
medium
Sources
8

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-2026-46218 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.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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
0ADP providers
7Source links

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.1CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H1.85.2Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.1High
CVSS 3.1 vector shape for CVE-2026-46218Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxd38ceaf99ed015f2a0b9af3499791bd3a3daae21, d38ceaf99ed015f2a0b9af3499791bd3a3daae21, d38ceaf99ed015f2a0b9af3499791bd3a3daae21, d38ceaf99ed015f2a0b9af3499791bd3a3daae21, d38ceaf99ed015f2a0b9af3499791bd3a3daae21, d38ceaf99ed015f2a0b9af3499791bd3a3daae21unaffected
LinuxLinux4.2, 0, 6.1.175, 6.6.140, 6.12.90, 6.18.32, 7.0.9, 7.1affected
Weakness

CWE details

No CWE listed

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