CVE-2022-49316
NFSv4: Don't hold the layoutget locks across multiple RPC calls
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: NFSv4: Don't hold the layoutget locks across multiple RPC calls When doing layoutget as part of the open() compound, we have to be careful to release the layout locks before we can call any further RPC calls, such as setattr(). The reason is that those calls could trigger a recall, which could deadlock.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
4.18
References 7
git.kernel.org
- stable/c/6b3fc1496e7227cd6a39a80bbfb7588ef7c7a010
- stable/c/a2b3be930e79cc5d9d829f158e31172b2043f0cd
- stable/c/0ee5b9644f06b4d3cdcd9544f43f63312e425a4c
- stable/c/d4c2a041ed3ba114502d5ed6ace5b1a48d637a8e
- stable/c/08d7a26d115cc7892668baa9750f64bd8baca29b
- stable/c/ea759ae0a9ae5acee677d722129710ac89cc59c1
- stable/c/6949493884fe88500de4af182588e071cf1544ee