CVE-2024-47746Published Oct 21, 2024 · Oct 21Updated Oct 28
fuse: use exclusive lock when FUSE_I_CACHE_IO_MODE is set
Linux
Medium5.5Fix available
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.10.136.11.26.12In the Linux kernel, the following vulnerability has been resolved:
fuse: use exclusive lock when FUSE_I_CACHE_IO_MODE 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 `fuse_file_cached_io_open` may be forever.
From the CVE record · Linux
The Linux kernel’s FUSE code may use a shared lock when FUSE_I_CACHE_IO_MODE is set, even though shared locks are not allowed in that state. This can cause an indefinite wait in fuse_file_cached_io_open. The input does not describe an attack path, authentication requirements, or user interaction.
Engineers running Linux kernels with FUSE support should check their versions; affected versions are not specified.