CVE-2026-80810
io_uring/rsrc: fix folio size overflow in io_vec_fill_bvec()
Reported by linux · Published September 4, 2026
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.
EPSS 0.21% · 11.0th percentile
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| kernel6.18-modules-extra | Amazon Linux | 1:6.18.48-107.148.amzn2023 |
| microvm-kernel6.18 | Amazon Linux | 1:6.18.48-107.148.amzn2023 |
| kernel6.18-modules-extra-common | Amazon Linux | 1:6.18.48-107.148.amzn2023 |
| kernel6.18-devel | Amazon Linux | 1:6.18.48-107.148.amzn2023 |
| kernel6.18 | Amazon Linux | 1:6.18.48-107.148.amzn2023 |
| kernel6.18-headers | Amazon Linux | 1:6.18.48-107.148.amzn2023 |
| perf6.18 | Amazon Linux | 1:6.18.48-107.148.amzn2023 |
| kernel-livepatch-6.18.48-107.148 | Amazon Linux | 1:1.0-0.amzn2023 |
| kernel6.18-tools | Amazon Linux | 1:6.18.48-107.148.amzn2023 |
| kernel6.18-tools-devel | Amazon Linux | 1:6.18.48-107.148.amzn2023 |
| python3-perf6.18 | Amazon Linux | 1:6.18.48-107.148.amzn2023 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 9ef4cbbcb4ac3786a1a4164507511b76b2a572c5, 9ef4cbbcb4ac3786a1a4164507511b76b2a572c5, 9ef4cbbcb4ac3786a1a4164507511b76b2a572c5 |
| Linux | Linux | 6.15, 0, 6.18.47 |
| amazon:2023 | kernel6.18-modules-extra | 0 |
| amazon:2023 | microvm-kernel6.18 | 0 |
| amazon:2023 | kernel6.18-modules-extra-common | 0 |
| amazon:2023 | kernel6.18-devel | 0 |
| amazon:2023 | kernel6.18 | 0 |
| amazon:2023 | kernel6.18-headers | 0 |
| amazon:2023 | perf6.18 | 0 |
| amazon:2023 | kernel-livepatch-6.18.48-107.148 | 0 |
| amazon:2023 | kernel6.18-tools | 0 |
| amazon:2023 | kernel6.18-tools-devel | 0 |
| amazon:2023 | python3-perf6.18 | 0 |
| linux | linux_kernel | 6.15, 6.15, 6.15 |
| Linux | Linux | 7.3, 9ef4cbbcb4ac3786a1a4164507511b76b2a572c5, 9ef4cbbcb4ac3786a1a4164507511b76b2a572c5 |
| amazon:2023 | bpftool6.18 | 0 |
Timeline
- Sep 4, 2026 Coalition ESS Score
- Sep 4, 2026 CVE Published
- Sep 5, 2026 EPSS Score (12 in total, the first dated here)
- Sep 15, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-80810
vulnetix vdb fixes CVE-2026-80810
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-80810/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart