Answer in brief
CVE-2025-38002 records a Unknown severity vulnerability in io_uring/fdinfo: grab ctx->uring_lock around io_uring_show_fdinfo(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=79cfe9e59c2a12c3b3faeeefe38d23f3d8030972 <bdb7d2ec2e31c46c45d1f32667dfa8216a72705e || >=79cfe9e59c2a12c3b3faeeefe38d23f3d8030972 <d871198ee431d90f5308d53998c1ba1d5db5619a | bdb7d2ec2e31c46c45d1f32667dfa8216a72705e, d871198ee431d90f5308d53998c1ba1d5db5619a |
| Linux/Linuxgeneric | 6.13 | Not reported |
Published upstream
Jun 6, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2025-38002 records a Unknown severity vulnerability in io_uring/fdinfo: grab ctx->uring_lock around io_uring_show_fdinfo(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=79cfe9e59c2a12c3b3faeeefe38d23f3d8030972 <bdb7d2ec2e31c46c45d1f32667dfa8216a72705e || >=79cfe9e59c2a12c3b3faeeefe38d23f3d8030972 <d871198ee431d90f5308d53998c1ba1d5db5619a | bdb7d2ec2e31c46c45d1f32667dfa8216a72705e, d871198ee431d90f5308d53998c1ba1d5db5619a |
| Linux/Linuxgeneric | 6.13 | Not reported |
Published upstream
Jun 6, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.