LiveActive security incident?Get immediate response
CVE Record

CVE-2024-58000: io_uring: prevent reg-wait speculations

In the Linux kernel, the following vulnerability has been resolved: io_uring: prevent reg-wait speculations With *ENTER_EXT_ARG_REG instead of passing a user pointer with arguments for the waiting loop the user can specify an offset into a pre-mapped region of memory, in which case the [offset, offset + sizeof(io_uring_reg_wait)) will be intepreted as the argument. As we address a kernel array using a user given index, it'd be a subject to speculation type of exploits. Use array_index_nospec() to prevent that. Make sure to pass not the full region size but truncate by the maximum offset allowed considering the structure size.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2024-58000 is a Linux kernel io_uring issue where a user-controlled offset could influence a kernel array access under CPU speculation. The public record does not provide a CVSS score, impact detail, or confirmed exploitation. Treat it as kernel-hardening relevant, especially for systems allowing untrusted local users.

Executive priority

Monitor and patch through normal kernel maintenance unless your environment has high-risk multi-user Linux systems. There is no provided evidence of active exploitation or remote compromise, but kernel speculation issues can matter for shared infrastructure and should not be ignored.

Technical view

The issue affects io_uring registered wait handling with ENTER_EXT_ARG_REG. A user-provided offset into a pre-mapped region could be used as an index during argument interpretation, creating a speculation-style exposure. The fix uses array_index_nospec() and limits the maximum offset by the io_uring_reg_wait structure size.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions or downstream builds containing the vulnerable io_uring code. The bundle lists Linux 6.13, 6.13.2, and 6.14 as affected data, but exact downstream package status requires vendor confirmation.

Exploitation context

The source bundle marks CISA KEV status as false and provides no cited evidence of active exploitation. The description frames the bug as speculation-related rather than a conventional remote vulnerability. Exploitability and practical impact are not established in the provided sources.

Researcher notes

The public record is sparse: no CVSS, CWE, exploit status, or detailed impact statement is supplied. Analysis should stay close to the io_uring registered-wait path and the stable commits. Confirm affected and fixed ranges through upstream and distribution-specific advisories before making exposure claims.

Mitigation direction

  • Use vendor kernel packages that include the referenced stable fixes.
  • Track distribution advisories for backports and fixed package versions.
  • Prioritize multi-user systems and hosts running untrusted workloads.
  • Review vendor guidance before applying temporary io_uring restrictions.
  • Do not rely on upstream version numbers alone for patched status.

Validation and detection

  • Inventory Linux hosts running 6.13 or 6.14 kernel lines.
  • Confirm whether kernel packages include the referenced stable commits.
  • Check distribution security advisories for CVE-2024-58000 coverage.
  • Identify systems where untrusted local users can access io_uring.
  • Record exceptions where vendor fixed-version evidence is unavailable.
Prepared
Confidence
medium
Sources
4

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-58000 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
3Timeline events
0ADP providers
3Source links

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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxaa00f67adc2c0d6439f81b5a81ff181377c47a7e, aa00f67adc2c0d6439f81b5a81ff181377c47a7eunaffected
LinuxLinux6.13, 0, 6.13.2, 6.14affected
Weakness

CWE details

No CWE listed

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