CVE-2025-23154 [Medium] | Security Vulnerability in Linux Kernel

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.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-09	0.07%	0.02%	-0.04%
2	2026-02-25	0.02%	0.07%	+0.05%
3	2025-05-02	—	0.02%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-09

0.07%

0.02%

-0.04%

2026-02-25

0.02%

0.07%

+0.05%

2025-05-02

—

0.02%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
5.5	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	3.6	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

5.5

3.1

MEDIUM

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

3.6

[email protected]

OS Trackers for CVE-2025-23154

vendor	priority	summary	link
`debian`	unimportant	CVE-2025-23154 unimportant priority: Debian including 1 source packages (linux), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2025-23154
`redhat`	low	—	https://access.redhat.com/security/cve/CVE-2025-23154
`suse`	medium	CVE-2025-23154 severity moderate: SUSE including 88 source package names (15.7.20.5.1:kernel-default-6.4.0-150700.53.3.1, cluster-md-kmp-default, …), 417 product×package rows across 98 product lines (Container suse/hpc/warewulf4-x86_64/sle-hpc-node, Image SLES15-SP7-Azure-3P, … (98 product lines)): Known Not Affected 254, Fixed 163.	https://www.suse.com/security/cve/CVE-2025-23154/
`ubuntu`	medium	CVE-2025-23154 medium priority: Ubuntu including 158 source packages (linux, linux-allwinner-5.19, …), 1551 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 1145, ignored 161, not-affected 143, released 100, needs-triage 2.	https://ubuntu.com/security/CVE-2025-23154

Affected software / configurations for CVE-2025-23154

Vendor	Product	Version	Raw CPE
linux	linux_kernel	>= 6.10, < 6.12.24	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 6.13, < 6.13.12	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 6.14, < 6.14.3	cpe:2.3:o:linux:linux_kernel::::::::

References for CVE-2025-23154

URL	Tags
https://git.kernel.org/stable/c/6889ae1b4df1579bcdffef023e2ea9a982565dff	Patch
https://git.kernel.org/stable/c/7888c9fc0b2d3636f2e821ed1ad3c6920fa8e378	Patch
https://git.kernel.org/stable/c/9aa804e6b9696998308095fb9d335046a71550f1	Patch
https://git.kernel.org/stable/c/b7c6d081c19a5e11bbd77bb97a62cff2b6b21cb5	Patch

URL

CVE-2025-23154 | io_uring/net: fix io_req_post_cqe abuse by send bundle

Exploit prediction scoring system (EPSS) score for CVE-2025-23154

Common vulnerability scoring system (CVSS) metrics for CVE-2025-23154

Weakness enumeration for CVE-2025-23154

OS Trackers for CVE-2025-23154

Affected software / configurations for CVE-2025-23154

References for CVE-2025-23154