CVE-2022-49316
published 2025-02-26CVE-2022-49316: 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…
PriorityP417medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.21%
11.5th percentile
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.
Affected
19 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.18.5-1 (bookworm) | linux 5.18.5-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 56f487f8c8fc5d6e582b79a86fc132d050129e15 < 6b3fc1496e7227cd6a39a80bbfb7588ef7c7a010 | 6b3fc1496e7227cd6a39a80bbfb7588ef7c7a010 |
| linux | linux | >= 56f487f8c8fc5d6e582b79a86fc132d050129e15 < a2b3be930e79cc5d9d829f158e31172b2043f0cd | a2b3be930e79cc5d9d829f158e31172b2043f0cd |
| linux | linux | >= 56f487f8c8fc5d6e582b79a86fc132d050129e15 < 0ee5b9644f06b4d3cdcd9544f43f63312e425a4c | 0ee5b9644f06b4d3cdcd9544f43f63312e425a4c |
| linux | linux | >= 56f487f8c8fc5d6e582b79a86fc132d050129e15 < d4c2a041ed3ba114502d5ed6ace5b1a48d637a8e | d4c2a041ed3ba114502d5ed6ace5b1a48d637a8e |
| linux | linux | >= 56f487f8c8fc5d6e582b79a86fc132d050129e15 < 08d7a26d115cc7892668baa9750f64bd8baca29b | 08d7a26d115cc7892668baa9750f64bd8baca29b |
| linux | linux | >= 56f487f8c8fc5d6e582b79a86fc132d050129e15 < ea759ae0a9ae5acee677d722129710ac89cc59c1 | ea759ae0a9ae5acee677d722129710ac89cc59c1 |
| linux | linux | >= 56f487f8c8fc5d6e582b79a86fc132d050129e15 < 6949493884fe88500de4af182588e071cf1544ee | 6949493884fe88500de4af182588e071cf1544ee |
| linux | linux_kernel | < 4.19.247 | 4.19.247 |
| linux | linux_kernel | >= 0 < 5.10.127-1 | 5.10.127-1 |
| linux | linux_kernel | >= 0 < 5.18.5-1 | 5.18.5-1 |
| linux | linux_kernel | >= 0 < 5.18.5-1 | 5.18.5-1 |
| linux | linux_kernel | >= 0 < 5.18.5-1 | 5.18.5-1 |
| linux | linux_kernel | >= 4.20 < 5.4.198 | 5.4.198 |
| linux | linux_kernel | >= 5.11 < 5.15.47 | 5.15.47 |
| linux | linux_kernel | >= 5.16 < 5.17.15 | 5.17.15 |
| linux | linux_kernel | >= 5.18 < 5.18.4 | 5.18.4 |
| linux | linux_kernel | >= 5.5 < 5.10.122 | 5.10.122 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-grrp-5mc5-ccmg: In the Linux kernel, the following vulnerability has been resolved:
NFSv4: Don't hold the layoutget locks across multiple RPC calls
When doing layou
ghsa_unreviewed·2025-03-14
CVE-2022-49316 [MEDIUM] CWE-667 GHSA-grrp-5mc5-ccmg: In the Linux kernel, the following vulnerability has been resolved:
NFSv4: Don't hold the layoutget locks across multiple RPC calls
When doing layou
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.
OSV
CVE-2022-49316: In the Linux kernel, the following vulnerability has been resolved: NFSv4: Don't hold the layoutget locks across multiple RPC calls When doing layoutg
osv·2025-02-26·CVSS 5.5
CVE-2022-49316 [MEDIUM] CVE-2022-49316: In the Linux kernel, the following vulnerability has been resolved: NFSv4: Don't hold the layoutget locks across multiple RPC calls When doing layoutg
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.
Red Hat
kernel: NFSv4: Don't hold the layoutget locks across multiple RPC calls
vendor_redhat·2025-02-26·CVSS 5.5
CVE-2022-49316 [MEDIUM] CWE-667 kernel: NFSv4: Don't hold the layoutget locks across multiple RPC calls
kernel: NFSv4: Don't hold the layoutget locks across multiple RPC calls
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.
Package: kernel (Red Hat Enterprise Linux 10) - Not affected
Package: kernel (Red Hat Enterprise Linux 6) - Out of support scope
Package: kernel (Red Hat Enterprise Linux 7) - Out of support scope
Package: kernel-rt (Red Hat Enterprise Linux 7) - Out of support scope
Package: kernel-rt (Red Hat Enterprise Linux 8) - Out of support scope
Package:
Debian
CVE-2022-49316: linux - In the Linux kernel, the following vulnerability has been resolved: NFSv4: Don'...
vendor_debian·2022·CVSS 5.5
CVE-2022-49316 [MEDIUM] CVE-2022-49316: linux - In the Linux kernel, the following vulnerability has been resolved: NFSv4: Don'...
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.
Scope: local
bookworm: resolved (fixed in 5.18.5-1)
bullseye: resolved (fixed in 5.10.127-1)
forky: resolved (fixed in 5.18.5-1)
sid: resolved (fixed in 5.18.5-1)
trixie: resolved (fixed in 5.18.5-1)
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
https://git.kernel.org/stable/c/08d7a26d115cc7892668baa9750f64bd8baca29bhttps://git.kernel.org/stable/c/0ee5b9644f06b4d3cdcd9544f43f63312e425a4chttps://git.kernel.org/stable/c/6949493884fe88500de4af182588e071cf1544eehttps://git.kernel.org/stable/c/6b3fc1496e7227cd6a39a80bbfb7588ef7c7a010https://git.kernel.org/stable/c/a2b3be930e79cc5d9d829f158e31172b2043f0cdhttps://git.kernel.org/stable/c/d4c2a041ed3ba114502d5ed6ace5b1a48d637a8ehttps://git.kernel.org/stable/c/ea759ae0a9ae5acee677d722129710ac89cc59c1
2025-02-26
Published