CyberSecBulletin
CVE-2026-46006NVD status: Modified

Linux: Out-of-bounds Write

Published Updated By the CyberSecBulletin desk

CVE-2026-46006 is a high-severity out-of-bounds write vulnerability in Linux, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions 3429275684f4bad42876955301f3c5c814aae909, 573a1104bd36e49c067a9dc62e7c476d5ee7e92a, 45a45184b9c0b0b26ead06e370cda2073616a7cc as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.14% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Linux to 3429275684f4bad42876955301f3c5c814aae909 or 573a1104bd36e49c067a9dc62e7c476d5ee7e92a or 45a45184b9c0b0b26ead06e370cda2073616a7cc or fa297e919d1680c38ab268ff952b1698dac987f6, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 5.15.209 or 6.1.175 or 6.6.140 or 6.12.86, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinuxa1606a9596e54da90ad6209071b357a4c1b0fa82 up to, but not including, 3429275684f4bad42876955301f3c5c814aae909; a1606a9596e54da90ad6209071b357a4c1b0fa82 up to, but not including, 573a1104bd36e49c067a9dc62e7c476d5ee7e92a; a1606a9596e54da90ad6209071b357a4c1b0fa82 up to, but not including, 45a45184b9c0b0b26ead06e370cda2073616a7cc; a1606a9596e54da90ad6209071b357a4c1b0fa82 up to, but not including, fa297e919d1680c38ab268ff952b1698dac987f6; a1606a9596e54da90ad6209071b357a4c1b0fa82 up to, but not including, d749a9a0ee4014681487e7ae549901aa8c176637; a1606a9596e54da90ad6209071b357a4c1b0fa82 up to, but not including, 332884f5eb79dd60a7162b079d09d39208567a31; a1606a9596e54da90ad6209071b357a4c1b0fa82 up to, but not including, e441d5c23ec644c8d27593db3b8928e8933512a9; a1606a9596e54da90ad6209071b357a4c1b0fa82 up to, but not including, 2fc87d37be1b730a149b035f9375fdb8cc5333a5; and 1 more ranges3429275684f4bad42876955301f3c5c814aae909, 573a1104bd36e49c067a9dc62e7c476d5ee7e92a, 45a45184b9c0b0b26ead06e370cda2073616a7cc, fa297e919d1680c38ab268ff952b1698dac987f6, d749a9a0ee4014681487e7ae549901aa8c176637, 332884f5eb79dd60a7162b079d09d39208567a31
LinuxLinux Kernel2.6.34 up to, but not including, 5.15.209; 5.16 up to, but not including, 6.1.175; 6.2 up to, but not including, 6.6.140; 6.7 up to, but not including, 6.12.86; 6.13 up to, but not including, 6.18.27; 6.19 up to, but not including, 7.0.45.15.209, 6.1.175, 6.6.140, 6.12.86, 6.18.27, 7.0.4

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

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

Official description

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 ]

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Out-of-bounds Write

The product writes data past the end, or before the beginning, of the intended buffer.

How developers prevent this class of flaw

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
  • Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.

More Out-of-bounds Write vulnerabilities (CWE-787)

Timeline

  1. CVE record published.
  2. Record last changed materially (score, affected products, status or references).

References

Recent Out-of-bounds Write vulnerabilities

Spotted an error? Tell us.