This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
kernel: io_uring/uring_cmd: unconditionally copy SQEs at prep time
This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
No data.
No data.
No data.
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2025-7588 | This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
| 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 |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
threat_severity
|
threat_severity
|
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|
| 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 |
|
No data.
No weakness.