CVE Vulnerabilities

CVE-2025-23345

Out-of-bounds Read

Published: Oct 23, 2025 | Modified: Oct 27, 2025
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
RedHat/V2
RedHat/V3
6.6 MODERATE
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H
Ubuntu
MEDIUM

NVIDIA Display Driver for Windows and Linux contains a vulnerability in a video decoder, where an attacker might cause an out-of-bounds read. A successful exploit of this vulnerability might lead to information disclosure or denial of service.

Weakness

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

Affected Software

Name Vendor Start Version End Version
Nvidia-graphics-drivers-304 Ubuntu esm-infra/xenial *
Nvidia-graphics-drivers-304 Ubuntu upstream *
Nvidia-graphics-drivers-304-updates Ubuntu upstream *
Nvidia-graphics-drivers-340 Ubuntu esm-infra/bionic *
Nvidia-graphics-drivers-340 Ubuntu esm-infra/focal *
Nvidia-graphics-drivers-340 Ubuntu esm-infra/xenial *
Nvidia-graphics-drivers-340 Ubuntu upstream *
Nvidia-graphics-drivers-340-updates Ubuntu upstream *
Nvidia-graphics-drivers-352 Ubuntu upstream *
Nvidia-graphics-drivers-352-updates Ubuntu upstream *
Nvidia-graphics-drivers-361 Ubuntu upstream *
Nvidia-graphics-drivers-367 Ubuntu upstream *
Nvidia-graphics-drivers-375 Ubuntu upstream *
Nvidia-graphics-drivers-384 Ubuntu upstream *
Nvidia-graphics-drivers-390 Ubuntu esm-infra/bionic *
Nvidia-graphics-drivers-390 Ubuntu esm-infra/focal *
Nvidia-graphics-drivers-390 Ubuntu jammy *
Nvidia-graphics-drivers-390 Ubuntu upstream *
Nvidia-graphics-drivers-418-server Ubuntu esm-apps/bionic *
Nvidia-graphics-drivers-418-server Ubuntu esm-apps/focal *
Nvidia-graphics-drivers-418-server Ubuntu jammy *
Nvidia-graphics-drivers-418-server Ubuntu upstream *
Nvidia-graphics-drivers-430 Ubuntu esm-infra/bionic *
Nvidia-graphics-drivers-430 Ubuntu esm-infra/focal *
Nvidia-graphics-drivers-430 Ubuntu jammy *
Nvidia-graphics-drivers-430 Ubuntu upstream *
Nvidia-graphics-drivers-435 Ubuntu esm-apps/jammy *
Nvidia-graphics-drivers-435 Ubuntu esm-infra/bionic *
Nvidia-graphics-drivers-435 Ubuntu esm-infra/focal *
Nvidia-graphics-drivers-435 Ubuntu jammy *
Nvidia-graphics-drivers-435 Ubuntu upstream *
Nvidia-graphics-drivers-440 Ubuntu esm-infra/bionic *
Nvidia-graphics-drivers-440 Ubuntu esm-infra/focal *
Nvidia-graphics-drivers-440 Ubuntu jammy *
Nvidia-graphics-drivers-440 Ubuntu upstream *
Nvidia-graphics-drivers-440-server Ubuntu esm-apps/bionic *
Nvidia-graphics-drivers-440-server Ubuntu esm-apps/focal *
Nvidia-graphics-drivers-440-server Ubuntu esm-apps/jammy *
Nvidia-graphics-drivers-440-server Ubuntu jammy *
Nvidia-graphics-drivers-440-server Ubuntu upstream *
Nvidia-graphics-drivers-450 Ubuntu esm-infra/bionic *
Nvidia-graphics-drivers-450 Ubuntu esm-infra/focal *
Nvidia-graphics-drivers-450 Ubuntu jammy *
Nvidia-graphics-drivers-450 Ubuntu upstream *
Nvidia-graphics-drivers-450-server Ubuntu esm-infra/bionic *
Nvidia-graphics-drivers-450-server Ubuntu esm-infra/focal *
Nvidia-graphics-drivers-450-server Ubuntu jammy *
Nvidia-graphics-drivers-450-server Ubuntu upstream *
Nvidia-graphics-drivers-455 Ubuntu esm-apps/bionic *
Nvidia-graphics-drivers-455 Ubuntu esm-apps/focal *
Nvidia-graphics-drivers-455 Ubuntu jammy *
Nvidia-graphics-drivers-455 Ubuntu upstream *
Nvidia-graphics-drivers-460 Ubuntu esm-infra/bionic *
Nvidia-graphics-drivers-460 Ubuntu esm-infra/focal *
Nvidia-graphics-drivers-460 Ubuntu jammy *
Nvidia-graphics-drivers-460 Ubuntu upstream *
Nvidia-graphics-drivers-460-server Ubuntu esm-infra/bionic *
Nvidia-graphics-drivers-460-server Ubuntu esm-infra/focal *
Nvidia-graphics-drivers-460-server Ubuntu upstream *
Nvidia-graphics-drivers-470 Ubuntu esm-infra/bionic *
Nvidia-graphics-drivers-470 Ubuntu esm-infra/focal *
Nvidia-graphics-drivers-470 Ubuntu jammy *
Nvidia-graphics-drivers-470 Ubuntu noble *
Nvidia-graphics-drivers-470 Ubuntu upstream *
Nvidia-graphics-drivers-470-server Ubuntu esm-infra/bionic *
Nvidia-graphics-drivers-470-server Ubuntu esm-infra/focal *
Nvidia-graphics-drivers-470-server Ubuntu jammy *
Nvidia-graphics-drivers-470-server Ubuntu noble *
Nvidia-graphics-drivers-470-server Ubuntu upstream *
Nvidia-graphics-drivers-495 Ubuntu upstream *
Nvidia-graphics-drivers-510 Ubuntu esm-infra/bionic *
Nvidia-graphics-drivers-510 Ubuntu esm-infra/focal *
Nvidia-graphics-drivers-510 Ubuntu jammy *
Nvidia-graphics-drivers-510 Ubuntu upstream *
Nvidia-graphics-drivers-515 Ubuntu esm-infra/bionic *
Nvidia-graphics-drivers-515 Ubuntu esm-infra/focal *
Nvidia-graphics-drivers-515 Ubuntu jammy *
Nvidia-graphics-drivers-515 Ubuntu upstream *
Nvidia-graphics-drivers-515-server Ubuntu esm-infra/bionic *
Nvidia-graphics-drivers-515-server Ubuntu esm-infra/focal *
Nvidia-graphics-drivers-515-server Ubuntu jammy *
Nvidia-graphics-drivers-515-server Ubuntu upstream *
Nvidia-graphics-drivers-520 Ubuntu esm-infra/bionic *
Nvidia-graphics-drivers-520 Ubuntu esm-infra/focal *
Nvidia-graphics-drivers-520 Ubuntu jammy *
Nvidia-graphics-drivers-520 Ubuntu upstream *
Nvidia-graphics-drivers-525 Ubuntu upstream *
Nvidia-graphics-drivers-525-server Ubuntu upstream *
Nvidia-graphics-drivers-530 Ubuntu esm-infra/bionic *
Nvidia-graphics-drivers-530 Ubuntu esm-infra/focal *
Nvidia-graphics-drivers-530 Ubuntu jammy *
Nvidia-graphics-drivers-530 Ubuntu upstream *
Nvidia-graphics-drivers-545 Ubuntu jammy *
Nvidia-graphics-drivers-545 Ubuntu upstream *
Nvidia-graphics-drivers-560 Ubuntu devel *
Nvidia-graphics-drivers-560 Ubuntu plucky *
Nvidia-graphics-drivers-560 Ubuntu questing *
Nvidia-graphics-drivers-560 Ubuntu upstream *
Nvidia-graphics-drivers-565-server Ubuntu esm-infra/focal *
Nvidia-graphics-drivers-565-server Ubuntu jammy *
Nvidia-graphics-drivers-565-server Ubuntu noble *
Nvidia-graphics-drivers-565-server Ubuntu upstream *
Nvidia-graphics-drivers-575 Ubuntu upstream *

Potential Mitigations

  • Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
  • When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, “boat” may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as “red” or “blue.”
  • Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code’s environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
  • To reduce the likelihood of introducing an out-of-bounds read, ensure that you validate and ensure correct calculations for any length argument, buffer size calculation, or offset. Be especially careful of relying on a sentinel (i.e. special character such as NUL) in untrusted inputs.

References