dbcve.org
Linux KernelOperating system · Linux

CVE-2024-56709

MEDIUM · 5.5 CVSS v3.1 Published 2024-12-29
Fix available
A fix is available. Upgrade to 6.1.122 / 6.6.68 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In the Linux kernel, the following vulnerability has been resolved: io_uring: check if iowq is killed before queuing task work can be executed after the task has gone through io_uring termination, whether it's the final task_work run or the fallback path. In this case, task work will find ->io_wq being already killed and null'ed, which is a problem if it then tries to forward the request to io_queue_iowq(). Make io_queue_iowq() fail requests in this case. Note that it also checks PF_KTHREAD, because the user can first close a DEFER_TASKRUN ring and shortly after kill the task, in which case ->iowq check would race.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 5.14.1, < 6.1.122>= 6.2, < 6.6.68>= 6.7, < 6.12.7= 5.14= 6.13

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.1.122 / 6.6.68 / 6.12.7 or later
Fixed in 6.1.1226.6.686.12.7
Vendor patch git.kernel.org →
Recommended fix High confidence

6.1.122+, 6.6.68+, or 6.12.7+ (or move to a currently supported stable LTS branch such as 6.1.y or 6.6.y)

  1. Check current kernel version using 'uname -r' or 'cat /proc/version'
  2. Identify which kernel branch you're running (e.g., 6.1.x, 6.2.x, 6.6.x, 6.7.x, 6.12.x)
  3. For systems running 6.1.x: upgrade to kernel >= 6.1.122
  4. For systems running 6.2.x through 6.5.x: upgrade to kernel >= 6.6.68
  5. For systems running 6.7.x through 6.11.x: upgrade to kernel >= 6.12.7
  6. For systems running 5.14.x: upgrade to a supported stable branch (6.1 LTS or later recommended)
  7. Apply the upgrade via package manager (e.g., apt-get update && apt-get upgrade, yum update, dnf update)
  8. Reboot the system to load the fixed kernel
Caveat Kernel upgrades generally do not introduce breaking userspace changes but require system reboot; ensure compatibility with existing system configuration before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-56709 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-56709 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data