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-2026-23468drm/amdgpu: Limit BO list entry count to prevent resource exhaustion

Description

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Limit BO list entry count to prevent resource exhaustion Userspace can pass an arbitrary number of BO list entries via the bo_number field. Although the previous multiplication overflow check prevents out-of-bounds allocation, a large number of entries could still cause excessive memory allocation (up to potentially gigabytes) and unnecessarily long list processing times. Introduce a hard limit of 128k entries per BO list, which is more than sufficient for any realistic use case (e.g., a single list containing all buffers in a large scene). This prevents memory exhaustion attacks and ensures predictable performance. Return -EINVAL if the requested entry count exceeds the limit (cherry picked from commit 688b87d39e0aa8135105b40dc167d74b5ada5332)

Timeline

  1. ID reserved

    By Linux

  2. · 3 months later

    Published

  3. · 7 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-2026-23468, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.13% · top 98% of all CVEs (18 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: Medium 5.5.

Affected products

  • Linux · Linux

    • affected d38ceaf99ed015f2a0b9af3499791bd3a3daae21 – < c833d6c7199c5b5fca9ec95593acd539ec9c171c
    • affected d38ceaf99ed015f2a0b9af3499791bd3a3daae21 – < e620378aab78d415bd8a15a2f91c145906520288
    • affected d38ceaf99ed015f2a0b9af3499791bd3a3daae21 – < 2723e6851309531ce61aed74e93a0cd268cc862a
    • affected d38ceaf99ed015f2a0b9af3499791bd3a3daae21 – < 5ce4a38e6c2488949e373d5066303f9c128db614
    • affected d38ceaf99ed015f2a0b9af3499791bd3a3daae21 – < f462624a6e4b5f1ec2664c2c53e408b2f4fb53e9
    • affected d38ceaf99ed015f2a0b9af3499791bd3a3daae21 – < 6270b1a5dab94665d7adce3dc78bc9066ed28bdd
  • Linux · Linux

    • affected 4.2
    • unaffected < 4.2
    • unaffected 6.1.175 – ≤ 6.1.*
    • unaffected 6.6.140 – ≤ 6.6.*
    • unaffected 6.12.86 – ≤ 6.12.*
    • unaffected 6.18.20 – ≤ 6.18.*
    • unaffected 6.19.10 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .