References to Advisories, Solutions, and Tools

By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to nvd@nist.gov.

Known Affected Software Configurations Switch to CPE 2.2

Change History

OR
     *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions up to (excluding) 6.9.11

NIST AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

NIST CWE-667

https://git.kernel.org/stable/c/73254a297c2dd094abec7c9efee32455ae875bdf No Types Assigned

https://git.kernel.org/stable/c/73254a297c2dd094abec7c9efee32455ae875bdf Patch

https://git.kernel.org/stable/c/b571a367502c7ef94c688ef9c7f7d69a2ce3bcca No Types Assigned

https://git.kernel.org/stable/c/b571a367502c7ef94c688ef9c7f7d69a2ce3bcca Patch

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(), an

kernel.org https://git.kernel.org/stable/c/73254a297c2dd094abec7c9efee32455ae875bdf [No types assigned]

kernel.org https://git.kernel.org/stable/c/b571a367502c7ef94c688ef9c7f7d69a2ce3bcca [No types assigned]