CVE-2024-35914

In the Linux kernel, the following vulnerability has been resolved:

nfsd: Fix error cleanup path in nfsd_rename()

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 has been acquired. Fix the cleanup path to properly drop the remount protection.

Weakness

The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

Affected Software

Extended Description

Locking is a type of synchronization behavior that ensures that multiple independently-operating processes or threads do not interfere with each other when accessing the same resource. All processes/threads are expected to follow the same steps for locking. If these steps are not followed precisely - or if no locking is done at all - then another process/thread could modify the shared resource in a way that is not visible or predictable to the original process. This can lead to data or memory corruption, denial of service, etc.

Potential Mitigations

Related Attack Patterns

• https://cwe.mitre.org/data/definitions/25.html
• https://cwe.mitre.org/data/definitions/26.html
• https://cwe.mitre.org/data/definitions/27.html

References

• https://git.kernel.org/stable/c/331e125e02c08ffaecc1074af78a988a278039bd
• https://git.kernel.org/stable/c/9fe6e9e7b58944037714442384075c17cfde1c56
• https://git.kernel.org/stable/c/331e125e02c08ffaecc1074af78a988a278039bd
• https://git.kernel.org/stable/c/9fe6e9e7b58944037714442384075c17cfde1c56