CVE-2023-53394 [Medium] | Security Vulnerability in Linux Kernel

In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: xsk: Fix crash on regular rq reactivation When the regular rq is reactivated after the XSK socket is closed it could be reading stale cqes which eventually corrupts the rq. This leads to no more traffic being received on the regular rq and a crash on the next close or deactivation of the rq. Kal Cuttler Conely reported this issue as a crash on the release path when the xdpsock sample program is stopped (killed) and restarted in sequence while traffic is running. This patch flushes all cqes when during the rq flush. The cqe flushing is done in the reset state of the rq. mlx5e_rq_to_ready code is moved into the flush function to allow for this.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2025-09-19	—	0.02%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2025-09-19

—

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]
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	134c704f-9b21-4f2e-91b3-4a467353bcc0

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]

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

134c704f-9b21-4f2e-91b3-4a467353bcc0

OS Trackers for CVE-2023-53394

vendor	priority	summary	link
`debian`	unimportant	CVE-2023-53394 unimportant priority: Debian including 1 source packages (linux), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 1.	https://security-tracker.debian.org/tracker/CVE-2023-53394
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2023-53394
`suse`	medium	CVE-2023-53394 severity moderate: SUSE including 430 source package names (2.1.3-6.80:kernel-default-base-6.4.0-35.1.21.12, 2.1.3-7.57:kernel-default-6.4.0-35.1, …), 850 product×package rows across 177 product lines (Container suse/sl-micro/6.0/base-os-container, Container suse/sl-micro/6.0/kvm-os-container, … (177 product lines)): Fixed 471, Known Affected 231, Known Not Affected 148.	https://www.suse.com/security/cve/CVE-2023-53394/
`ubuntu`	medium	CVE-2023-53394 medium priority: Ubuntu including 150 source packages (linux, linux-allwinner-5.19, …), 1350 status rows across 9 suites (bionic, focal, jammy, noble, plucky, questing, trusty, upstream, xenial): DNE 969, ignored 159, not-affected 142, released 80.	https://ubuntu.com/security/CVE-2023-53394

Affected software / configurations for CVE-2023-53394

Vendor	Product	Version	Raw CPE
linux	linux_kernel	>= 6.1, < 6.4.10	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	6.5	cpe:2.3:o:linux:linux_kernel:6.5:rc1::::::
linux	linux_kernel	6.5	cpe:2.3:o:linux:linux_kernel:6.5:rc2::::::
linux	linux_kernel	6.5	cpe:2.3:o:linux:linux_kernel:6.5:rc3::::::
linux	linux_kernel	6.5	cpe:2.3:o:linux:linux_kernel:6.5:rc4::::::

References for CVE-2023-53394

URL	Tags
https://git.kernel.org/stable/c/02a84eb2af6bea7871cd34264fb27f141f005fd9	Patch
https://git.kernel.org/stable/c/39646d9bcd1a65d2396328026626859a1dab59d7	Patch

URL

CVE-2023-53394 | net/mlx5e: xsk: Fix crash on regular rq reactivation

Exploit prediction scoring system (EPSS) score for CVE-2023-53394

Common vulnerability scoring system (CVSS) metrics for CVE-2023-53394

Weakness enumeration for CVE-2023-53394

OS Trackers for CVE-2023-53394

Affected software / configurations for CVE-2023-53394

References for CVE-2023-53394