CVE-2024-41080

In the Linux kernel, the following vulnerability has been resolved: io_uring: fix possible deadlock in io_register_iowq_max_workers() The io_register_iowq_max_workers() function calls io_put_sq_data(), which acquires the sqd->lock without releasing the uring_lock. Similar to the commit 009ad9f0c6ee ("io_uring: drop ctx->uring_lock before acquiring sqd->lock"), this can lead to a potential deadlock situation. To resolve this issue, the uring_lock is released before calling io_put_sq_data(), and then it is re-acquired after the function call. This change ensures that the locks are acquired in the correct order, preventing the possibility of a deadlock.
Configurations

Configuration 1 (hide)

cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

History

21 Nov 2024, 09:32

Type Values Removed Values Added
References () https://git.kernel.org/stable/c/73254a297c2dd094abec7c9efee32455ae875bdf - Patch () https://git.kernel.org/stable/c/73254a297c2dd094abec7c9efee32455ae875bdf - Patch
References () https://git.kernel.org/stable/c/b571a367502c7ef94c688ef9c7f7d69a2ce3bcca - Patch () https://git.kernel.org/stable/c/b571a367502c7ef94c688ef9c7f7d69a2ce3bcca - Patch

17 Nov 2024, 15:15

Type Values Removed Values Added
References
  • () https://git.kernel.org/stable/c/950ac86cff338ab56e2eaf611f4936ee34893b63 -
  • () https://git.kernel.org/stable/c/97ed7ff58de66c544692b3c2b988f3f594348de0 -
  • () https://git.kernel.org/stable/c/b17397a0a5c56e111f61cb5b77d162664dc00de9 -
  • () https://git.kernel.org/stable/c/fdacd09f2ddf7a00787291f08ee48c0421e5b709 -

22 Aug 2024, 13:39

Type Values Removed Values Added
Summary
  • (es) En el kernel de Linux se ha resuelto la siguiente vulnerabilidad: io_uring: soluciona posible punto muerto en io_register_iowq_max_workers() La función io_register_iowq_max_workers() llama a io_put_sq_data(), que adquiere el sqd->lock sin liberar uring_lock. De manera similar a la confirmación 009ad9f0c6ee ("io_uring: drop ctx->uring_lock before adquiring sqd->lock"), esto puede conducir a una posible situación de punto muerto. Para resolver este problema, uring_lock se libera antes de llamar a io_put_sq_data() y luego se vuelve a adquirir después de la llamada a la función. Este cambio garantiza que los bloqueos se adquieran en el orden correcto, evitando la posibilidad de un punto muerto.
First Time Linux linux Kernel
Linux
CPE cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
CVSS v2 : unknown
v3 : unknown
v2 : unknown
v3 : 5.5
CWE CWE-667
References () https://git.kernel.org/stable/c/73254a297c2dd094abec7c9efee32455ae875bdf - () https://git.kernel.org/stable/c/73254a297c2dd094abec7c9efee32455ae875bdf - Patch
References () https://git.kernel.org/stable/c/b571a367502c7ef94c688ef9c7f7d69a2ce3bcca - () https://git.kernel.org/stable/c/b571a367502c7ef94c688ef9c7f7d69a2ce3bcca - Patch

29 Jul 2024, 15:15

Type Values Removed Values Added
New CVE

Information

Published : 2024-07-29 15:15

Updated : 2024-11-21 09:32


NVD link : CVE-2024-41080

Mitre link : CVE-2024-41080

CVE.ORG link : CVE-2024-41080


JSON object : View

Products Affected

linux

  • linux_kernel
CWE
CWE-667

Improper Locking