CVE-2026-23468: Linux kernel · drm/amdgpu: Limit BO list entry count to prevent resource exhaustion
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in f462624a6e4b5f1ec2664c2c53e408b2f4fb53e9 : update Linux kernel when convenient.
Data as of 5 Nov 2026, 22:04 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-05.
- Patch
- Available – fixed in f462624a6e4b5f1ec2664c2c53e408b2f4fb53e9, e620378aab78d415bd8a15a2f91c145906520288, c833d6c7199c5b5fca9ec95593acd539ec9c171c +3
Exploitation evidence
Disclosed: evidence found.
CVE published 3 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
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)
References
- git.kernel.org/stable/c/c833d6c7199c5b5fca9ec95593acd539ec9c171c (opens in a new tab)
- git.kernel.org/stable/c/e620378aab78d415bd8a15a2f91c145906520288 (opens in a new tab)
- git.kernel.org/stable/c/2723e6851309531ce61aed74e93a0cd268cc862a (opens in a new tab)
- git.kernel.org/stable/c/5ce4a38e6c2488949e373d5066303f9c128db614 (opens in a new tab)
- git.kernel.org/stable/c/f462624a6e4b5f1ec2664c2c53e408b2f4fb53e9 (opens in a new tab)
- git.kernel.org/stable/c/6270b1a5dab94665d7adce3dc78bc9066ed28bdd (opens in a new tab)