CVE-2022-50000
BaseFortify
Publication date: 2025-06-18
Last updated on: 2025-11-14
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.0 |
| linux | linux_kernel | 6.0 |
| 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's netfilter flowtable occurs during the cleanup process of flow tables. Normally, a sequence of steps ensures that all flow table entries are properly removed and hardware work is completed before freeing the flow table. However, if a flow table entry has pending hardware stats or add work, the deletion work is skipped and may execute after the flow table is freed, causing a use-after-free bug. This can lead to kernel crashes or memory corruption. The fix involves flushing pending work and carefully sequencing the teardown and garbage collection to avoid this issue.
How can this vulnerability impact me? :
This vulnerability can cause use-after-free errors in the Linux kernel, potentially leading to system instability, crashes, or security issues such as privilege escalation or denial of service if exploited. It affects the reliability and security of systems using the affected kernel versions.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability may be detected by monitoring kernel logs for use-after-free errors related to netfilter flowtable operations, such as KASAN (Kernel Address Sanitizer) reports showing stack traces involving nf_flow_table and flow_offload_work_handler. Commands like 'dmesg | grep -i kasan' or 'journalctl -k | grep nf_flow_table' can help identify such errors.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version that includes the patch fixing the flowtable cleanup issue. The patch ensures proper flushing of pending work and garbage collection to prevent use-after-free conditions. Until an update is applied, consider disabling or limiting netfilter flowtable offload features if possible to reduce exposure.