CVE-2026-46006: drm/nouveau: fix u32 overflow in pushbuf reloc bounds check
In the Linux kernel, the following vulnerability has been resolved:
drm/nouveau: fix u32 overflow in pushbuf reloc bounds check
nouveau_gem_pushbuf_reloc_apply() validates each relocation with
if (r->reloc_bo_offset + 4 > nvbo->bo.base.size)
but reloc_bo_offset is __u32 (uapi/drm/nouveau_drm.h) and the integer
literal 4 promotes to unsigned int, so the addition is performed in 32
bits and wraps before the comparison against the size_t bo size.
Cast to u64 so the addition happens in 64-bit arithmetic.
[ Add Fixes: tag. - Danilo ]
Security readout for executives and security teams
Plain-English summary
A local, low-privileged user may be able to bypass a Nouveau graphics-driver bounds check because a large offset can wrap to a small value. The supplied CVSS assessment indicates potential compromise of confidentiality, integrity, and availability. This is not described as remotely exploitable.
Executive priority
Treat as a high-priority local privilege-boundary issue, especially on shared workstations, rendering hosts, and multi-tenant systems using Nouveau. It warrants prompt patch validation, but the available evidence does not support emergency internet-wide incident response.
Technical view
In nouveau_gem_pushbuf_reloc_apply(), adding 4 to the 32-bit reloc_bo_offset can overflow before comparison with the buffer object's size. The wrapped result may incorrectly pass validation. The Linux stable fix performs the addition using 64-bit arithmetic.
Likely exposure
Exposure is most likely on Linux systems using the Nouveau DRM driver where untrusted local users or workloads can access the affected graphics interface. The bundle does not provide sufficient distribution package ranges to identify vulnerable installations solely by kernel version.
Exploitation context
The CVSS vector requires local access and low privileges, without user interaction. The supplied record is not in CISA KEV, and the sources provide no evidence of active exploitation or a public exploit. Internet exposure alone does not establish reachability.
Researcher notes
The defect is a 32-bit unsigned addition wrap in a relocation bounds check. The fix casts the calculation to 64 bits. Exact affected distribution builds, practical exploitability, and exploitation in the wild are not established by the supplied bundle; validate against vendor backports rather than version strings alone.
Mitigation direction
Install a distribution kernel containing the applicable upstream stable fix.
Confirm the corrected package and reboot requirements through Linux distribution guidance.
Prioritize multi-user systems running Nouveau with untrusted local workloads.
If updates are delayed, obtain vendor-approved exposure-reduction guidance.
Validation and detection
Identify systems where the Nouveau kernel module is present and active.
Record running kernel and distribution package versions.
Map each package to the vendor advisory or applicable stable fix.
Confirm the remediated kernel is running after maintenance.
Review local telemetry for unexplained GPU-driver crashes without treating them as proof of exploitation.
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-46006 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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
9Source 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.