SECUFOCUSNOW
Home›CVE index›CVE-2022-50303
Review reviewHigh

CVE-2022-50303

Linux Linux, linux kernel

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...

CVSS
7.8
EPSS
0.15%
4.78% percentile
CISA KEV
Not listed
Published
2025.09.16
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.15%
Technical severityCVSS 7.8

Vulnerability overview

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...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 88f7f88159bcdff96b2a5d244b26c8ba99b5e773 < 89f0d766c9e3fdeafbed6f855d433c2768cde862, >= 88f7f88159bcdff96b2a5d244b26c8ba99b5e773 < a02c07b619899179384fde06f951530438a3512d, >= 88f7f88159bcdff96b2a5d244b26c8ba99b5e773 < 1a799c4c190ea9f0e81028e3eb3037ed0ab17ff5, >= 5.15, >= 3.19 < 6.0.19, >= 6.1 < 6.1.5
Fixed versions
6.0.19, 6.1.5

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-415