CVE-2024-39508

In the Linux kernel, the following vulnerability has been resolved: io_uring/io-wq: Use set_bit() and test_bit() at worker->flags Utilize set_bit() and test_bit() on worker->flags within io_uring/io-wq to address potential data races. The structure io_worker->flags may be accessed through various data paths, leading to concurrency issues. When KCSAN is enabled, it reveals data races occurring in io_worker_handle_work and io_wq_activate_free_worker functions. BUG: KCSAN: data-race in io_worker_handle_work / io_wq_activate_free_worker write to 0xffff8885c4246404 of 4 bytes by task 49071 on cpu 28: io_worker_handle_work (io_uring/io-wq.c:434 io_uring/io-wq.c:569) io_wq_worker (io_uring/io-wq.c:?) <snip> read to 0xffff8885c4246404 of 4 bytes by task 49024 on cpu 5: io_wq_activate_free_worker (io_uring/io-wq.c:? io_uring/io-wq.c:285) io_wq_enqueue (io_uring/io-wq.c:947) io_queue_iowq (io_uring/io_uring.c:524) io_req_task_submit (io_uring/io_uring.c:1511) io_handle_tw_list (io_uring/io_uring.c:1198) <snip> Line numbers against commit 18daea77cca6 ("Merge tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm"). These races involve writes and reads to the same memory location by different tasks running on different CPUs. To mitigate this, refactor the code to use atomic operations such as set_bit(), test_bit(), and clear_bit() instead of basic "and" and "or" operations. This ensures thread-safe manipulation of worker flags. Also, move `create_index` to avoid holes in the structure.

• CWE-362

• https://git.kernel.org/stable/c/1cbb0affb15470a9621267fe0a8568007553a4bfPatch
• https://git.kernel.org/stable/c/8a565304927fbd28c9f028c492b5c1714002cbabPatch
• https://git.kernel.org/stable/c/ab702c3483db9046bab9f40306f1a28b22dbbdc0Patch
• https://git.kernel.org/stable/c/1cbb0affb15470a9621267fe0a8568007553a4bfPatch
• https://git.kernel.org/stable/c/8a565304927fbd28c9f028c492b5c1714002cbabPatch
• https://git.kernel.org/stable/c/ab702c3483db9046bab9f40306f1a28b22dbbdc0Patch

Published

Jul 12, 2024

Last Modified

Aug 4, 2026

Status

Modified

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2024-39502In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2024-39503In the Linux kernel, the following vulnerability has been re…7
• CVE-2024-39504In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2024-39505In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2024-39506In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2024-39507In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2024-39509In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2024-3951 PTC Codebeamer is vulnerable to a cross site scripting vuln…7.1
• CVE-2024-39510In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2024-39511An Improper Input Validation vulnerability in the 802.1X Aut…6.8
• CVE-2024-39512An Improper Physical Access Control vulnerability in the con…7
• CVE-2024-39513An Improper Input Validation vulnerability in the Packet For…6.8