io_uring/memmap: cast nr_pages to size_t before shifting
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.15.116.16.26.17In the Linux kernel, the following vulnerability has been resolved:
io_uring/memmap: cast nr_pages to size_t before shifting
If the allocated size exceeds UINT_MAX, then it's necessary to cast the mr->nr_pages value to size_t to prevent it from overflowing. In practice this isn't much of a concern as the required memory size will have been validated upfront, and accounted to the user. And > 4GB sizes will be necessary to make the lack of a cast a problem, which greatly exceeds normal user locked_vm settings that are generally in the kb to mb range. However, if root is used, then accounting isn't done, and then it's possible to hit this issue.
From the CVE record · Linux
The Linux kernel's io_uring/memmap code can overflow a size calculation when an allocation exceeds 4 GB. This can occur when root is used, because memory accounting is not performed; normal user memory limits generally prevent reaching that size.
Teams running Linux kernels with the affected io_uring/memmap code should check their kernel against the vendor advisory; affected versions were not provided.