LiveActive security incident?Get immediate response
CVE Record

CVE-2023-54030: io_uring/net: don't overflow multishot recv

In the Linux kernel, the following vulnerability has been resolved: io_uring/net: don't overflow multishot recv Don't allow overflowing multishot recv CQEs, it might get out of hand, hurt performance, and in the worst case scenario OOM the task.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel flaw can let io_uring multishot receive handling generate too many completion events, degrading performance and potentially causing the task to run out of memory. The public record does not show code execution, privilege escalation, or active exploitation.

Executive priority

Treat as a normal kernel maintenance priority unless affected systems are multi-tenant, internet-facing, or run io_uring-heavy network services. No source indicates emergency exploitation, but resource exhaustion bugs can affect availability.

Technical view

The issue is in Linux kernel io_uring networking multishot recv completion queue event handling. The fix prevents overflowing multishot recv CQEs, which could otherwise become uncontrolled, hurt performance, and in worst case OOM the task.

Likely exposure

Exposure is likely limited to Linux systems running affected kernel versions that use io_uring networking multishot receive paths. The bundle lists Linux 6.0 through fixed/stable ranges around 6.5.3 and 6.6, but distribution backports need vendor confirmation.

Exploitation context

The CVE is not listed as KEV, and the supplied sources do not report active exploitation or public exploit details. The described impact is resource exhaustion/performance degradation rather than confirmed system compromise.

Researcher notes

Evidence is narrow: the CVE record and two kernel stable commits describe a resolved overflow risk in multishot recv CQEs. No CVSS, CWE, exploit status, or distro-specific affected matrix is included, so validation should rely on kernel provenance and vendor advisories.

Mitigation direction

  • Apply vendor kernel updates containing the referenced io_uring/net fix.
  • Check distribution advisories for backported fixes before relying on upstream version numbers.
  • Prioritize internet-facing or multi-tenant Linux workloads using io_uring networking.
  • If updates are unavailable, follow vendor guidance for temporary risk reduction.

Validation and detection

  • Inventory kernel versions across Linux hosts and containers with host-kernel dependency.
  • Confirm whether deployed kernels include the referenced stable commits or vendor backports.
  • Identify applications using io_uring networking, especially multishot receive behavior.
  • Review monitoring for task OOM events or unusual network-service memory growth.
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-2023-54030 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
LinuxLinuxb3fdea6ecb55c3ceea866ff66486927e51a982b3, b3fdea6ecb55c3ceea866ff66486927e51a982b3unaffected
LinuxLinux6.0, 0, 6.5.3, 6.6affected
Weakness

CWE details

No CWE listed

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