VDB

CVE-2024-41050

CVE-2024-41050 PUBLISHED

cachefiles: cyclic allocation of msg_id to avoid reuse

Reported by linux · Published July 29, 2024

In the Linux kernel, the following vulnerability has been resolved: cachefiles: cyclic allocation of msg_id to avoid reuse Reusing the msg_id after a maliciously completed reopen request may cause a read request to remain unprocessed and result in a hung, as shown below: t1 | t2 | t3 ------------------------------------------------- cachefiles_ondemand_select_req cachefiles_ondemand_object_is_close(A) cachefiles_ondemand_set_object_reopening(A) queue_work(fscache_object_wq, &info->work) ondemand_object_worker cachefiles_ondemand_init_object(A) cachefiles_ondemand_send_req(OPEN) // get msg_id 6 wait_for_completion(&req_A->done) cachefiles_ondemand_daemon_read // read msg_id 6 req_A cachefiles_ondemand_get_fd copy_to_user // Malicious completion msg_id 6 copen 6,-1 cachefiles_ondemand_copen complete(&req_A->done) // will not set the object to close // because ondemand_id && fd is valid. // ondemand_object_worker() is done // but the object is still reopening. // new open req_B cachefiles_ondemand_init_object(B) cachefiles_ondemand_send_req(OPEN) // reuse msg_id 6 process_open_req copen 6,A.size // The expected failed copen was executed successfully Expect copen to fail, and when it does, it closes fd, which sets the object to close, and then close triggers reopen again. However, due to msg_id reuse resulting in a successful copen, the anonymous fd is not closed until the daemon exits. Therefore read requests waiting for reopen to complete may trigger hung task. To avoid this issue, allocate the msg_id cyclically to avoid reusing the msg_id for a very short duration of time.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
bpftoolAmazon Linux6.1.102-108.177.amzn2023
kernel-libbpf-staticAmazon Linux6.1.102-108.177.amzn2023
LinuxLinux5.19

Affected products

VendorProductVersions
LinuxLinuxc8383054506c77b814489c09877b5db83fd4abf2, c8383054506c77b814489c09877b5db83fd4abf2, c8383054506c77b814489c09877b5db83fd4abf2
LinuxLinux5.19, 0, 6.1.100
amazon:2023bpftool0
amazon:2023kernel-libbpf-static0
LinuxLinux*, 6.6.41, 6.1.100
amazon:2023python3-perf0
amazon:2023kernel-modules-extra0
amazon:2023kernel-modules-extra-common0
linuxlinux_kernel5.19, 5.19, 5.19
amazon:2023kernel-tools-devel0
amazon:2023kernel-headers0
amazon:2023kernel-libbpf0
amazon:2023kernel0
amazon:2023perf0
amazon:2023kernel-libbpf-devel0
amazon:2023kernel-tools0
amazon:2023kernel-devel0
amazon:2023kernel-livepatch-6.1.102-108.1770

Timeline

  • Jul 29, 2024 CVE Published
  • Jul 30, 2024 EPSS Score (30 in total, the first dated here)
  • Oct 4, 2024 Coalition ESS Score (5 in total, the first dated here)
  • Jan 7, 2026 Security Advisory (355 in total, the first dated here)
  • Mar 30, 2026 Distribution Patch (237 in total, the first dated here)
  • Nov 19, 2026 CVE Updated

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2024-41050
vulnetix vdb fixes CVE-2024-41050

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2024-41050/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›