CVE-2024-56709: io_uring: check if iowq is killed before queuing

Published Dec 29, 2024
·
Updated

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

iouring: check if iowq is killed before queuing

task work can be executed after the task has gone through iouring termination, whether it's the final taskwork run or the fallback path. In this case, task work will find ->iowq being already killed and null'ed, which is a problem if it then tries to forward the request to ioqueueiowq(). Make ioqueueiowq() fail requests in this case.

Note that it also checks PFKTHREAD, because the user can first close a DEFERTASKRUN ring and shortly after kill the task, in which case ->iowq check would race.

Other sources

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

iouring: check if iowq is killed before queuing

task work can be executed after the task has gone through iouring termination, whether it's the final taskwork run or the fallback path. In this case, task work will find -iowq being already killed and null'ed, which is a problem if it then tries to forward the request to ioqueueiowq(). Make ioqueueiowq() fail requests in this case.

Note that it also checks PFKTHREAD, because the user can first close a DEFERTASKRUN ring and shortly after kill the task, in which case -iowq check would race.

IBM

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

19 affected componentsFixes available
Linux Linux kernel
debian/linux<=6.12.27-1
5.10.223-15.10.234-16.1.129-16.1.135-1
debian/linux-6.1
6.1.129-1~deb11u1
Microsoft cbl2 kernel 5.15.186.1-1
Linux Linux kernel>=5.14.1<6.1.122
Linux Linux kernel>=6.2<6.6.68
Linux Linux kernel>=6.7<6.12.7
Linux Linux kernel=5.14
Linux Linux kernel=5.14-rc4
Linux Linux kernel=5.14-rc5
Linux Linux kernel=5.14-rc6
Linux Linux kernel=5.14-rc7
Linux Linux kernel=6.13-rc1
Linux Linux kernel=6.13-rc2
Linux Linux kernel=6.13-rc3
IBM Verify Identity Access<=11.0 - 11.0.2
IBM Security Verify Access<=10.0 - 10.0.9.1
IBM Verify Identity Access Container<=11.0 - 11.0.2
IBM Security Verify Access Container<=10.0 - 10.0.9.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.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1
  2. Upgrade

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

    Fixed in 6.1.129-1~deb11u1

Event History

Dec 29, 2024
CVE Published
via MITRE·08:42 AM
Data Sourced
via MITRE·08:42 AM
Description
Data Sourced
via Red Hat·09:01 AM
DescriptionSeverityAffected Software
Data Sourced
via NVD·09:15 AM
Description
Data Sourced
via NVD·09:15 AM
RemedySeverityAffected Software
Mar 27, 2025
Data Sourced
via Launchpad·06:47 PM
Description
Apr 28, 2025
Data Sourced
via Ubuntu·06:54 PM
RemedyDescriptionSeverityAffected Software
Oct 17, 2025
Data Sourced
via Microsoft·01:01 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·01:01 AM
DescriptionSeverity
Jul 8, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-56709?

CVE-2024-56709 has a high severity rating as it could allow task work to be executed improperly after termination.

2

How do I fix CVE-2024-56709?

To mitigate CVE-2024-56709, update your Linux kernel to the latest version where this vulnerability has been addressed.

3

What versions of the Linux kernel are affected by CVE-2024-56709?

CVE-2024-56709 affects multiple versions of the Linux kernel that utilize io_uring functionality.

4

Is CVE-2024-56709 being actively exploited?

As of now, there have been no confirmed reports of active exploitation for CVE-2024-56709.

5

What impact does CVE-2024-56709 have on system performance?

CVE-2024-56709 may lead to unexpected behavior in task work execution, potentially affecting system stability and performance.

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