VulnerabilityPublished 8 May 2026Updated 6 Nov 2026

CVE-2026-43398: Linux kernel · drm/amdgpu: add upper bound check on user inputs in wait ioctl

Affects Linux kernelSource CVE Database V5

Compare

Not known to be exploited · fixed in b1d10508da559da2e0ca9cca6505094a7df948e1 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 15:49 UTC

Severity

Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

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-06.

Patch

Available – fixed in b1d10508da559da2e0ca9cca6505094a7df948e1, 64ac7c09fc44985ec9bb6a9db740899fa40ca613, 3cd93bc695b3456f26f5ed52753d9071da26202a

Exploitation evidence

Disclosed: evidence found.
CVE published 8 May 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 6 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Linux kernel to b1d10508da559da2e0ca9cca6505094a7df948e1, 64ac7c09fc44985ec9bb6a9db740899fa40ca613 or 3cd93bc695b3456f26f5ed52753d9071da26202a.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ a292fdecd72834b3bec380baa5db1e69e7f70679, < b1d10508da559da2e0ca9cca6505094a7df948e1	Fixed in b1d10508da559da2e0ca9cca6505094a7df948e1
LinuxLinux	Affected ≥ a292fdecd72834b3bec380baa5db1e69e7f70679, < 64ac7c09fc44985ec9bb6a9db740899fa40ca613	Fixed in 64ac7c09fc44985ec9bb6a9db740899fa40ca613
LinuxLinux	Affected ≥ a292fdecd72834b3bec380baa5db1e69e7f70679, < 3cd93bc695b3456f26f5ed52753d9071da26202a	Fixed in 3cd93bc695b3456f26f5ed52753d9071da26202a
LinuxLinux	Affected =6.16	Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: add upper bound check on user inputs in wait ioctl Huge input values in amdgpu_userq_wait_ioctl can lead to a OOM and could be exploited. So check these input value against AMDGPU_USERQ_MAX_HANDLES which is big enough value for genuine use cases and could potentially avoid OOM. v2: squash in Srini's fix (cherry picked from commit fcec012c664247531aed3e662f4280ff804d1476)

References

Community reviews

Loading reviews…