Linux Kernel up to 7.2.12 amdgpu drm/amdgpu amdgpu_gem_userptr_ioctl release of resource

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.34 |
Summary
A vulnerability labeled as problematic has been found in Linux Kernel up to 7.2.12. The affected element is the function amdgpu_gem_userptr_ioctl of the file drm/amdgpu of the component amdgpu. Executing a manipulation can lead to release of resource.
This vulnerability is handled as CVE-2026-99149. It is possible to launch the attack on the local host. There is not any exploit available.
The affected component should be upgraded.
Details
A vulnerability classified as problematic was found in Linux Kernel up to 7.2.12. This vulnerability affects the function amdgpu_gem_userptr_ioctl of the file drm/amdgpu of the component amdgpu. The manipulation with an unknown input leads to a release of resource vulnerability. The CWE definition for the vulnerability is CWE-772. The product does not release a resource after its effective lifetime has ended, i.e., after the resource is no longer needed. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
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)
The advisory is available at git.kernel.org. This vulnerability was named CVE-2026-99149 since 09/25/2026. The exploitation appears to be easy. Local access is required to approach this attack. Technical details are known, but there is no available exploit.
Upgrading to version 7.2.13 eliminates this vulnerability. Applying the patch 64a6d40156ae98caafc922c6d79fe202b0acd836/3c516a5646285442e1cd71dff2584b77eb4fc421 is able to eliminate this problem. The best possible mitigation is suggested to be upgrading to the latest version.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Release of resourceCWE: CWE-772 / CWE-400 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 7.2.13
Patch: 64a6d40156ae98caafc922c6d79fe202b0acd836/3c516a5646285442e1cd71dff2584b77eb4fc421
Timeline
09/25/2026 CVE reserved10/28/2026 Advisory disclosed
10/28/2026 VulDB entry created
10/28/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2026-99149 (🔒)
GCVE (CVE): GCVE-0-2026-99149
GCVE (VulDB): GCVE-100-427906
Entry
Created: 10/28/2026 12:46Changes: 10/28/2026 12:46 (60)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.