CVE-2025-38453 Information
Description
In the Linux kernel the following vulnerability has been resolved:
io_uring/msg_ring: ensure io_kiocb freeing is deferred for RCU
syzbot reports that defer/local task_work adding via msg_ring can hit a request that has been freed:
CPU: 1 UID: 0 PID: 19356 Comm: iou-wrk-19354 Not tainted 6.16.0-rc4-syzkaller-00108-g17bbde2e1716 0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine BIOS Google 05/07/2025
Call Trace:
which is supposed to be safe with how requests are allocated. But msg ring requests alloc and free on their own and hence must defer freeing to a sane time.
Add an rcu_head and use kfree_rcu() in both spots where requests are freed. Only the one in io_msg_tw_complete() is strictly required as it has been visible on the other ring but use it consistently in the other spot as well.
This should not cause any other issues outside of KASAN rightfully complaining about it.
Reference
https://git.kernel.org/stable/c/e5b3432f4a6b418b8bd8fc91f38efbf17a77167a https://git.kernel.org/stable/c/fc582cd26e888b0652bc1494f252329453fd3b23
Related CNNVD
CNNVD-202507-3304 (Published: 2025-07-25)
Share on: