LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50302: lockd: set other missing fields when unlocking files

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can crash affected systems in a specific NFS file-locking path. The cited description says re-exported NFSv3 has caused an Oops when a lock structure was incomplete. Business impact is mainly service stability for Linux servers that provide or re-export NFS services.

Executive priority

Treat as targeted operational risk for Linux NFS infrastructure, not a broad emergency from the supplied evidence. Prioritize patch validation on NFS servers, especially re-exported NFSv3 environments, because kernel crashes can disrupt shared storage services.

Technical view

The lockd unlock path passed a struct file_lock to vfs_lock_file() without all expected fields set. vfs_lock_file() expects full caller initialization, and a NULL fl_file field was observed causing an Oops during re-exported NFSv3 handling.

Likely exposure

Most relevant exposure is Linux systems on affected kernel versions that run NFS lockd and re-export NFSv3. Systems not using NFS services, NFSv3, or re-export behavior appear less exposed based on the supplied evidence.

Exploitation context

The bundle does not cite active exploitation, public exploit availability, KEV listing, CVSS, or CWE data. The known failure mode is a kernel Oops observed in re-exported NFSv3, suggesting stability or denial-of-service concern rather than confirmed compromise.

Researcher notes

Evidence is sparse: no CVSS, CWE, CPEs, or exploit detail are supplied. Analysis should focus on the lockd unlock path, file_lock initialization, fl_file handling, and whether downstream kernel packages include the stable fixes.

Mitigation direction

  • Apply vendor kernel updates containing the referenced stable fixes.
  • Prioritize NFS servers and systems re-exporting NFSv3.
  • If patching is delayed, review vendor guidance for NFS or lockd workarounds.
  • Reduce re-exported NFSv3 exposure where operationally feasible.
  • Monitor kernel logs for related Oops events.

Validation and detection

  • Inventory Linux kernel versions across NFS-serving systems.
  • Identify hosts using lockd, NFSv3, or NFS re-export behavior.
  • Confirm whether vendor kernels include the referenced stable commits.
  • Review kernel logs for lockd or vfs_lock_file Oops events.
  • Track vendor advisories because severity metadata is incomplete.
Prepared
Confidence
medium
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-50302 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
6Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux486c1acf14233b1ff7b37e6f026a737a2f7f53f1, 9c3eef773cf4a8a18f959234bbb4c0a55c31ab71, aec158242b87a43d83322e99bc71ab4428e5ab79, aec158242b87a43d83322e99bc71ab4428e5ab79, aec158242b87a43d83322e99bc71ab4428e5ab79, 58c3f48a540b821b3253e2dc31c8fa237293ffc9unaffected
LinuxLinux5.19, 0, 5.15.86, 6.0.16, 6.1.2, 6.2affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.