io_uring: fix memory leak when removing provided buffers
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel ac48787f58d1068f4e06d627c1135784d64b4c72, Kernel b4a72c0589fdea6259720375426179888969d6a2 and Kernel c117c15927772d1624c29c092b6bd3f47c7faa48.
In the Linux kernel, the following vulnerability has been resolved: io_uring: fix memory leak when removing provided buffers When removing provided buffers, io_buffer structs are not being disposed of, leading to a memory leak. They can't be freed individually, because they are allocated in page-sized groups. They need to be added to some free list instead, such as io_buffers_cache. All callers already hold the lock protecting it, apart from when destroying buffers, so had to extend the lock there.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =5.18, >=cc3cec8367cba76a8ae4c271eba8450f3efc1ba3 <ac48787f58d1068f4e06d627c1135784d64b4c72, >=cc3cec8367cba76a8ae4c271eba8450f3efc1ba3 <b4a72c0589fdea6259720375426179888969d6a2, >=cc3cec8367cba76a8ae4c271eba8450f3efc1ba3 <c117c15927772d1624c29c092b6bd3f47c7faa48 | ac48787f58d1068f4e06d627c1135784d64b4c72, b4a72c0589fdea6259720375426179888969d6a2, c117c15927772d1624c29c092b6bd3f47c7faa48 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket