| From bippy-1.2.0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@kernel.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2025-38002: io_uring/fdinfo: grab ctx->uring_lock around io_uring_show_fdinfo() |
| |
| 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. |
| |
| The Linux kernel CVE team has assigned CVE-2025-38002 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 6.13 with commit 79cfe9e59c2a12c3b3faeeefe38d23f3d8030972 and fixed in 6.14.8 with commit bdb7d2ec2e31c46c45d1f32667dfa8216a72705e |
| Issue introduced in 6.13 with commit 79cfe9e59c2a12c3b3faeeefe38d23f3d8030972 and fixed in 6.15 with commit d871198ee431d90f5308d53998c1ba1d5db5619a |
| |
| Please see https://www.kernel.org for a full list of currently supported |
| kernel versions by the kernel community. |
| |
| Unaffected versions might change over time as fixes are backported to |
| older supported kernel versions. The official CVE entry at |
| https://cve.org/CVERecord/?id=CVE-2025-38002 |
| will be updated if fixes are backported, please check that for the most |
| up to date information about this issue. |
| |
| |
| Affected files |
| ============== |
| |
| The file(s) affected by this issue are: |
| io_uring/fdinfo.c |
| |
| |
| Mitigation |
| ========== |
| |
| The Linux kernel CVE team recommends that you update to the latest |
| stable kernel version for this, and many other bugfixes. Individual |
| changes are never tested alone, but rather are part of a larger kernel |
| release. Cherry-picking individual commits is not recommended or |
| supported by the Linux kernel community at all. If however, updating to |
| the latest release is impossible, the individual changes to resolve this |
| issue can be found at these commits: |
| https://git.kernel.org/stable/c/bdb7d2ec2e31c46c45d1f32667dfa8216a72705e |
| https://git.kernel.org/stable/c/d871198ee431d90f5308d53998c1ba1d5db5619a |
