EUVD-2023-60346

In the Linux kernel, the following vulnerability has been resolved: fs: Protect reconfiguration of sb read-write from racing writes The reconfigure / remount code takes a lot of effort to protect filesystem's reconfiguration code from racing writes on remounting read-only. However during remounti...

SUSE CVE-2024-35914

In the Linux kernel, the following vulnerability has been resolved: nfsd: Fix error cleanup path in nfsdrename Commit a8b0026847b8 "rename: avoid a deadlock in the case of parents having no common ancestor" added an error bail out path. However this path does not drop the remount protection that...

CVE-2024-35914

In the Linux kernel, the following vulnerability has been resolved: nfsd: Fix error cleanup path in nfsdrename Commit a8b0026847b8 "rename: avoid a deadlock in the case of parents having no common ancestor" added an error bail out path. However this path does not drop the remount protection that...

DEBIAN-CVE-2024-35914

In the Linux kernel, the following vulnerability has been resolved: nfsd: Fix error cleanup path in nfsdrename Commit a8b0026847b8 "rename: avoid a deadlock in the case of parents having no common ancestor" added an error bail out path. However this path does not drop the remount protection that...

CVE-2024-35914

In the Linux kernel, the following vulnerability has been resolved: nfsd: Fix error cleanup path in nfsdrename Commit a8b0026847b8 "rename: avoid a deadlock in the case of parents having no common ancestor" added an error bail out path. However this path does not drop the remount protection that...

UBUNTU-CVE-2024-35914

In the Linux kernel, the following vulnerability has been resolved: nfsd: Fix error cleanup path in nfsdrename Commit a8b0026847b8 "rename: avoid a deadlock in the case of parents having no common ancestor" added an error bail out path. However this path does not drop the remount protection that...

CVE-2024-35914

The CVE-2024-35914 vulnerability affects the Linux kernel’s NFS server (nfsd) rename error cleanup path. The issue arose when a remount protection acquired during a cleanup path was not dropped, potentially enabling a deadlock or inconsistency. The fix, tracked in the commit a8b0026847b8, updates...