CVE-2022-50302
BaseFortify
Publication date: 2025-09-15
Last updated on: 2025-12-04
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.56 (inc) to 5.15.86 (exc) |
| linux | linux_kernel | From 5.18.13 (inc) to 5.19 (exc) |
| linux | linux_kernel | From 5.19.1 (inc) to 6.0.16 (exc) |
| linux | linux_kernel | From 6.1 (inc) to 6.1.2 (exc) |
| linux | linux_kernel | 5.19 |
| linux | linux_kernel | 5.19 |
| linux | linux_kernel | 5.19 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-NVD-CWE-noinfo |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in the Linux kernel involves the lockd component where the function vfs_lock_file() expects the struct file_lock to be fully initialized by the caller. However, in some cases, such as with re-exported NFSv3, the fl_file field was NULL, causing the system to crash (Oops). The issue was resolved by ensuring that missing fields are properly set when unlocking files.
How can this vulnerability impact me? :
This vulnerability can cause the Linux kernel to crash (Oops) when handling certain file locking operations, particularly with re-exported NFSv3. This can lead to system instability or downtime.