CVE-2024-47746: fuse: use exclusive lock when FUSE_I_CACHE_IO_MODE is set
In the Linux kernel, the following vulnerability has been resolved:
fuse: use exclusive lock when FUSEICACHEIOMODE is set
This may be a typo. The comment has said shared locks are not allowed when this bit is set. If using shared lock, the wait in fusefilecachedioopen may be forever.
Other sources
This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.
— Launchpad
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-47746?
CVE-2024-47746 has been classified as a medium severity vulnerability in the Linux kernel.
How do I fix CVE-2024-47746?
To fix CVE-2024-47746, update your Linux kernel to a version that includes the relevant patches, such as those released after 6.10.13 or 6.11.2.
Which versions of the Linux kernel are affected by CVE-2024-47746?
CVE-2024-47746 affects the Linux kernel versions from 6.9 up to but not including 6.10.13 and also versions from 6.11 up to but not including 6.11.2.
What type of lock is indicated by CVE-2024-47746?
CVE-2024-47746 discusses the use of exclusive locks when FUSE_I_CACHE_IO_MODE is set in the Linux kernel.
Is CVE-2024-47746 capable of leading to a denial of service?
While CVE-2024-47746 does not explicitly state a denial of service risk, improper lock usage can lead to unpredictable behavior.