In the Linux kernel, the following vulnerability has been resolved: io_uring/query: cap user size passed to copy_struct_to_user… (CVE-2026-81009)
A vulnerability in the Linux kernel's io_uring query interface allows a user to specify a size parameter larger than the kernel expects, leading to excessive zeroing of memory up to nearly 4 GiB. This occurs because the user-supplied size is used in copy_struct_to_user() without proper clamping, potentially causing clear_user() to zero trailing bytes beyond intended limits. The issue affects the io_handle_query_entry() function and the IORING_REGISTER_QUERY interface. The vulnerability has been resolved by rejecting sizes larger than PAGE_SIZE, aligning with recommended practices for copy_struct_* interfaces.
AI Analysis
Technical Summary
The Linux kernel vulnerability CVE-2026-81009 involves the io_uring query interface where the user-supplied size (hdr.size) is passed to copy_struct_to_user() without adequate clamping. While io_handle_query_entry() clamps hdr.size for copy_from_user(), it retains the original user value as usize. copy_struct_to_user() uses usize and may clear trailing bytes beyond the kernel's result size, potentially up to nearly 4 GiB due to hdr.size being a 32-bit unsigned integer. This can occur even on error paths where the result size is zero. The interface is accessible without a ring via IORING_REGISTER_QUERY. The fix rejects sizes larger than PAGE_SIZE to prevent excessive zeroing.
Potential Impact
The vulnerability allows a user to request an excessively large size for zeroing memory, which could lead to unintended clearing of memory regions. The description does not specify direct exploitation consequences such as privilege escalation or denial of service, nor does it mention active exploitation in the wild. The impact is primarily related to improper memory handling in the kernel's io_uring query interface.
Mitigation Recommendations
A fix is available that rejects user-supplied sizes larger than PAGE_SIZE in the io_uring query interface, preventing excessive zeroing of memory. Users should apply the official Linux kernel update that includes this fix. Since this is a kernel vulnerability, updating to a patched kernel version is the recommended remediation.
In the Linux kernel, the following vulnerability has been resolved: io_uring/query: cap user size passed to copy_struct_to_user… (CVE-2026-81009)
Description
A vulnerability in the Linux kernel's io_uring query interface allows a user to specify a size parameter larger than the kernel expects, leading to excessive zeroing of memory up to nearly 4 GiB. This occurs because the user-supplied size is used in copy_struct_to_user() without proper clamping, potentially causing clear_user() to zero trailing bytes beyond intended limits. The issue affects the io_handle_query_entry() function and the IORING_REGISTER_QUERY interface. The vulnerability has been resolved by rejecting sizes larger than PAGE_SIZE, aligning with recommended practices for copy_struct_* interfaces.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel vulnerability CVE-2026-81009 involves the io_uring query interface where the user-supplied size (hdr.size) is passed to copy_struct_to_user() without adequate clamping. While io_handle_query_entry() clamps hdr.size for copy_from_user(), it retains the original user value as usize. copy_struct_to_user() uses usize and may clear trailing bytes beyond the kernel's result size, potentially up to nearly 4 GiB due to hdr.size being a 32-bit unsigned integer. This can occur even on error paths where the result size is zero. The interface is accessible without a ring via IORING_REGISTER_QUERY. The fix rejects sizes larger than PAGE_SIZE to prevent excessive zeroing.
Potential Impact
The vulnerability allows a user to request an excessively large size for zeroing memory, which could lead to unintended clearing of memory regions. The description does not specify direct exploitation consequences such as privilege escalation or denial of service, nor does it mention active exploitation in the wild. The impact is primarily related to improper memory handling in the kernel's io_uring query interface.
Mitigation Recommendations
A fix is available that rejects user-supplied sizes larger than PAGE_SIZE in the io_uring query interface, preventing excessive zeroing of memory. Users should apply the official Linux kernel update that includes this fix. Since this is a kernel vulnerability, updating to a patched kernel version is the recommended remediation.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-w44c-cv6c-x94c
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-81009"]
Threat ID: 6aa4a02755bf5e2cf5a86b0a
Added to database: 09/12/2026, 00:43:19 UTC
Last enriched: 09/12/2026, 01:19:39 UTC
Last updated: 09/12/2026, 01:19:39 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.