This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
Metrics
Affected Vendors & Products
No data.
No data.
No data.
References
History
Tue, 20 May 2025 14:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
Tue, 20 May 2025 14:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In the Linux kernel, the following vulnerability has been resolved: io_uring/uring_cmd: unconditionally copy SQEs at prep time This isn't generally necessary, but conditions have been observed where SQE data is accessed from the original SQE after prep has been done and outside of the initial issue. Opcode prep handlers must ensure that any SQE related data is stable beyond the prep phase, but uring_cmd is a bit special in how it handles the SQE which makes it susceptible to reading stale data. If the application has reused the SQE before the original completes, then that can lead to data corruption. Down the line we can relax this again once uring_cmd has been sanitized a bit, and avoid unnecessarily copying the SQE. | This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| Title | io_uring/uring_cmd: unconditionally copy SQEs at prep time | kernel: io_uring/uring_cmd: unconditionally copy SQEs at prep time |
Wed, 02 Apr 2025 03:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
threat_severity
|
threat_severity
|
Sat, 08 Mar 2025 14:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|
Fri, 07 Mar 2025 09:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In the Linux kernel, the following vulnerability has been resolved: io_uring/uring_cmd: unconditionally copy SQEs at prep time This isn't generally necessary, but conditions have been observed where SQE data is accessed from the original SQE after prep has been done and outside of the initial issue. Opcode prep handlers must ensure that any SQE related data is stable beyond the prep phase, but uring_cmd is a bit special in how it handles the SQE which makes it susceptible to reading stale data. If the application has reused the SQE before the original completes, then that can lead to data corruption. Down the line we can relax this again once uring_cmd has been sanitized a bit, and avoid unnecessarily copying the SQE. | |
| Title | io_uring/uring_cmd: unconditionally copy SQEs at prep time | |
| References |
|
MITRE
Status: REJECTED
Assigner: Linux
Published:
Updated: 2025-05-20T13:53:34.359Z
Reserved: 2024-12-29T08:45:45.777Z
Link: CVE-2025-21837
Vulnrichment
No data.
NVD
Status : Rejected
Published: 2025-03-07T09:15:16.710
Modified: 2025-05-20T14:15:48.343
Link: CVE-2025-21837
Redhat