CVE-2025-38002: Linux kernel · io_uring/fdinfo: grab ctx->uring_lock around io_uring_show_fdinfo()
Source GCVE Database
Not known to be exploited · CVSS 5.5 Medium.
Data as of 13 Nov 2026, 18:52 UTC
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 6 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.
What to do
AI-suggested
A fix has been implemented in the Linux kernel by adding a trylock on ctx->uring_lock around io_uring_show_fdinfo(). Users should update to the fixed kernel version once available. No other mitigations are indicated.
Description
CVE-2025-38002 is a medium severity vulnerability in the Linux kernel's io_uring subsystem. It involves improper locking around the io_uring_show_fdinfo() function, which can lead to issues when reading Submission Queue Entry (SQE) fields if the ring buffer is being resized concurrently. The flaw is addressed by wrapping the relevant code with a trylock on ctx->uring_lock, preventing output if the lock cannot be acquired.
References
- nvd.nist.gov/vuln/detail/CVE-2025-38002 (opens in a new tab)
- git.kernel.org/stable/c/bdb7d2ec2e31c46c45d1f32667dfa8216a72705e (opens in a new tab)
- git.kernel.org/stable/c/d871198ee431d90f5308d53998c1ba1d5db5619a (opens in a new tab)
- project-zero.issues.chromium.org/issues/417522668 (opens in a new tab)