CVE-2024-56755: netfs/fscache: Add a memory barrier for FSCACHE_VOLUME_CREATING
First published: Sun Dec 29 2024(Updated: )
In the Linux kernel, the following vulnerability has been resolved: netfs/fscache: Add a memory barrier for FSCACHE_VOLUME_CREATING In fscache_create_volume(), 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] [volume_work] fscache_perform_lookup fscache_create_volume fscache_perform_lookup fscache_create_volume fscache_create_volume_work cachefiles_acquire_volume clear_and_wake_up_bit test_and_set_bit test_and_set_bit goto maybe_wait goto no_wait 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 clear_and_wake_up_bit() in fscache_create_volume_work()"), barriers were added to similar operations in fscache_create_volume_work(), but fscache_create_volume() was missed. By combining the clear and wake operations into clear_and_wake_up_bit() to fix this issue.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel | >=5.17<6.1.120 | |
| Linux Kernel | >=6.2<6.6.64 | |
| Linux Kernel | >=6.7<6.11.11 | |
| Linux Kernel | >=6.12<6.12.2 | |
| debian/linux | 5.10.223-1 5.10.226-1 6.1.123-1 6.1.128-1 6.12.12-1 6.12.15-1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/ddab02607eed9e415dc62fde421d4329e5345315
- 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/22f9400a6f3560629478e0a64247b8fcc811a24d
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-56755
- https://nvd.nist.gov/vuln/detail/CVE-2024-56755
- https://launchpad.net/bugs/cve/CVE-2024-56755
- https://security-tracker.debian.org/tracker/CVE-2024-56755
- https://ubuntu.com/security/CVE-2024-56755
- https://git.kernel.org/linus/22f9400a6f3560629478e0a64247b8fcc811a24d
Frequently Asked Questions
What is the severity of CVE-2024-56755?
CVE-2024-56755 has been rated as a medium severity vulnerability in the Linux kernel.
How do I fix CVE-2024-56755?
To fix CVE-2024-56755, ensure that you update the Linux kernel to the latest patched version that addresses this vulnerability.
Which Linux kernel versions are affected by CVE-2024-56755?
CVE-2024-56755 affects Linux kernel versions between 5.17 to 6.1.120, 6.2 to 6.6.64, 6.7 to 6.11.11, and 6.12 to 6.12.2.
What component is primarily affected by CVE-2024-56755?
CVE-2024-56755 primarily affects the netfs/fscache subsystem of the Linux kernel.
What type of vulnerability is CVE-2024-56755?
CVE-2024-56755 is a synchronization issue due to a missing memory barrier in the fscache_create_volume() function.
- agent/title
- agent/first-publish-date
- agent/type
- agent/author
- agent/remedy
- agent/severity
- agent/weakness
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- collector/usn-cve
- source/Ubuntu
- agent/references
- agent/source
- agent/softwarecombine
- agent/description
- agent/tags
- collector/security-tracker-debian
- source/Debian
- collector/nvd-cve
- agent/event
- vendor/linux
- canonical/linux kernel
- version/linux kernel/5.17
- version/linux kernel/6.2
- version/linux kernel/6.7
- version/linux kernel/6.12
- package-manager/debian