This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.

Metrics

No CVSS v4.0

Attack Vector Local

Attack Complexity Low

Privileges Required Low

Scope Unchanged

Confidentiality Impact None

Integrity Impact None

Availability Impact High

User Interaction None

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.

Affected Vendors & Products

No data.

No data.

No data.

No data.

Advisories
Source ID Title
EUVD EUVD EUVD-2025-13975 This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
Fixes

Solution

No solution given by the vendor.

Workaround

No workaround given by the vendor.

References
Link Providers
https://lore.kernel.org/linux-cve-announce/2025050814-CVE-2025-37804-9c2b@gregkh/T cve-icon
https://nvd.nist.gov/vuln/detail/CVE-2025-37804 cve-icon
https://www.cve.org/CVERecord?id=CVE-2025-37804 cve-icon
History

Wed, 18 Jun 2025 16:00:00 +0000

Type Values Removed Values Added
Metrics threat_severity

Moderate

 threat_severity

None

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: always do atomic put from iowq io_uring always switches requests to atomic refcounting for iowq execution before there is any parallilism by setting REQ_F_REFCOUNT, and the flag is not cleared until the request completes. That should be fine as long as the compiler doesn't make up a non existing value for the flags, however KCSAN still complains when the request owner changes oter flag bits: BUG: KCSAN: data-race in io_req_task_cancel / io_wq_free_work ... read to 0xffff888117207448 of 8 bytes by task 3871 on cpu 0: req_ref_put_and_test io_uring/refs.h:22 [inline] Skip REQ_F_REFCOUNT checks for iowq, we know it's set. This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
Title io_uring: always do atomic put from iowq kernel: io_uring: always do atomic put from iowq

Fri, 09 May 2025 02:15:00 +0000

Type Values Removed Values Added
References
Metrics threat_severity

None

 cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Moderate

Thu, 08 May 2025 06:45:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: io_uring: always do atomic put from iowq io_uring always switches requests to atomic refcounting for iowq execution before there is any parallilism by setting REQ_F_REFCOUNT, and the flag is not cleared until the request completes. That should be fine as long as the compiler doesn't make up a non existing value for the flags, however KCSAN still complains when the request owner changes oter flag bits: BUG: KCSAN: data-race in io_req_task_cancel / io_wq_free_work ... read to 0xffff888117207448 of 8 bytes by task 3871 on cpu 0: req_ref_put_and_test io_uring/refs.h:22 [inline] Skip REQ_F_REFCOUNT checks for iowq, we know it's set.
Title io_uring: always do atomic put from iowq
References

Projects

Sign in to view the affected projects.

cve-icon MITRE

Status: REJECTED

Assigner: Linux

Published:

Updated: 2025-05-20T13:54:16.401Z

Reserved: 2025-04-16T04:51:23.942Z

Link: CVE-2025-37804

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Rejected

Published: 2025-05-08T07:15:51.570

Modified: 2025-05-20T14:15:48.763

Link: CVE-2025-37804

cve-icon Redhat

Severity :

Publid Date: 2025-05-08T00:00:00Z

Links: CVE-2025-37804 - Bugzilla

cve-icon OpenCVE Enrichment

No data.

Weaknesses

No weakness.