Vulnerability 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.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 6.13, < 6.14.8 |
References
- https://git.kernel.org/stable/c/bdb7d2ec2e31c46c45d1f32667dfa8216a72705ePatch
- https://git.kernel.org/stable/c/d871198ee431d90f5308d53998c1ba1d5db5619aPatch
- https://project-zero.issues.chromium.org/issues/417522668ExploitIssue Tracking
FAQ
What is CVE-2025-38002?
CVE-2025-38002 is a vulnerability with a CVSS score of 5.5 (MEDIUM). 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 'ha...
How severe is CVE-2025-38002?
CVE-2025-38002 has been rated MEDIUM with a CVSS base score of 5.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2025-38002?
Check the references section above for vendor advisories and patch information. Affected products include: Linux Linux Kernel.