Linux Kernel Drm Amdkfd drm/ kfd_ioctl_get_process_apertures_new num_of_nodes memory corruption

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.5 | $5k-$25k | 3.22- |
Summary
A vulnerability was found in Linux Kernel. It has been classified as very critical. Affected by this vulnerability is the function kfd_ioctl_get_process_apertures_new of the file drm/ of the component Drm Amdkfd. The manipulation of the argument num_of_nodes leads to memory corruption.
This vulnerability is referenced as CVE-2026-53376. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability was found in Linux Kernel (unknown version). It has been rated as very critical. This issue affects the function kfd_ioctl_get_process_apertures_new of the file drm/ of the component Drm Amdkfd. The manipulation of the argument num_of_nodes with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Add upper bound check for num_of_nodes drm/amdkfd: Add upper bound check for num_of_nodes in kfd_ioctl_get_process_apertures_new. (cherry picked from commit 98ff46a5ea090c14d2cdb4f5b993b05d74f3949f)
The advisory is shared at git.kernel.org. The identification of this vulnerability is CVE-2026-53376 since 06/09/2026. The exploitation is known to be easy. The attack may be initiated remotely. Technical details are known, but no exploit is available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 07/19/2026).
Applying the patch 98ff46a5ea090c14d2cdb4f5b993b05d74f3949f is able to eliminate this problem.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-45449). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.9VulDB Meta Temp Score: 9.5
VulDB Base Score: 9.9
VulDB Temp Score: 9.5
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: Memory corruptionCWE: CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
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: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Patch: 98ff46a5ea090c14d2cdb4f5b993b05d74f3949f
Timeline
06/09/2026 CVE reserved07/19/2026 Advisory disclosed
07/19/2026 VulDB entry created
07/19/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2026-53376 (🔒)
GCVE (CVE): GCVE-0-2026-53376
GCVE (VulDB): GCVE-100-380105
EUVD: 🔒
Entry
Created: 07/19/2026 12:47Updated: 07/19/2026 15:26
Changes: 07/19/2026 12:47 (56), 07/19/2026 15:26 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.