CVE-2025-6297 | dpkg-deb: Fix cleanup for control member with restricted directories

It was discovered that dpkg-deb does not properly sanitize directory permissions when extracting a control member into a temporary directory, which is documented as being a safe operation even on untrusted data. This may result in leaving temporary files behind on cleanup. Given automated and repeated execution of dpkg-deb commands on adversarial .deb packages or with well compressible files, placed inside a directory with permissions not allowing removal by a non-root user, this can end up in a DoS scenario due to causing disk quota exhaustion or disk full conditions.

Published: 2025-07-01 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-6297 is rated Moderate Risk (50.3/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.27%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

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

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-22 0.25% 0.27% +0.02%
2 2026-04-27 0.08% 0.25% +0.17%
3 2026-03-21 — 0.08% —

Full EPSS history (5 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.2 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
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:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 4.2 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2025-6297

OS Trackers for CVE-2025-6297

vendor priority summary link
alpine — CVE-2025-6297: 1 source package rows (dpkg); 26 state rows across 6 repos (3.19-main, 3.20-main, 3.21-main, 3.22-main, 3.23-main, edge-main); fixed 0, open 26. https://security.alpinelinux.org/vuln/CVE-2025-6297
debian not yet assigned CVE-2025-6297 not yet assigned priority: Debian including 1 source packages (dpkg), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 1. https://security-tracker.debian.org/tracker/CVE-2025-6297
suse medium CVE-2025-6297 severity moderate: SUSE including 50 source package names (0.0.17-1.1:update-alternatives-1.19.0.4-150000.4.7.1, 0.1.6-1.2:update-alternatives-1.19.0.4-150000.4.7.1, …), 340 product×package rows across 328 product lines (Container bci/kiwi, Container bci/spack, … (328 product lines)): Fixed 340. https://www.suse.com/security/cve/CVE-2025-6297/
ubuntu low CVE-2025-6297 low priority: Ubuntu including 1 source packages (dpkg), 10 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): released 5, needs-triage 4, ignored 1. https://ubuntu.com/security/CVE-2025-6297

Affected software / configurations for CVE-2025-6297

Vendor Product Version Raw CPE
debian dpkg < 1.22.21 cpe:2.3:a:debian:dpkg:*:*:*:*:*:*:*:*

References for CVE-2025-6297

cvelogic Threat Intelligence