LiveActive security incident?Get immediate response
CVE Record

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

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.

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A race in Linux io_uring shutdown can allow work to continue after its worker queue is killed, causing unsafe kernel behavior. The CVSS assessment indicates a low-privileged local actor could potentially compromise confidentiality, integrity, and availability. Based on supplied evidence, this is a local host risk rather than a remotely reachable vulnerability.

Executive priority

Treat this as high-priority kernel remediation for multi-user systems and hosts running untrusted workloads. The evidence does not support an internet-wide emergency because the attack vector is local and active exploitation is unconfirmed. Schedule vendor-approved updates and required reboots promptly.

Technical view

Task work may execute after io_uring termination and encounter an io_wq structure that has already been killed and cleared before forwarding a request. The fix makes io_queue_iowq reject requests in this state and checks PF_KTHREAD to address a race involving DEFER_TASKRUN ring closure followed by task termination.

Likely exposure

The bundle identifies Linux kernel releases including 5.14 and specified 6.1, 6.6, 6.12, and 6.13 entries, but does not clearly express all range boundaries. Exploitation requires local low-privileged access. Distribution kernels may contain backported fixes, so version strings alone cannot establish exposure.

Exploitation context

The CVSS vector describes local, low-complexity exploitation requiring low privileges and no user interaction, with potentially high impact. The bundle reports that CVE-2024-56709 is not in KEV, and none of the supplied sources supports a claim of active exploitation.

Researcher notes

The source bundle establishes the affected shutdown race and defensive fix but does not provide a complete, unambiguous version-range mapping or demonstrated exploitation. Researchers should correlate vendor kernel source or changelogs with the four referenced stable commits and avoid inferring vulnerability solely from package version labels.

Mitigation direction

  • Update to a vendor-supported kernel containing the applicable stable fix, following distribution guidance.
  • Reboot into the updated kernel and verify the running image, not only the installed package.
  • If patching is delayed, consult the Linux distribution vendor for supported temporary controls; none are specified here.
  • Prioritize systems allowing untrusted or low-privileged local workloads.

Validation and detection

  • Inventory each system's running kernel release and build.
  • Check vendor changelogs or source history for the referenced stable fix commits.
  • Confirm distribution backport status rather than relying solely on upstream version numbers.
  • After updating and rebooting, verify the running kernel includes the applicable fix.
Prepared
Confidence
medium
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-56709 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
6Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2024-56709Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux773af69121ecc6c53d192661af8d53bb3db028ae, 773af69121ecc6c53d192661af8d53bb3db028ae, 773af69121ecc6c53d192661af8d53bb3db028ae, 773af69121ecc6c53d192661af8d53bb3db028aeunaffected
LinuxLinux5.14, 0, 6.1.122, 6.6.68, 6.12.7, 6.13affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.