CVE-2026-80810

published 4 Sep 2026 · updated 19 Oct 2026

io_uring/rsrc: fix folio size overflow in io_vec_fill_bvec()

5.0MediumEPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 3267d7c8ba51642117f7bdd1ece02b2540668476, Kernel 3f3a6a16bbe8bde76532d9415438f8cdef439e5d, Kernel 45c945107e007b1fb73e21cd220277652a45521a and 1 more.

In the Linux kernel, the following vulnerability has been resolved: io_uring/rsrc: fix folio size overflow in io_vec_fill_bvec() io_vec_fill_bvec() computes the folio size with a plain int 1: unsigned long folio_size = 1 << imu->folio_shift; imu->folio_shift is unsigned int and comes from folio_shift() of the folio backing the registered buffer, so it can be 32 or more on a 64 bit kernel. Shifting int 1 that far is undefined, and on x86 and arm64 the count is taken modulo 32, so a shift of 34 yields 4 rather than 16G. Every other folio_shift shift in this file already uses 1UL. The result is that the segment estimate and the fill loop disagree. io_estimate_bvec_size() sizes the bvec array with the real shift: max_segs += (iov[i].iov_len >> shift) + 2; so a 1M iovec on a 16G folio is charged 2 segments, while io_vec_fill_bvec() then walks the same iovec in folio_size chunks of 4 bytes and writes res_bvec[bvec_idx] a quarter of a million times, past the end of the array it was given. src_bvec is advanced once per iteration as well, so imu->bvec is read past its end at the same time. validate_fixed_range() only checks that the range is inside the registered buffer and does not bound the segment count. Reaching it needs a folio with a shift of at least 32, which means a gigantic hugetlb page: 16G on arm64 with 64K pages, where CONT_PMD_SHIFT is 34 and hugetlb_add_hstate(CONT_PMD_SHIFT - PAGE_SHIFT) registers that size, and likewise on powerpc. x86_64 tops out at 1G, so a shift of 30, which still fits in int and is unaffected. Use 1UL, as the rest of the file does.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=6.15, >=9ef4cbbcb4ac3786a1a4164507511b76b2a572c5 <3267d7c8ba51642117f7bdd1ece02b2540668476, >=9ef4cbbcb4ac3786a1a4164507511b76b2a572c5 <3f3a6a16bbe8bde76532d9415438f8cdef439e5d, >=9ef4cbbcb4ac3786a1a4164507511b76b2a572c5 <45c945107e007b1fb73e21cd220277652a45521a, >=9ef4cbbcb4ac3786a1a4164507511b76b2a572c5 <6b308c37fbeba3aa8c634fb1ed53e2f63a5d5a5c3267d7c8ba51642117f7bdd1ece02b2540668476, 3f3a6a16bbe8bde76532d9415438f8cdef439e5d, 45c945107e007b1fb73e21cd220277652a45521a, 6b308c37fbeba3aa8c634fb1ed53e2f63a5d5a5c

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-80810 severity on Zeptric[![CVE-2026-80810](https://zeptric.io/badge/cve/CVE-2026-80810.svg)](https://zeptric.io/cve/CVE-2026-80810)