linux-cve-announce - CVE-2025-23154: io_uring/net: fix io_req_post

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025050129-CVE-2025-23154-36e0@gregkh>
Date: Thu,  1 May 2025 14:56:34 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-23154: io_uring/net: fix io_req_post_cqe abuse by send bundle

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

io_uring/net: fix io_req_post_cqe abuse by send bundle

[  114.987980][ T5313] WARNING: CPU: 6 PID: 5313 at io_uring/io_uring.c:872 io_req_post_cqe+0x12e/0x4f0
[  114.991597][ T5313] RIP: 0010:io_req_post_cqe+0x12e/0x4f0
[  115.001880][ T5313] Call Trace:
[  115.002222][ T5313]  <TASK>
[  115.007813][ T5313]  io_send+0x4fe/0x10f0
[  115.009317][ T5313]  io_issue_sqe+0x1a6/0x1740
[  115.012094][ T5313]  io_wq_submit_work+0x38b/0xed0
[  115.013223][ T5313]  io_worker_handle_work+0x62a/0x1600
[  115.013876][ T5313]  io_wq_worker+0x34f/0xdf0

As the comment states, io_req_post_cqe() should only be used by
multishot requests, i.e. REQ_F_APOLL_MULTISHOT, which bundled sends are
not. Add a flag signifying whether a request wants to post multiple
CQEs. Eventually REQ_F_APOLL_MULTISHOT should imply the new flag, but
that's left out for simplicity.

The Linux kernel CVE team has assigned CVE-2025-23154 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 6.10 with commit a05d1f625c7aa681d8816bc0f10089289ad07aad and fixed in 6.12.24 with commit b7c6d081c19a5e11bbd77bb97a62cff2b6b21cb5
	Issue introduced in 6.10 with commit a05d1f625c7aa681d8816bc0f10089289ad07aad and fixed in 6.13.12 with commit 7888c9fc0b2d3636f2e821ed1ad3c6920fa8e378
	Issue introduced in 6.10 with commit a05d1f625c7aa681d8816bc0f10089289ad07aad and fixed in 6.14.3 with commit 9aa804e6b9696998308095fb9d335046a71550f1
	Issue introduced in 6.10 with commit a05d1f625c7aa681d8816bc0f10089289ad07aad and fixed in 6.15-rc1 with commit 6889ae1b4df1579bcdffef023e2ea9a982565dff

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2025-23154
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	include/linux/io_uring_types.h
	io_uring/io_uring.c
	io_uring/net.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/b7c6d081c19a5e11bbd77bb97a62cff2b6b21cb5
	https://git.kernel.org/stable/c/7888c9fc0b2d3636f2e821ed1ad3c6920fa8e378
	https://git.kernel.org/stable/c/9aa804e6b9696998308095fb9d335046a71550f1
	https://git.kernel.org/stable/c/6889ae1b4df1579bcdffef023e2ea9a982565dff