CVE-2025-39816Time-of-check Time-of-use (TOCTOU) Race Condition in Linux

Severity
5.5MEDIUMNVD
EPSS
0.0%
top 95.55%
CISA KEV
Not in KEV
Exploit
No known exploits
Timeline
PublishedSep 16

Description

In the Linux kernel, the following vulnerability has been resolved: io_uring/kbuf: always use READ_ONCE() to read ring provided buffer lengths Since the buffers are mapped from userspace, it is prudent to use READ_ONCE() to read the value into a local variable, and use that for any other actions taken. Having a stable read of the buffer length avoids worrying about it changing after checking, or being read multiple times. Similarly, the buffer may well change in between it being picked and be

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitability: 1.8 | Impact: 3.6

Affected Packages4 packages

NVDlinux/linux_kernel6.126.12.49+2
Debianlinux/linux_kernel< 6.12.57-1+1
CVEListV5linux/linuxae98dbf43d755b4e111fcd086e53939bef3e9a1a695673eb5711ee5eb1769481cf1503714716a7d1+4
debiandebian/linux< linux 6.16.5-1 (forky)

Patches

🔴Vulnerability Details

2
OSV
CVE-2025-39816: In the Linux kernel, the following vulnerability has been resolved: io_uring/kbuf: always use READ_ONCE() to read ring provided buffer lengths Since t2025-09-16
GHSA
GHSA-57pg-f379-59c5: In the Linux kernel, the following vulnerability has been resolved: io_uring/kbuf: always use READ_ONCE() to read ring provided buffer lengths Since2025-09-16

📋Vendor Advisories

2
Red Hat
kernel: io_uring/kbuf: always use READ_ONCE() to read ring provided buffer lengths2025-09-16
Debian
CVE-2025-39816: linux - In the Linux kernel, the following vulnerability has been resolved: io_uring/kb...2025
CVE-2025-39816 — Linux vulnerability | cvebase