CVE-2024-56755
CVE.org · Published
- Record status
- Published
- Identifier year (not publication year)
- 2024
- Source publication
- Source updated
- Imported by cveboard
- Source snapshot
- cve_2026-10-24_midnight_baseline ·
CNA source text (English)
netfs/fscache: Add a memory barrier for FSCACHE_VOLUME_CREATING
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.
Scoped product and version facts
Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.
Exploitation unknown; this catalogue does not assess exploitation.
Linux
- Vendor
- Linux
- Product
- Linux
- Platforms
- Unknown
- Default status
unaffected
| Version (version) | Status (status) | Version scheme (versionType) | Exclusive end (lessThan) | Inclusive end (lessThanOrEqual) | Status changes (at → status) |
|---|---|---|---|---|---|
| bfa22da3ed652aa15acd4246fa13a0de6dbe4a59 | affected | git | ddab02607eed9e415dc62fde421d4329e5345315 | Unavailable | None listed |
| bfa22da3ed652aa15acd4246fa13a0de6dbe4a59 | affected | git | 539fabba965e119b98066fc6ba5257b5eaf4eda2 | Unavailable | None listed |
| bfa22da3ed652aa15acd4246fa13a0de6dbe4a59 | affected | git | 8beb682cc9a0798a280bbb95e3e41617237090b2 | Unavailable | None listed |
| bfa22da3ed652aa15acd4246fa13a0de6dbe4a59 | affected | git | 8cc1df3113cb71a0df2c46dd5b102c9e11c8a8c6 | Unavailable | None listed |
| bfa22da3ed652aa15acd4246fa13a0de6dbe4a59 | affected | git | 22f9400a6f3560629478e0a64247b8fcc811a24d | Unavailable | None listed |
Linux
- Vendor
- Linux
- Product
- Linux
- Platforms
- Unknown
- Default status
affected
| Version (version) | Status (status) | Version scheme (versionType) | Exclusive end (lessThan) | Inclusive end (lessThanOrEqual) | Status changes (at → status) |
|---|---|---|---|---|---|
| 5.17 | affected | Unavailable | Unavailable | Unavailable | None listed |
| 0 | unaffected | semver | 5.17 | Unavailable | None listed |
| 6.1.120 | unaffected | semver | Unavailable | 6.1.* | None listed |
| 6.6.64 | unaffected | semver | Unavailable | 6.6.* | None listed |
| 6.11.11 | unaffected | semver | Unavailable | 6.11.* | None listed |
| 6.12.2 | unaffected | semver | Unavailable | 6.12.* | None listed |
| 6.13 | unaffected | original_commit_for_fix | Unavailable | * | None listed |