LibTIFF fax2ps tiff2pdf.c t2p_read_tiff_init null pointer dereference
CVE-2024-13978 is fixed in 6 products on 1 platform, first by DEBIAN-CVE-2024-13978, released August 1, 2025. It is not reported as exploited. Patch Radar priority: Routine.
This update for tiff fixes the following issues: - CVE-2025-9165: local execution manipulation leading to memory leak (bsc#1248330). - CVE-2024-13978: null pointer dereference in component fax2ps (bsc#1247581) - CVE-2025-8534: null pointer dereference in function PS_Lvl2page (bsc#1247582). - CVE-2025-8961: segmentation fault via main function of tiffcrop utility (bsc#1248117).
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| libtiff-opengl · Ubuntu 25.10 (questing) | 4.7.0-3ubuntu2 | libtiff-opengl 4.7.0-3ubuntu2 | Aug 4, 2025 |
| libtiff-tools · Ubuntu 25.10 (questing) | 4.7.0-3ubuntu2 | libtiff-tools 4.7.0-3ubuntu2 | Aug 4, 2025 |
| libtiff6 · Ubuntu 25.10 (questing) | 4.7.0-3ubuntu2 | libtiff6 4.7.0-3ubuntu2 | Aug 4, 2025 |
| libtiffxx6 · Ubuntu 25.10 (questing) | 4.7.0-3ubuntu2 | libtiffxx6 4.7.0-3ubuntu2 | Aug 4, 2025 |
| tiff · Debian 11.6 (bullseye) | 4.2.0-1+deb11u7 | DLA-4315-1 | Sep 30, 2025 |
| tiff · Debian 13.5 (trixie) | 4.7.0-3+deb13u1 | DEBIAN-CVE-2024-13978 | Aug 1, 2025 |
| tiff · Debian 14 | 4.7.0-4 | DEBIAN-CVE-2024-13978 | Aug 1, 2025 |
| tiff · opensuse-leap 15.6 | 4.7.0-150600.3.18.1 | SUSE-SU-2025:03348-1 | Sep 24, 2025 |
| tiff · opensuse-leap 16.0 | 4.7.1-160000.1.1 | OPENSUSE-SU-2025:20049-1 | Nov 19, 2025 |
| tiff · sles 15.6 | 4.7.0-150600.3.18.1 | SUSE-SU-2025:03348-1 | Sep 24, 2025 |
| tiff · sles 15.7 | 4.7.0-150600.3.18.1 | SUSE-SU-2025:03348-1 | Sep 24, 2025 |
| tiff · sles 16.0 | 4.7.1-160000.1.1 | SUSE-SU-2025:21009-1 | Nov 19, 2025 |
| tiff-man · opensuse-leap 16.0 | 4.7.1-160000.1.1 | OPENSUSE-SU-2025:20049-1 | Nov 19, 2025 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.