io_uring: fix memory leak when removing provided buffers
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.1.246.2.116.3In 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.
From the CVE record · Linux
Removing provided buffers in the Linux kernel's io_uring subsystem can leave io_buffer structures allocated, causing a memory leak. The input does not specify attacker access, authentication requirements, or whether user interaction is needed.
Engineers running the Linux kernel should check their versions; affected versions are not specified in the input.