CVE-2025-38002
MediumIn 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 3.1 score
5.5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected versions
Linux kernel versions
6.13
and later are affected. Fixed in
6.14.8,
6.15
and their respective stable series.
References
The following references provide additional information about CVE-2025-38002 including vendor advisories, patch commits, exploit details, and third-party analysis. Links are sourced from the NIST NVD database.
-
Exploit Issue Tracking
-
PatchKernel patch commithttps://git.kernel.org/stable/c/bdb7d2ec2e31c46c45d1f32667dfa8216a72705e
-
PatchKernel patch commithttps://git.kernel.org/stable/c/d871198ee431d90f5308d53998c1ba1d5db5619a
Frequently asked questions
-
What is CVE-2025-38002?
CVE-2025-38002 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10 . It affects Linux kernel versions from 6.13 onward and has been patched in 6.14.8 and 6.15. CVE-2025-38002 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
What is the CVSS score for CVE-2025-38002?
CVE-2025-38002 has a CVSS score of 5.5 out of 10, rated Medium severity (CVSS 3.1). The vector string is
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H. -
Is there a patch available for CVE-2025-38002?
Yes — CVE-2025-38002 has been patched. Fixed versions include 6.14.8 and 6.15. If you are running Linux kernel 6.13 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2025-38002 actively exploited?
No — CVE-2025-38002 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.