https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 05 Oct 2026 01:53:27 +0000 https://vulnerability.circl.lu/vuln/CERTFR-2025-AVI-0252 CERTFR-2025-AVI-0252 https://vulnerability.circl.lu/vuln/CERTFR-2025-AVI-0252 https://vulnerability.circl.lu/vuln/bdu:2026-02213 bdu:2026-02213 https://vulnerability.circl.lu/vuln/bdu:2026-02213 https://vulnerability.circl.lu/vuln/fkie_cve-2022-49316 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>NFSv4: Don&#39;t hold the layoutget locks across multiple RPC calls</p> <p>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.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>NFSv4: Don&#39;t hold the layoutget locks across multiple RPC calls</p> <p>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.</p> https://vulnerability.circl.lu/vuln/fkie_cve-2022-49316 https://vulnerability.circl.lu/vuln/ghsa-grrp-5mc5-ccmg <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>NFSv4: Don&#39;t hold the layoutget locks across multiple RPC calls</p> <p>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.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>NFSv4: Don&#39;t hold the layoutget locks across multiple RPC calls</p> <p>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.</p> https://vulnerability.circl.lu/vuln/ghsa-grrp-5mc5-ccmg https://vulnerability.circl.lu/vuln/rhsa-2023:6583 <p>security update for kernel</p> <p>security update for kernel</p> https://vulnerability.circl.lu/vuln/rhsa-2023:6583 https://vulnerability.circl.lu/vuln/suse-su-2025:1027-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://vulnerability.circl.lu/vuln/suse-su-2025:1027-1 https://vulnerability.circl.lu/vuln/ubuntu-cve-2022-49316 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 145 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: NFSv4: Don&#39;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.</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 145 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: NFSv4: Don&#39;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.</p> https://vulnerability.circl.lu/vuln/ubuntu-cve-2022-49316