CVE-2024-41080: io_uring: fix possible deadlock in io_register_iowq_max_workers()

Published Jul 29, 2024
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

iouring: fix possible deadlock in ioregisteriowqmaxworkers()

The ioregisteriowqmaxworkers() function calls ioputsqdata(), which acquires the sqd->lock without releasing the uringlock. Similar to the commit 009ad9f0c6ee ("iouring: drop ctx->uringlock before acquiring sqd->lock"), this can lead to a potential deadlock situation.

To resolve this issue, the uringlock is released before calling ioputsqdata(), 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.

Other sources

This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.

— Launchpad

Affected Software

10 affected componentsFixes available
Linux Linux kernel<6.9.11
Microsoft azl3 kernel 6.6.92.2-1
Microsoft cbl2 kernel 5.15.182.1-1
Microsoft azl3 kernel 6.6.64.2-9
Microsoft cbl2 kernel 5.15.182.1-1
Microsoft cbl2 kernel 5.15.176.3-1
debian/linux<6.1.119-1
6.1.119-1
debian/linux<6.9.11-1
6.9.11-1
debian/linux<6.9.11-1
6.9.11-1
debian/linux
6.1.176-16.1.190-16.12.107-16.12.115-27.2.12-17.2.15-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.25-1Fixed in 6.12.27-1
  2. Upgrade

    Upgrade debian/linux-6.1 to a version that resolves this vulnerability.

    Fixed in 6.1.129-1~deb11u1

Event History

Jul 29, 2024
CVE Published
via MITRE·03:04 PM
Data Sourced
via MITRE·03:04 PM
Description
Data Sourced
via NVD·03:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Data Sourced
via OSV·03:15 PM
DescriptionSeverityAffected Software
Sep 4, 2025
Data Sourced
via Microsoft·03:09 AM
DescriptionSeverityWeaknessAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of CVE-2024-41080?

The severity of CVE-2024-41080 is categorized as a moderate impact due to the potential for a deadlock in the Linux kernel.

2

How do I fix CVE-2024-41080?

To fix CVE-2024-41080, it is recommended to update to the latest patched versions of the Linux kernel provided by your distribution.

3

Which versions of the Linux kernel are affected by CVE-2024-41080?

CVE-2024-41080 affects Linux kernel versions prior to 5.10.226 and certain patched versions within the 6.1 series.

4

Is CVE-2024-41080 a remote exploit vulnerability?

CVE-2024-41080 is not considered a remote exploit vulnerability, as it primarily involves local conditions leading to a deadlock.

5

What is io_register_iowq_max_workers() in relation to CVE-2024-41080?

The function io_register_iowq_max_workers() is involved in the deadlock issue identified in CVE-2024-41080 within the Linux kernel's io_uring subsystem.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203