CVE-2022-50256
BaseFortify
Publication date: 2025-09-15
Last updated on: 2025-11-25
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
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 in the Linux kernel involves the drm/meson driver where drm bridges added during initialization were not properly removed when the module was unloaded. This caused dangling references to freed memory to remain in a global list. When the driver modules were loaded again, the system would access this freed memory, leading to a use-after-free error detected by KASAN (Kernel Address Sanitizer).
How can this vulnerability impact me? :
The vulnerability can cause the Linux kernel to access freed memory, which may lead to system instability, crashes, or potential security risks such as memory corruption. This can affect the reliability and security of systems using the affected drm/meson drivers.
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) use-after-free errors related to drm bridges, such as messages containing 'BUG: KASAN: use-after-free' and stack traces involving drm_bridge_add and meson_drm modules. You can check the kernel log using the command: dmesg | grep -i kasan
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version where the drm/meson bridge removal at aggregate driver unbind time has been fixed. This prevents dangling references to freed memory. Until then, avoid unloading and reloading the affected drm modules (meson_encoder_hdmi and meson_encoder_cvbs) to reduce the risk of triggering the use-after-free condition.