VulnerabilityPublished 28 Oct 2026

CVE-2026-99149: Linux kernel · drm/amdgpu: fix GEM object leak on ENOMEM in userptr ioctl

Affects Linux kernelSource CVE Database V5

Not known to be exploited : upgrade to 64a6d40156ae98caafc922c6d79fe202b0acd836 or 3c516a5646285442e1cd71dff2584b77eb4fc421 when convenient.

Data as of 28 Oct 2026, 10:58 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Patch: Available – fixed in 64a6d40156ae98caafc922c6d79fe202b0acd836, 3c516a5646285442e1cd71dff2584b77eb4fc421

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, 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 64a6d40156ae98caafc922c6d79fe202b0acd836 or 3c516a5646285442e1cd71dff2584b77eb4fc421.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ e095b55155ef69a8ae0eb114a7fd2a381c012f33, < 64a6d40156ae98caafc922c6d79fe202b0acd836	Fixed in 64a6d40156ae98caafc922c6d79fe202b0acd836
LinuxLinux	Affected ≥ e095b55155ef69a8ae0eb114a7fd2a381c012f33, < 3c516a5646285442e1cd71dff2584b77eb4fc421	Fixed in 3c516a5646285442e1cd71dff2584b77eb4fc421
LinuxLinux	Affected =6.19	Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix GEM object leak on ENOMEM in userptr ioctl When amdgpu_hmm_range_alloc() fails amdgpu_gem_userptr_ioctl() returns -ENOMEM right away and skips the cleanup every other error path goes through. The GEM object, the bo->parent reference on the VM root and the MMU notifier registration are all left behind. Use release_object here, not user_pages_done, range is still NULL at this point. (cherry picked from commit bbe739e407a542073ec1a7872b14843566b4919e)

References

Community reviews

Loading reviews…