Linux Kernel up to 5.10.187/5.15.120/6.1.38/6.4.3 io_uring missing initialization

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Linux Kernel up to 5.10.187/5.15.120/6.1.38/6.4.3 and classified as critical. Impacted is an unknown function of the component io_uring. Performing a manipulation results in missing initialization. This vulnerability is known as CVE-2023-53461. No exploit is available. The affected component should be upgraded.
Details
A vulnerability, which was classified as critical, was found in Linux Kernel up to 5.10.187/5.15.120/6.1.38/6.4.3. This affects an unknown part of the component io_uring. The manipulation with an unknown input leads to a missing initialization vulnerability. CWE is classifying the issue as CWE-456. The product does not initialize critical variables, which causes the execution environment to use unexpected values. The impact remains unknown. The summary by CVE is:
In the Linux kernel, the following vulnerability has been resolved: io_uring: wait interruptibly for request completions on exit WHen the ring exits, cleanup is done and the final cancelation and waiting on completions is done by io_ring_exit_work. That function is invoked by kworker, which doesn't take any signals. Because of that, it doesn't really matter if we wait for completions in TASK_INTERRUPTIBLE or TASK_UNINTERRUPTIBLE state. However, it does matter to the hung task detection checker! Normally we expect cancelations and completions to happen rather quickly. Some test cases, however, will exit the ring and park the owning task stopped (eg via SIGSTOP). If the owning task needs to run task_work to complete requests, then io_ring_exit_work won't make any progress until the task is runnable again. Hence io_ring_exit_work can trigger the hung task detection, which is particularly problematic if panic-on-hung-task is enabled. As the ring exit doesn't take signals to begin with, have it wait interruptibly rather than uninterruptibly. io_uring has a separate stuck-exit warning that triggers independently anyway, so we're not really missing anything by making this switch.
It is possible to read the advisory at git.kernel.org. This vulnerability is uniquely identified as CVE-2023-53461 since 10/01/2025. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 03/18/2026).
The vulnerability scanner Nessus provides a plugin with the ID 302727 (EulerOS 2.0 SP11 : kernel (EulerOS-SA-2026-1582)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 5.10.188, 5.15.121, 6.1.39 or 6.4.4 eliminates this vulnerability. Applying the patch 28e649dc9947e6525c95e32aa9a8e147925e3f56/8e29835366138389bfad3b31ea06960d0a77bf77/b50d6e06cca7b67a3d73ca660dda27662b76e6ea/58e80cb68b057e974768792c34708c6957810486/4826c59453b3b4677d6bf72814e7ababdea86949 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the databases at Tenable (302727), EUVD (EUVD-2025-32796) and CERT Bund (WID-SEC-2025-2187). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Affected
- Amazon Linux 2
- Red Hat Enterprise Linux
- SUSE Linux
- Oracle Linux
- Open Source Linux Kernel
- Dell Secure Connect Gateway
Product
Type
Vendor
Name
Version
- 5.10.187
- 5.15.120
- 6.1.0
- 6.1.1
- 6.1.2
- 6.1.3
- 6.1.4
- 6.1.5
- 6.1.6
- 6.1.7
- 6.1.8
- 6.1.9
- 6.1.10
- 6.1.11
- 6.1.12
- 6.1.13
- 6.1.14
- 6.1.15
- 6.1.16
- 6.1.17
- 6.1.18
- 6.1.19
- 6.1.20
- 6.1.21
- 6.1.22
- 6.1.23
- 6.1.24
- 6.1.25
- 6.1.26
- 6.1.27
- 6.1.28
- 6.1.29
- 6.1.30
- 6.1.31
- 6.1.32
- 6.1.33
- 6.1.34
- 6.1.35
- 6.1.36
- 6.1.37
- 6.1.38
- 6.4.0
- 6.4.1
- 6.4.2
- 6.4.3
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.4
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Missing initializationCWE: CWE-456 / CWE-453
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 302727
Nessus Name: EulerOS 2.0 SP11 : kernel (EulerOS-SA-2026-1582)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 5.10.188/5.15.121/6.1.39/6.4.4
Patch: 28e649dc9947e6525c95e32aa9a8e147925e3f56/8e29835366138389bfad3b31ea06960d0a77bf77/b50d6e06cca7b67a3d73ca660dda27662b76e6ea/58e80cb68b057e974768792c34708c6957810486/4826c59453b3b4677d6bf72814e7ababdea86949
Timeline
10/01/2025 Advisory disclosed10/01/2025 CVE reserved
10/01/2025 VulDB entry created
03/18/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2023-53461 (🔒)
GCVE (CVE): GCVE-0-2023-53461
GCVE (VulDB): GCVE-100-326595
EUVD: 🔒
CERT Bund: WID-SEC-2025-2187 - Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service
Entry
Created: 10/01/2025 15:04Updated: 03/18/2026 21:12
Changes: 10/01/2025 15:04 (58), 11/24/2025 04:00 (7), 01/17/2026 01:28 (10), 01/18/2026 03:14 (1), 03/18/2026 21:12 (2)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.