CVE-2022-50219
BaseFortify
Publication date: 2025-06-18
Last updated on: 2025-11-19
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) |
| 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 is a Use After Free (UAF) bug in the Linux kernel's BPF subsystem, specifically in the compute_effective_progs function. It occurs when detaching BPF links causes a pointer to freed memory to be dereferenced, leading to a KASAN (Kernel Address Sanitizer) UAF error. The issue arises because after a failed memory allocation during link detach, the pointer to the BPF cgroup link is restored but the memory is freed shortly after, causing subsequent calls to access invalid memory.
How can this vulnerability impact me? :
This vulnerability can lead to kernel memory corruption or crashes due to the use of freed memory. Exploiting this bug could potentially allow an attacker to cause denial of service or escalate privileges by manipulating kernel memory through BPF link detach operations.