CVE-2022-50884
Null Pointer Dereference in Linux Kernel DRM ioctl Causes Kernel Crash
Publication date: 2025-12-30
Last updated on: 2025-12-30
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability occurs in the Linux kernel's DRM subsystem where the function drm_copy_field() attempts to copy certain driver fields to user-space. If a driver has a bug and does not set some required fields, drm_copy_field() may try to copy a NULL pointer, leading to a kernel access error and potential system crash (kernel oops).
How can this vulnerability impact me? :
This vulnerability can cause the Linux kernel to crash or become unstable due to attempts to access NULL pointers when copying driver fields to user-space. This can lead to denial of service or system instability.
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 kernel oops or error messages related to drm_copy_field() attempting to copy a NULL pointer. Specifically, look for kernel log entries similar to: 'Unable to handle kernel access to user memory outside uaccess routines at virtual address 0000000000000000' or 'Internal error: Oops: 96000004'. You can use the command 'dmesg | grep drm_copy_field' or 'journalctl -k | grep drm_copy_field' to search for such messages in the kernel logs.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating the Linux kernel to a version where this vulnerability is fixed, as it involves a kernel bug in drm_copy_field(). Until an update is applied, avoid running untrusted drivers or code that may trigger DRM_IOCTL_VERSION calls. Monitoring logs for the described errors can also help in early detection of exploitation attempts.