CVE-2022-50302
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-09-15

Last updated on: 2025-12-04

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: lockd: set other missing fields when unlocking files vfs_lock_file() expects the struct file_lock to be fully initialised by the caller. Re-exported NFSv3 has been seen to Oops if the fl_file field is NULL.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-09-15
Last Modified
2025-12-04
Generated
2026-06-16
AI Q&A
2025-09-15
EPSS Evaluated
2026-06-14
NVD
CVE-2022-50302
Affected Vendors & Products
Showing 7 associated CPEs
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
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-NVD-CWE-noinfo
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

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.

Impact Analysis

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.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2022-50302. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart