Metrics
Affected Vendors & Products
Fri, 27 Jun 2025 14:45:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Metrics |
cvssV3_1
|
cvssV3_1
|
Thu, 26 Jun 2025 15:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
References |
|
Tue, 10 Jun 2025 19:00:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Metrics |
cvssV3_1
|
cvssV3_1
|
Sat, 07 Jun 2025 02:45:00 +0000
Type | Values Removed | Values Added |
---|---|---|
References |
| |
Metrics |
threat_severity
|
cvssV3_1
|
Fri, 06 Jun 2025 14:00:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Description | In the Linux kernel, the following vulnerability has been resolved: io_uring/fdinfo: grab ctx->uring_lock around io_uring_show_fdinfo() Not everything requires locking in there, which is why the 'has_lock' variable exists. But enough does that it's a bit unwieldy to manage. Wrap the whole thing in a ->uring_lock trylock, and just return with no output if we fail to grab it. The existing trylock() will already have greatly diminished utility/output for the failure case. This fixes an issue with reading the SQE fields, if the ring is being actively resized at the same time. | |
Title | io_uring/fdinfo: grab ctx->uring_lock around io_uring_show_fdinfo() | |
References |
|

Status: PUBLISHED
Assigner: Linux
Published: 2025-06-06T13:43:41.137Z
Updated: 2025-06-26T14:59:26.666Z
Reserved: 2025-04-16T04:51:23.977Z
Link: CVE-2025-38002

No data.

Status : Awaiting Analysis
Published: 2025-06-06T14:15:22.313
Modified: 2025-06-26T15:15:22.843
Link: CVE-2025-38002
