CVE-2022-50393
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-09-18

Last updated on: 2025-12-12

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: SDMA update use unlocked iterator SDMA update page table may be called from unlocked context, this generate below warning. Use unlocked iterator to handle this case. WARNING: CPU: 0 PID: 1475 at drivers/dma-buf/dma-resv.c:483 dma_resv_iter_next Call Trace: dma_resv_iter_first+0x43/0xa0 amdgpu_vm_sdma_update+0x69/0x2d0 [amdgpu] amdgpu_vm_ptes_update+0x29c/0x870 [amdgpu] amdgpu_vm_update_range+0x2f6/0x6c0 [amdgpu] svm_range_unmap_from_gpus+0x115/0x300 [amdgpu] svm_range_cpu_invalidate_pagetables+0x510/0x5e0 [amdgpu] __mmu_notifier_invalidate_range_start+0x1d3/0x230 unmap_vmas+0x140/0x150 unmap_region+0xa8/0x110
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-09-18
Last Modified
2025-12-12
Generated
2026-06-16
AI Q&A
2025-09-18
EPSS Evaluated
2026-06-15
NVD
CVE-2022-50393
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
linux linux_kernel From 4.2 (inc) to 5.19.17 (exc)
linux linux_kernel From 6.0 (inc) to 6.0.3 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-NVD-CWE-noinfo
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability involves the Linux kernel's AMD GPU driver (amdgpu) where the SDMA update page table function may be called from an unlocked context, which generates a warning. The issue is related to the use of an iterator without proper locking, potentially causing unsafe access during page table updates.

Impact Analysis

The vulnerability may lead to warnings and potentially unsafe behavior in the AMD GPU driver when updating page tables without proper locking. This could cause instability or unexpected behavior in systems using affected Linux kernel versions with the amdgpu driver.

Detection Guidance

This vulnerability can be detected by monitoring the system logs for the specific warning message: "WARNING: CPU: 0 PID: 1475 at drivers/dma-buf/dma-resv.c:483 dma_resv_iter_next". You can use commands like 'dmesg | grep dma_resv_iter_next' or 'journalctl -k | grep dma_resv_iter_next' to check for this warning in the kernel logs.

Mitigation Strategies

Immediate mitigation involves updating the Linux kernel to a version where this vulnerability is resolved, as the issue is fixed by using an unlocked iterator in the SDMA update page table handling. Until then, monitoring for the warning messages and avoiding workloads that trigger this condition may reduce risk.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2022-50393. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart