Skip to content
Fencer Intel
high 8.2

CVE-2025-6297 json

dpkg-deb: Fix cleanup for control member with restricted directories

published last yr. modified 4mo ago also EUVD-2025-19670

cvss
8.2
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 41%
public exploits
0
none known

Summary

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.

Patch / fix

  • Debian dpkg ed6bbd445dd8800308c67236ba35d08004c98e82
  • dpkg Debian 12 1.21.23
  • dpkg Debian 14, Debian 13 1.22.21

debian advisories DEBIAN-CVE-2025-6297

  • dpkg Ubuntu 22.04 LTS 1.21.1ubuntu2.6
  • dpkg Ubuntu 24.04 LTS 1.22.6ubuntu6.5
  • dpkg Ubuntu 25.10 1.22.21ubuntu1

ubuntu advisories UBUNTU-CVE-2025-6297

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • update-alternatives Linux Micro 6.1 1.22.0-slfo.1.1_2.1
  • update-alternatives Linux Micro 6.0 1.22.0-2.1
  • dpkg SLE Module for Development Tools 15 SP7, SLE Module for Development Tools 15 SP6, openSUSE Leap 15.6 1.19.0.4-150000.4.7.1
  • update-alternatives SLE Module for Basesystem 15 SP7, SLE Module for Basesystem 15 SP6, SLE Micro 5.5 +5 more 1.19.0.4-150000.4.7.1

suse advisories SUSE-SU-2025:20670-1SUSE-SU-2025:20562-1SUSE-SU-2025:02734-1

  • dpkg openSUSE Tumbleweed 1.22.21-1.1

opensuse advisories openSUSE-SU-2025:15314-1

Is CVE-2025-6297 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-6297 updated cvss 2.5

dpkg: dpkg excessive disk usage

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.48% chance of exploitation in the next 30 days, higher than 41% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CISA ADP 3.1 8.2 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
CNA 3.1 8.2 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Affected products

  • Debian dpkg

Classification

Weakness
  • CWE-732 Incorrect Permission Assignment for Critical Resource
  • CWE-400 Uncontrolled Resource Consumption

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.