LiveActive security incident?Get immediate response
CVE Record

CVE-2026-46237: drm/amdgpu/vcn3: Avoid overflow on msg bound check

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/vcn3: Avoid overflow on msg bound check As pointed out by SDL, the previous condition may be vulnerable to overflow. (cherry picked from commit db00257ac9e4a51eb2515aaea161a019f7125e10)

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel flaw in AMD GPU video-codec handling. A local low-privileged user may be able to trigger an integer overflow in a bounds check, creating risk of sensitive data exposure or system disruption. It is high severity, but the provided sources do not show active exploitation.

Executive priority

Prioritize remediation on shared Linux workstations, GPU servers, and environments where low-privileged users or workloads run on the same host. This is not shown as actively exploited, but the potential confidentiality and availability impact warrants normal high-severity patch timelines.

Technical view

The amdgpu VCN3 message boundary validation used a condition that could overflow, weakening the intended bounds check. The CVSS vector is local, low complexity, low privilege, no user interaction, unchanged scope, with high confidentiality and availability impact. Kernel stable commits are referenced as resolution points.

Likely exposure

Exposure is likely limited to Linux systems running affected kernel builds with the amdgpu VCN3 driver path present and reachable by local authenticated users. Internet-facing remote exploitation is not indicated by the CVSS vector or provided sources.

Exploitation context

The source bundle marks KEV as false and provides no cited evidence of exploitation in the wild. The risk model is local post-authentication abuse, not unauthenticated remote compromise. Exploitability details are incomplete in the public record provided.

Researcher notes

The public description is brief and does not assign a CWE. Analysis should focus on the amdgpu VCN3 message bound check fixed in the referenced stable commits. Avoid expanding scope beyond Linux kernel AMDGPU VCN3 paths unless additional vendor evidence appears.

Mitigation direction

  • Apply kernel or distribution updates that include the referenced stable commits.
  • Check Linux distribution advisories for patched kernel package availability.
  • Prioritize multi-user systems with AMD GPUs or exposed local workloads.
  • Treat untrusted local shell access as higher risk until patched.
  • Do not assume unrelated kernel versions are affected without vendor confirmation.

Validation and detection

  • Inventory Linux hosts for affected kernel versions and AMDGPU usage.
  • Check kernel package changelogs for CVE-2026-46237 or referenced commit IDs.
  • Confirm the deployed kernel includes the corrected amdgpu VCN3 bounds check.
  • Review vulnerability scanner results against vendor kernel advisories.
  • Record systems without AMDGPU exposure separately from confirmed affected hosts.
Prepared
Confidence
medium
Sources
7

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.

cve · low confidence lookup

CVE-2026-46237 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
6Source 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-46237Attack 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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux638d3e0b9eb77aa53fdd60e2b928761d16ba76fa, 870c8738c3774336baedddd0240951d078a703b8, 638e48ee39d0f2af9336f917a6f5d6692dd64d93, e382e0b81a3e7bd21504fee1d01ae8b08f84d3a7, b193019860d61e92da395eae2011f2f6716b182funaffected
LinuxLinux7.1-rc1, 0, 7.1-rc2affected
Weakness

CWE details

No CWE listed

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