VulnerabilityPublished 8 May 2026Updated 6 Nov 2026

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

Affects Linux kernelSource CVE Database V5

Compare

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

Data as of 6 Nov 2026, 16:04 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 ea78f8c68f4f6211c557df49174c54d167821962, 46630d966b99b0fc6cb01fef4110587f3375a0c0, 6fff5204d8aa26b1be50b6427f833bd3e8899c4f

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 ea78f8c68f4f6211c557df49174c54d167821962, 46630d966b99b0fc6cb01fef4110587f3375a0c0 or 6fff5204d8aa26b1be50b6427f833bd3e8899c4f.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ a292fdecd72834b3bec380baa5db1e69e7f70679, < ea78f8c68f4f6211c557df49174c54d167821962	Fixed in ea78f8c68f4f6211c557df49174c54d167821962
LinuxLinux	Affected ≥ a292fdecd72834b3bec380baa5db1e69e7f70679, < 46630d966b99b0fc6cb01fef4110587f3375a0c0	Fixed in 46630d966b99b0fc6cb01fef4110587f3375a0c0
LinuxLinux	Affected ≥ a292fdecd72834b3bec380baa5db1e69e7f70679, < 6fff5204d8aa26b1be50b6427f833bd3e8899c4f	Fixed in 6fff5204d8aa26b1be50b6427f833bd3e8899c4f
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 signal ioctl Huge input values in amdgpu_userq_signal_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. (cherry picked from commit be267e15f99bc97cbe202cd556717797cdcf79a5)

References

Community reviews

Loading reviews…