Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2022-48732

drm/nouveau: fix off by one in BIOS boundary checking

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 23 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2022-48732, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.24% · top 85% of all CVEs (12 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 4d4e9907ff572bb1d1c0f6913ad6e3d6d4525077 – < d4b746e60fd8eaa8016e144223abe91158edcdad
    • affected 4d4e9907ff572bb1d1c0f6913ad6e3d6d4525077 – < 909d3ec1bf9f0ec534bfc081b77c0836fea7b0e2
    • affected 4d4e9907ff572bb1d1c0f6913ad6e3d6d4525077 – < b2a21669ee98aafc41c6d42ef15af4dab9e6e882
    • affected 4d4e9907ff572bb1d1c0f6913ad6e3d6d4525077 – < acc887ba88333f5fec49631f12d8cc7ebd95781c
    • affected 4d4e9907ff572bb1d1c0f6913ad6e3d6d4525077 – < f071d9fa857582d7bd77f4906691f73d3edeab73
    • affected 4d4e9907ff572bb1d1c0f6913ad6e3d6d4525077 – < d877e814a62b7de9069aeff8bc1d979dfc996e06
    • affected 4d4e9907ff572bb1d1c0f6913ad6e3d6d4525077 – < e7c36fa8a1e63b08312162179c78a0c7795ea369
    • affected 4d4e9907ff572bb1d1c0f6913ad6e3d6d4525077 – < 1b777d4d9e383d2744fc9b3a09af6ec1893c8b1a
  • Linux · Linux

    • affected 4.8
    • unaffected < 4.8
    • unaffected 4.9.300 – ≤ 4.9.*
    • unaffected 4.14.265 – ≤ 4.14.*
    • unaffected 4.19.228 – ≤ 4.19.*
    • unaffected 5.4.178 – ≤ 5.4.*
    • unaffected 5.10.99 – ≤ 5.10.*
    • unaffected 5.15.22 – ≤ 5.15.*
    • unaffected 5.16.8 – ≤ 5.16.*
    • unaffected 5.17 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-48732 badge
[![CVE-2022-48732](https://cveledger.app/badge/CVE-2022-48732.svg)](https://cveledger.app/cve/CVE-2022-48732)

Record last updated .