Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2025-2635 | This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
Wed, 18 Jun 2025 16:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
threat_severity
|
threat_severity
|
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/rsrc: require cloned buffers to share accounting contexts When IORING_REGISTER_CLONE_BUFFERS is used to clone buffers from uring instance A to uring instance B, where A and B use different MMs for accounting, the accounting can go wrong: If uring instance A is closed before uring instance B, the pinned memory counters for uring instance B will be decremented, even though the pinned memory was originally accounted through uring instance A; so the MM of uring instance B can end up with negative locked memory. | This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| Title | io_uring/rsrc: require cloned buffers to share accounting contexts | kernel: io_uring/rsrc: require cloned buffers to share accounting contexts |
Tue, 11 Feb 2025 13:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-20 | |
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|
Mon, 10 Feb 2025 16:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In the Linux kernel, the following vulnerability has been resolved: io_uring/rsrc: require cloned buffers to share accounting contexts When IORING_REGISTER_CLONE_BUFFERS is used to clone buffers from uring instance A to uring instance B, where A and B use different MMs for accounting, the accounting can go wrong: If uring instance A is closed before uring instance B, the pinned memory counters for uring instance B will be decremented, even though the pinned memory was originally accounted through uring instance A; so the MM of uring instance B can end up with negative locked memory. | |
| Title | io_uring/rsrc: require cloned buffers to share accounting contexts | |
| References |
|
Subscriptions
No data.
Status: REJECTED
Assigner: Linux
Published:
Updated: 2025-05-20T13:55:32.454Z
Reserved: 2024-12-29T08:45:45.740Z
Link: CVE-2025-21686
No data.
Status : Rejected
Published: 2025-02-10T16:15:38.100
Modified: 2025-05-20T14:15:48.270
Link: CVE-2025-21686
OpenCVE Enrichment
No data.
EUVD