[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025091558-CVE-2022-50302-89ee@gregkh>
Date: Mon, 15 Sep 2025 16:46:04 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-50302: lockd: set other missing fields when unlocking files
From: Greg Kroah-Hartman <gregkh@...nel.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.
The Linux kernel CVE team has assigned CVE-2022-50302 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.15.56 with commit 9c3eef773cf4a8a18f959234bbb4c0a55c31ab71 and fixed in 5.15.86 with commit 95d42a8d3d4ae84a0bd3ee23e1fee240cdf0a9f0
Issue introduced in 5.19 with commit aec158242b87a43d83322e99bc71ab4428e5ab79 and fixed in 6.0.16 with commit 688575aef211b0986fc51010116f5888a99d76a2
Issue introduced in 5.19 with commit aec158242b87a43d83322e99bc71ab4428e5ab79 and fixed in 6.1.2 with commit d7aa9f7778316beb690f6e2763b6d672ad8b256f
Issue introduced in 5.19 with commit aec158242b87a43d83322e99bc71ab4428e5ab79 and fixed in 6.2 with commit 18ebd35b61b4693a0ddc270b6d4f18def232e770
Issue introduced in 5.18.13 with commit 58c3f48a540b821b3253e2dc31c8fa237293ffc9
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2022-50302
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
fs/lockd/svcsubs.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/31c93ee5f1e4dc278b562e20f3c3274ac34997f3
https://git.kernel.org/stable/c/95d42a8d3d4ae84a0bd3ee23e1fee240cdf0a9f0
https://git.kernel.org/stable/c/688575aef211b0986fc51010116f5888a99d76a2
https://git.kernel.org/stable/c/d7aa9f7778316beb690f6e2763b6d672ad8b256f
https://git.kernel.org/stable/c/18ebd35b61b4693a0ddc270b6d4f18def232e770
Powered by blists - more mailing lists