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.
Covered by Rapid7
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Amazon_linux_2023 | — | Upgrade bpftool-debuginfoUpgrade kernel-debuginfoUpgrade bpftoolUpgrade python3-perf-debuginfoUpgrade kernel-livepatch-6.1.25-37.47Upgrade kernel-libbpf-develUpgrade kernel-debuginfo-common-aarch64Upgrade kernel-develUpgrade kernelUpgrade kernel-libbpfUpgrade kernel-tools-develUpgrade kernel-toolsUpgrade perfUpgrade kernel-tools-debuginfoUpgrade python3-perfUpgrade kernel-libbpf-staticUpgrade perf-debuginfoUpgrade kernel-debuginfo-common-x86_64Upgrade kernel-headers | Feb 20, 2026 | Dec 24, 2025 |
| Debian | — | Upgrade linux | Dec 29, 2025 | Dec 29, 2025 |
| Redhat_linux | — | No solution exists | Jul 17, 2026 | Dec 24, 2025 |
Prioritise with Active Threat Intelligence
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub