CVE-2022-50378
BaseFortify
Publication date: 2025-09-18
Last updated on: 2025-12-11
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.10 (inc) to 5.15.75 (exc) |
| linux | linux_kernel | From 5.16 (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-416 | The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a use-after-free bug in the Linux kernel's drm/meson driver. It occurs due to an incorrect sequence in the driver deinitialization process, which leads to accessing memory that has already been freed when the driver is unloaded. This triggers a Kernel Address Sanitizer (KASAN) warning indicating unsafe memory access.
How can this vulnerability impact me? :
The use-after-free vulnerability can cause system instability or crashes when the affected driver is unloaded. It may also potentially be exploited to execute arbitrary code or escalate privileges within the kernel, depending on the context and attacker capabilities.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by observing kernel logs for KASAN (Kernel Address Sanitizer) warnings related to use-after-free errors when unloading the drm/meson driver. Specifically, look for messages similar to: 'BUG: KASAN: use-after-free in __list_del_entry_valid' during the rmmod (remove module) operation. You can check kernel logs using the command: dmesg | grep -i kasan or journalctl -k | grep -i kasan. Additionally, attempting to unload the affected driver module (e.g., using sudo rmmod meson_drm) may trigger the warning if the system is vulnerable.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version where the drm/meson driver deinitialization sequence has been reordered to fix the use-after-free bug. Until an update is applied, avoid unloading the affected driver module to prevent triggering the use-after-free condition. Monitoring kernel logs for KASAN warnings can help identify if the issue occurs.