CVE-2024-56755
- Source
- https://nvd.nist.gov/vuln/detail/CVE-2024-56755
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-56755.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2024-56755
- Downstream
- Related
- Published
- 2024-12-29T11:30:19Z
- Modified
- 2025-10-22T08:17:04.040760Z
- Severity
-
- 5.5 (Medium) CVSS_V3 - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H CVSS Calculator
- Summary
- netfs/fscache: Add a memory barrier for FSCACHE_VOLUME_CREATING
- Details
-
In the Linux kernel, the following vulnerability has been resolved:
netfs/fscache: Add a memory barrier for FSCACHEVOLUMECREATING
In fscachecreatevolume(), there is a missing memory barrier between the bit-clearing operation and the wake-up operation. This may cause a situation where, after a wake-up, the bit-clearing operation hasn't been detected yet, leading to an indefinite wait. The triggering process is as follows:
[cookie1] [cookie2] [volumework] fscacheperformlookup fscachecreatevolume fscacheperformlookup fscachecreatevolume fscachecreatevolumework cachefilesacquirevolume clearandwakeupbit testandsetbit testandsetbit goto maybewait goto nowait
In the above process, cookie1 and cookie2 has the same volume. When cookie1 enters the -no_wait- process, it will clear the bit and wake up the waiting process. If a barrier is missing, it may cause cookie2 to remain in the -wait- process indefinitely.
In commit 3288666c7256 ("fscache: Use clearandwakeupbit() in fscachecreatevolumework()"), barriers were added to similar operations in fscachecreatevolumework(), but fscachecreatevolume() was missed.
By combining the clear and wake operations into clearandwakeupbit() to fix this issue.
- References
-
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- https://git.kernel.org/stable/c/22f9400a6f3560629478e0a64247b8fcc811a24d
- https://git.kernel.org/stable/c/539fabba965e119b98066fc6ba5257b5eaf4eda2
- https://git.kernel.org/stable/c/8beb682cc9a0798a280bbb95e3e41617237090b2
- https://git.kernel.org/stable/c/8cc1df3113cb71a0df2c46dd5b102c9e11c8a8c6
- https://git.kernel.org/stable/c/ddab02607eed9e415dc62fde421d4329e5345315
Affected packages
Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected ranges
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introducedbfa22da3ed652aa15acd4246fa13a0de6dbe4a59Fixedddab02607eed9e415dc62fde421d4329e5345315
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introducedbfa22da3ed652aa15acd4246fa13a0de6dbe4a59Fixed539fabba965e119b98066fc6ba5257b5eaf4eda2
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introducedbfa22da3ed652aa15acd4246fa13a0de6dbe4a59Fixed8beb682cc9a0798a280bbb95e3e41617237090b2
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introducedbfa22da3ed652aa15acd4246fa13a0de6dbe4a59Fixed8cc1df3113cb71a0df2c46dd5b102c9e11c8a8c6
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introducedbfa22da3ed652aa15acd4246fa13a0de6dbe4a59Fixed22f9400a6f3560629478e0a64247b8fcc811a24d