CVE-2024-9369 · cross-distro fix matrix

CVE-2024-9369: Insufficient data validation in Mojo in Google Chrome prior to 129.0.6668.89 allowed a remote attacker who had compromised the renderer process to perform an out of bounds memory write via a crafted HTML page. (Chromium security severity: High)

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

Fix per ecosystem

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

Debian bookworm

Source: Debian Security Tracker

chromium→ fixed in129.0.6668.89-1~deb12u1urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y chromium
```

Debian trixie

Source: Debian Security Tracker

chromium→ fixed in129.0.6668.89-1urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y chromium
```

Alpine v3.21

Source: Alpine secdb

qt6-qtwebengine→ fixed in6.7.2-r6

apk update && apk add --upgrade qt6-qtwebengine

Alpine edge

Source: Alpine secdb

qt6-qtwebengine→ fixed in6.7.2-r6

apk update && apk add --upgrade qt6-qtwebengine

Are YOU affected by CVE-2024-9369?

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-2024-9369dropped 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)