CVE-2022-50265
BaseFortify
Publication date: 2025-09-15
Last updated on: 2025-12-03
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.6 (inc) to 4.9.332 (exc) |
| linux | linux_kernel | From 4.10 (inc) to 4.14.298 (exc) |
| linux | linux_kernel | From 4.15 (inc) to 4.19.264 (exc) |
| linux | linux_kernel | From 4.20 (inc) to 5.4.223 (exc) |
| linux | linux_kernel | From 5.5 (inc) to 5.10.153 (exc) |
| linux | linux_kernel | From 5.11 (inc) to 5.15.77 (exc) |
| linux | linux_kernel | From 5.16 (inc) to 6.0.7 (exc) |
| linux | linux_kernel | 6.1 |
| linux | linux_kernel | 6.1 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-NVD-CWE-noinfo |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability impact me? :
This vulnerability can lead to instability or crashes in the Linux kernel due to data races in the kcm subsystem. Such kernel issues can cause system crashes, denial of service, or unpredictable behavior in applications relying on the kernel networking stack.
Can you explain this vulnerability to me?
This vulnerability is a data race in the Linux kernel's kcm (Kernel Connection Multiplexor) subsystem. Specifically, the kcm->rx_psock variable can be read without proper locking in the kcm_rfree() function, leading to concurrent read and write operations on the same memory location without synchronization. This can cause unpredictable behavior or kernel crashes.