tiff: An out-of-memory flaw was found in libtiff that could be triggered by passing a crafted tiff file to the TIFFRasterSc...
CVE-2023-52355 is fixed in 4 products on 1 platform, first by DEBIAN-CVE-2023-52355, released January 25, 2024. It is not reported as exploited. Patch Radar priority: High.
An out-of-memory flaw was found in libtiff that could be triggered by passing a crafted tiff file to the TIFFRasterScanlineSize64() API. This flaw allows a remote attacker to cause a denial of service via a crafted input with a size smaller than 379 KB.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| libtiff · RHEL 9 | 0:4.4.0-15.el9 | RHSA-2025:20801 | Nov 11, 2025 |
| libtiff · almalinux 10 | 4.6.0-8.el10_2.4 | ALSA-2026:41892 | Jul 20, 2026 |
| libtiff · ol 10 | 0:4.6.0-8.el10_2.4 | ELSA-2026-41892 | Jul 20, 2026 |
| libtiff · ol 9 | 0:4.4.0-15.el9 | ELSA-2025-20801 | Nov 17, 2025 |
| libtiff · rocky 10 | 0:4.6.0-8.el10_2.4 | RLSA-2026:41892 | Jul 22, 2026 |
| libtiff · rocky 9 | 0:4.4.0-15.el9_7.2.0.1 | RLSA-2025:20801 | May 21, 2026 |
| libtiff-devel · RHEL 9 | 0:4.4.0-15.el9 | RHSA-2025:20801 | Nov 11, 2025 |
| libtiff-devel · almalinux 10 | 4.6.0-8.el10_2.4 | ALSA-2026:41892 | Jul 20, 2026 |
| libtiff-devel · ol 10 | 0:4.6.0-8.el10_2.4 | ELSA-2026-41892 | Jul 20, 2026 |
| libtiff-devel · ol 9 | 0:4.4.0-15.el9 | ELSA-2025-20801 | Nov 17, 2025 |
| libtiff-tools · RHEL 9 | 0:4.4.0-15.el9 | RHSA-2025:20801 | Nov 11, 2025 |
| libtiff-tools · almalinux 10 | 4.6.0-8.el10_2.4 | ALSA-2026:41892 | Jul 20, 2026 |
| libtiff-tools · ol 10 | 0:4.6.0-8.el10_2.4 | ELSA-2026-41892 | Jul 20, 2026 |
| libtiff-tools · ol 9 | 0:4.4.0-15.el9 | ELSA-2025-20801 | Nov 17, 2025 |
| tiff · Debian 13.5 (trixie) | 4.5.1+git230720-4 | DEBIAN-CVE-2023-52355 | Jan 25, 2024 |
| tiff · Debian 14 | 4.5.1+git230720-4 | DEBIAN-CVE-2023-52355 | Jan 25, 2024 |
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.