CVE-2023-52903: io_uring: lock overflowing for IOPOLL
In the Linux kernel, the following vulnerability has been resolved:
io_uring: lock overflowing for IOPOLL
syzbot reports an issue with overflow filling for IOPOLL:
WARNING: CPU: 0 PID: 28 at io_uring/io_uring.c:734 io_cqring_event_overflow+0x1c0/0x230 io_uring/io_uring.c:734
CPU: 0 PID: 28 Comm: kworker/u4:1 Not tainted 6.2.0-rc3-syzkaller-16369-g358a161a6a9e #0
Workqueue: events_unbound io_ring_exit_work
Call trace:
io_cqring_event_overflow+0x1c0/0x230 io_uring/io_uring.c:734
io_req_cqe_overflow+0x5c/0x70 io_uring/io_uring.c:773
io_fill_cqe_req io_uring/io_uring.h:168 [inline]
io_do_iopoll+0x474/0x62c io_uring/rw.c:1065
io_iopoll_try_reap_events+0x6c/0x108 io_uring/io_uring.c:1513
io_uring_try_cancel_requests+0x13c/0x258 io_uring/io_uring.c:3056
io_ring_exit_work+0xec/0x390 io_uring/io_uring.c:2869
process_one_work+0x2d8/0x504 kernel/workqueue.c:2289
worker_thread+0x340/0x610 kernel/workqueue.c:2436
kthread+0x12c/0x158 kernel/kthread.c:376
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:863
There is no real problem for normal IOPOLL as flush is also called with
uring_lock taken, but it's getting more complicated for IOPOLL|SQPOLL,
for which __io_cqring_overflow_flush() happens from the CQ waiting path.
Security readout for executives and security teams
Plain-English summary
CVE-2023-52903 is a Linux kernel io_uring flaw involving locking during IOPOLL completion overflow handling. It is rated high because a local low-privileged user could potentially impact confidentiality, integrity, and availability. The provided sources do not show active exploitation.
Executive priority
Treat as a high-priority Linux patching issue for multi-user, shared, or workload-hosting systems. It is less urgent than a remotely exploitable internet-facing flaw, but local privilege conditions make it important for defense-in-depth and tenant isolation.
Technical view
The issue is in Linux kernel io_uring, where IOPOLL overflow handling could occur without the expected locking, especially in IOPOLL|SQPOLL paths. The CVSS vector is local, low complexity, low privileges, no user interaction, with high CIA impact. Stable kernel commits are listed as references for the resolution.
Likely exposure
Exposure is most relevant on Linux systems running affected kernel versions where local users or untrusted workloads can interact with io_uring. Internet-facing status alone is not the main risk signal because the CVSS attack vector is local.
Exploitation context
The source bundle lists no CISA KEV entry and provides no public evidence of active exploitation. Practical risk depends on whether an attacker already has local code execution or low-privileged access on the Linux host.
Researcher notes
The evidence identifies the affected subsystem and stable kernel fix references, but not exploit availability or distribution-specific package status. Version mapping should be confirmed against the CVE record and downstream vendor advisories before declaring systems fixed or affected.
Mitigation direction
Update to a vendor-supported kernel containing the referenced stable fixes.
Check Linux distribution advisories for backported fixes and exact package versions.
Prioritize shared hosts and systems running untrusted local workloads.
If immediate patching is unavailable, follow vendor guidance for temporary risk reduction.
Validation and detection
Inventory Linux kernel versions across servers, containers hosts, and endpoints.
Confirm whether distribution kernel packages include the referenced stable commits.
Validate vulnerability status with authenticated vulnerability scanning or vendor package metadata.
Monitor CVE and distribution advisories for revised affected-version guidance.
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-52903 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
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.