Every one of these is reachable by opening a file, which is why they were worth a release.
- ffmpeg. A crafted MP4 with a long chain of
psshboxes exhausted the stack when freed (CVE-2026-107678). An RTSP server that answers every request with a redirect pinned a CPU forever; the fix caps it at 8 redirects (CVE-2026-107696). ffmpeg 9.0.3 isn't out, so both are carried as upstream master commits on our 9.0.2. - gst-plugins-good. An MP4 declaring 0 audio channels crashed
qtdemuxwith a division by zero (CVE-2026-46469, CVE-2026-46470). A WAVadtlchunk with an odd size read out of bounds (CVE-2026-1940). Checking the advisory properly mattered: most of upstream's qtdemux change is for channel-layout code that 1.24 doesn't have, which also means the advisory's third CVE doesn't apply to us at all. - gst-plugins-base. An Ogg Opus stream declaring more than 64 channels overflowed
opusdec's buffers (CVE-2026-18297). New patch set for that package. - libsndfile. A WAV or W64 file with IMA ADPCM and a large enough block count overflowed the frame
count, and an IRCAM file with an out-of-range sample rate hit undefined behaviour. libsndfile sits
under
pw-cat, under libpulse (sopactl), and under ffmpeg's PulseAudio input, so opening or previewing an audio file reaches it. There was no version to bump to: 1.2.2 is the newest release, so the two master commits are carried as patches. - podman. An image's
Enventries were parsed with the same parser aspodman run --env VAR*, so an image carrying a bare key, or*, got the matching host variables copied in, or all of them. Server and Desktop ship rootless podman with distrobox on top, so a shell's tokens and keys were onepodman runof an untrusted image away. An image with a malformed env entry now fails to start withinvalid image env variable.
Linux went 7.2.11 → 7.2.12, the stable point release, in all five editions, with nvidia-open rebuilt against it.
Two things the audit found were not what they looked like. Six GStreamer P1s the scanner reports are already fixed in 1.24.13 itself: the advisory patches reverse-apply against our source, and NVD's version ranges skip the 1.24 branch entirely. Two more are in plugins we don't build.