Log in Start free

Vulnerability · Published Jun 20, 2024 · Assigned by Linux

CVE-2022-48732drm/nouveau: fix off by one in BIOS boundary checking

High 7.8

In plain English

A high-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 15% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS NVD)7.8High
Exploit odds (30 days)0.2%top 85.5% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: drm/nouveau: fix off by one in BIOS boundary checking Bounds checking when parsing init scripts embedded in the BIOS reject access to the last byte. This causes driver initialization to fail on Apple eMac's with GeForce 2 MX GPUs, leaving the system with no working console. This is probably only seen on OpenFirmware machines like PowerPC Macs because the BIOS image provided by OF is only the used parts of the ROM, not a power-of-two blocks read from PCI directly so PCs always have empty bytes at the end that are never accessed.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linux5.16.10-1DEBIAN-CVE-2022-48732
Debian:13linux5.16.10-1DEBIAN-CVE-2022-48732
Debian:14linux5.16.10-1DEBIAN-CVE-2022-48732
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2022-48732
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2022-48732
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2022-48732
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2022-48732
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2022-48732
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2022-48732
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2022-48732
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2022-48732
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2022-48732
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2022-48732
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2022-48732
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2022-48732
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2022-48732
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2022-48732
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2022-48732
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2022-48732
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2022-48732
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2022-48732
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2022-48732
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2022-48732
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2022-48732
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2022-48732
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2022-48732
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2022-48732

Affected products (as reported)

VendorProductVersions
Linux Linux 4d4e9907ff572bb1d1c0f6913ad6e3d6d4525077 – before d4b746e60fd8eaa8016e144223abe91158edcdad4d4e9907ff572bb1d1c0f6913ad6e3d6d4525077 – before 909d3ec1bf9f0ec534bfc081b77c0836fea7b0e24d4e9907ff572bb1d1c0f6913ad6e3d6d4525077 – before b2a21669ee98aafc41c6d42ef15af4dab9e6e8824d4e9907ff572bb1d1c0f6913ad6e3d6d4525077 – before acc887ba88333f5fec49631f12d8cc7ebd95781c4d4e9907ff572bb1d1c0f6913ad6e3d6d4525077 – before f071d9fa857582d7bd77f4906691f73d3edeab734d4e9907ff572bb1d1c0f6913ad6e3d6d4525077 – before d877e814a62b7de9069aeff8bc1d979dfc996e064d4e9907ff572bb1d1c0f6913ad6e3d6d4525077 – before e7c36fa8a1e63b08312162179c78a0c7795ea3694d4e9907ff572bb1d1c0f6913ad6e3d6d4525077 – before 1b777d4d9e383d2744fc9b3a09af6ec1893c8b1a
Linux Linux 4.8

References