CVE-2025-39822: Linux kernel · io_uring/kbuf: fix signedness in this_len calculation
Source GCVE Database
Not known to be exploited · CVSS 5.5 Medium.
Data as of 22 Nov 2026, 02:46 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 16 Sep 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 21 Nov 2026.
What to do
AI-suggested
A fix for this vulnerability has been implemented in the Linux kernel by correcting the signedness in the this_len calculation. Users should apply the official kernel updates that include this fix.
Description
CVE-2025-39822 is a medium severity vulnerability in the Linux kernel's io_uring subsystem related to signedness handling in buffer length calculation. The issue arises because buffer length (buf->len) is treated as unsigned initially but converted to a signed int during commit, which can cause incorrect behavior if the length is large enough to be interpreted as negative. This flaw has been fixed by making the length calculation unsigned.