UBUNTU-CVE-2026-99266: Medium severity ubuntu/linux vulnerability
In the Linux kernel, the following vulnerability has been resolved: iouring/zcrx: fix buffer offsets in areas above 4GB iozcrxqueuecqe() computes the offset of the buffer in its area from netiovidx(), which is an unsigned int, so the shift is done in 32 bits and only the result is widened to the u64 that goes into the CQE. An area can be up to 1TB in size. For every niov beyond the first 4GB the CQE points the application at a buffer 4GB, or a multiple of that, below the one which has the data. It reads the wrong data, and then returns a buffer it doesn't own via the refill queue while the real one is never given back.
Affected Software
Event History
Frequently Asked Questions
Which systems are exposed to this issue?
The affected software list includes Ubuntu linux, linux-fips, linux-aws, linux-azure, linux-gcp, linux-oracle, linux-aws-fips, and linux-azure-fips kernel packages. Exposure requires use of the kernel io_uring zcrx functionality with buffer areas extending beyond 4 GB.
What happens when the vulnerable path is triggered?
For buffers beyond the first 4 GB of an area, the completion queue entry can identify a buffer 4 GB, or a multiple of 4 GB, below the buffer containing the data. The application may read incorrect data and return a buffer it does not own, while the actual buffer is not returned.
What can be done if an update cannot be applied immediately?
Avoid using io_uring zcrx buffer areas larger than 4 GB. This prevents the offset calculation from reaching the affected range.