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.
Metrics
Affected Vendors & Products
References
History
Thu, 06 Mar 2025 02:45:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Weaknesses | CWE-401 | |
Metrics |
cvssV3_1
|
cvssV3_1
|
Fri, 28 Feb 2025 02:00:00 +0000
Type | Values Removed | Values Added |
---|---|---|
References |
| |
Metrics |
threat_severity
|
cvssV3_1
|
Thu, 27 Feb 2025 02:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Description | 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. | |
Title | io_uring: prevent reg-wait speculations | |
References |
|

Status: PUBLISHED
Assigner: Linux
Published:
Updated: 2025-03-24T15:37:45.203Z
Reserved: 2025-02-27T02:04:28.915Z
Link: CVE-2024-58000

No data.

Status : Received
Published: 2025-02-27T02:15:14.033
Modified: 2025-02-27T02:15:14.033
Link: CVE-2024-58000
