# SUSE-SU-2025:20310-1: Security update for freetype2

> An attacker can cause denial of service or potentially execute code via malformed font files due to double-free and stack allocation flaws in the Freetype2 library.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 13 May 2025

## What is SUSE-SU-2025:20310-1?

SUSE-SU-2025:20310-1 is a memory corruption vulnerability in freetype2, published on 13 May 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

This update for freetype2 fixes the following issues:

Update to 2.13.2:

  * Some  fields in the `FT_Outline` structure have been changed
    from signed to unsigned type, which better reflects the actual
    usage. It is also an additional means to protect against
    malformed input.
  * Rare double-free crashes in the cache subsystem have been fixed.
  * Excessive stack allocation in the autohinter has been fixed.
  * The B/W  rasterizer has received a major upkeep that results in
    large performance improvements.  The rendering speed has
    increased and even doubled for very complex glyphs.

## Which versions are affected by SUSE-SU-2025:20310-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `freetype2` | SUSE:Linux Micro 6.1 | All versions | 2.13.3-slfo.1.1_1.1 |

## How do I fix SUSE-SU-2025:20310-1?

Upgrade to a fixed version.

## Is SUSE-SU-2025:20310-1 being exploited?

There is no known exploitation of SUSE-SU-2025:20310-1 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for SUSE-SU-2025:20310-1 and fix it if it is affected.

What it is: SUSE-SU-2025:20310-1 is a memory corruption vulnerability in freetype2, published on 13 May 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of SUSE-SU-2025:20310-1 in the wild and no public exploit code.

Affected product: freetype2. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/SUSE-SU-2025-20310-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2025-20310-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/SUSE-SU-2025:20310-1

---
From sbomify Insights: https://insights.sbomify.com/SUSE-SU-2025-20310-1/
Summaries are generated and may contain mistakes; the official description above is the record.