CVE-2022-50393
BaseFortify
Publication date: 2025-09-18
Last updated on: 2025-12-12
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| 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 ID | Description |
|---|---|
| CWE-NVD-CWE-noinfo |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
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.
How can this vulnerability impact me? :
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.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
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.
What immediate steps should I take to mitigate this vulnerability?
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.