CVE-2020-6070 · cross-distro fix matrix

CVE-2020-6070: An exploitable code execution vulnerability exists in the file system checking functionality of fsck.f2fs 1.12.0. A specially crafted f2fs file can cause a logic flaw and out-of-bounds heap operations, resulting in code execution. An attacker can provide a malicious file to trigger this vulnerabilit

Affects 3 Linux releases across 3 (distro × package) combinations.

Fix per ecosystem

Each block below is a distro release where CVE-2020-6070 has a known fix. Run the listed command on that distro to remediate.

Debian bullseye

Source: Debian Security Tracker

f2fs-tools→ fixed in1.14.0-1urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y f2fs-tools
```

Debian bookworm

Source: Debian Security Tracker

f2fs-tools→ fixed in1.14.0-1urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y f2fs-tools
```

Debian trixie

Source: Debian Security Tracker

f2fs-tools→ fixed in1.14.0-1urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y f2fs-tools
```

Are YOU affected by CVE-2020-6070?

5-second check on your actual server. Reads /etc/os-release, uname -r, and the distro's package manager; matches against this same cross-source index live.

curl https://mindsparkstack.com/scan.sh | bash

Form-based quickscan View on NVD

Continuous monitoring beats manual checking

CVE-2020-6070dropped silently in your distro's update channel. Every new CVE is the same story. StackPatch runs the matcher hourly against all 5 sources and emails the exact remediation when something new applies to one of your servers. $99 lifetime, 50 founder seats, 30-day refund.

See StackPatch ($99 lifetime)