CVE-2025-54567 [Medium] | Security Vulnerability in Qemu

CVE-2025-54567 is rated Low Risk (21.8/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.23%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.01%	0.23%	+0.21%
2	2025-07-25	—	0.01%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.01%

0.23%

+0.21%

2025-07-25

—

0.01%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
4.2	3.1	MEDIUM	`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L` Click to expand Attack vector (AV:A) Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet. Attack complexity (AC:H) Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. 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:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:L) Might cause slowdowns, glitches, or partial disruption—not a full brick.	1.6	2.5	[email protected]
5.4	3.1	MEDIUM	`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L` Click to expand Attack vector (AV:A) Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet. 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:N) No account or special rights needed—anonymous or random user is enough. 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:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:L) Might cause slowdowns, glitches, or partial disruption—not a full brick.	2.8	2.5	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

4.2

3.1

MEDIUM

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

Attack vector (AV:A): Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet.
Attack complexity (AC:H): Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
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:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:L): Might cause slowdowns, glitches, or partial disruption—not a full brick.

1.6

2.5

[email protected]

5.4

3.1

MEDIUM

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

Attack vector (AV:A): Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet.
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:N): No account or special rights needed—anonymous or random user is enough.
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:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:L): Might cause slowdowns, glitches, or partial disruption—not a full brick.

2.8

2.5

[email protected]

OS Trackers for CVE-2025-54567

vendor	priority	summary	link
`alpine`	—	CVE-2025-54567: 1 source package rows (qemu); 100 state rows across 2 repos (3.22-community, edge-community); fixed 0, open 100.	https://security.alpinelinux.org/vuln/CVE-2025-54567
`debian`	unimportant	CVE-2025-54567 unimportant priority: Debian including 1 source packages (qemu), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2025-54567
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2025-54567
`suse`	medium	CVE-2025-54567 severity moderate: SUSE including 101 source package names (qemu, qemu-10.0.3-160000.1.2, …), 1068 product×package rows across 42 product lines (SLES-LTSS-TERADATA 15 SP2, SUSE Linux Enterprise High Performance Computing 15 SP3-LTSS, … (42 product lines)): Known Not Affected 1028, Fixed 40.	https://www.suse.com/security/cve/CVE-2025-54567/
`ubuntu`	medium	CVE-2025-54567 medium priority: Ubuntu including 1 source packages (qemu), 8 status rows across 8 suites (bionic, focal, jammy, noble, plucky, trusty, upstream, xenial): not-affected 7, needs-triage 1.	https://ubuntu.com/security/CVE-2025-54567

Affected software / configurations for CVE-2025-54567

Vendor	Product	Version	Raw CPE
qemu	qemu	<= 10.0.3	cpe:2.3:a:qemu:qemu::::::::

References for CVE-2025-54567

URL	Tags
https://lore.kernel.org/qemu-devel/[email protected]/	Mailing List Patch

URL

CVE-2025-54567

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

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

Weakness enumeration for CVE-2025-54567

OS Trackers for CVE-2025-54567

Affected software / configurations for CVE-2025-54567

References for CVE-2025-54567