LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50303: drm/amdkfd: Fix double release compute pasid

In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Fix double release compute pasid If kfd_process_device_init_vm returns failure after vm is converted to compute vm and vm->pasid set to compute pasid, KFD will not take pdd->drm_file reference. As a result, drm close file handler maybe called to release the compute pasid before KFD process destroy worker to release the same pasid and set vm->pasid to zero, this generates below WARNING backtrace and NULL pointer access. Add helper amdgpu_amdkfd_gpuvm_set_vm_pasid and call it at the last step of kfd_process_device_init_vm, to ensure vm pasid is the original pasid if acquiring vm failed or is the compute pasid with pdd->drm_file reference taken to avoid double release same pasid. amdgpu: Failed to create process VM object ida_free called for id=32770 which is not allocated. WARNING: CPU: 57 PID: 72542 at ../lib/idr.c:522 ida_free+0x96/0x140 RIP: 0010:ida_free+0x96/0x140 Call Trace: amdgpu_pasid_free_delayed+0xe1/0x2a0 [amdgpu] amdgpu_driver_postclose_kms+0x2d8/0x340 [amdgpu] drm_file_free.part.13+0x216/0x270 [drm] drm_close_helper.isra.14+0x60/0x70 [drm] drm_release+0x6e/0xf0 [drm] __fput+0xcc/0x280 ____fput+0xe/0x20 task_work_run+0x96/0xc0 do_exit+0x3d0/0xc10 BUG: kernel NULL pointer dereference, address: 0000000000000000 RIP: 0010:ida_free+0x76/0x140 Call Trace: amdgpu_pasid_free_delayed+0xe1/0x2a0 [amdgpu] amdgpu_driver_postclose_kms+0x2d8/0x340 [amdgpu] drm_file_free.part.13+0x216/0x270 [drm] drm_close_helper.isra.14+0x60/0x70 [drm] drm_release+0x6e/0xf0 [drm] __fput+0xcc/0x280 ____fput+0xe/0x20 task_work_run+0x96/0xc0 do_exit+0x3d0/0xc10

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2022-50303 is a Linux kernel AMD GPU driver bug that can double-release a compute PASID during an error path. The public record shows kernel warnings and a NULL pointer dereference, meaning affected systems could crash or become unstable when this driver path is hit.

Executive priority

Treat as a stability and availability risk for Linux hosts with AMD GPU compute exposure. Prioritize patch validation where GPU workloads are business-critical or shared by multiple users.

Technical view

In drm/amdkfd, kfd_process_device_init_vm could fail after converting a VM to compute mode and setting vm->pasid, before taking pdd->drm_file. Later DRM close and KFD cleanup could release the same PASID twice. The fix moves compute PASID assignment to the final successful step.

Likely exposure

Exposure is most likely on Linux systems using the AMDGPU/AMDKFD kernel driver and affected kernel versions identified by the CVE data. Distro kernels may differ because vendors backport fixes.

Exploitation context

The source bundle does not show KEV listing, active exploitation, public exploit code, or attacker prerequisites. Evidence is limited to a driver error path causing warnings and a kernel NULL pointer dereference.

Researcher notes

The public data supports a double-free style lifecycle bug around PASID ownership, not a confirmed privilege escalation. Reproduction and impact details are incomplete in the provided sources.

Mitigation direction

  • Apply vendor kernel updates that include the referenced stable fixes.
  • Check Linux distribution advisories for backported AMDGPU/AMDKFD fixes.
  • Prioritize GPU compute hosts and shared Linux systems using AMD GPUs.
  • If updates are unavailable, ask the vendor for supported temporary risk reduction.

Validation and detection

  • Inventory Linux kernels and systems using AMDGPU or AMDKFD.
  • Compare installed kernel builds against vendor advisories and referenced stable commits.
  • Review kernel logs for amdgpu PASID warnings or NULL pointer dereferences.
  • Confirm updated kernels include the PASID assignment ordering fix.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-50303 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux88f7f88159bcdff96b2a5d244b26c8ba99b5e773, 88f7f88159bcdff96b2a5d244b26c8ba99b5e773, 88f7f88159bcdff96b2a5d244b26c8ba99b5e773unaffected
LinuxLinux5.15, 0, 6.0.19, 6.1.5, 6.2affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.