# SUSE-SU-2026:2224-1: Security update for xorg-x11-server

> Multiple memory corruption flaws in the X11 server allow local attackers to execute arbitrary code or disclose sensitive information.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jun 2026

## What is SUSE-SU-2026:2224-1?

SUSE-SU-2026:2224-1 is an use after free vulnerability, published on 2 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

This update for xorg-x11-server fixes the following issues

- CreateSaverWindow Use-After-Free Information Disclosure. (bsc#1266301)
- DRI2 DRIGetBuffers/DRIGetBuffersWithFormat Out-Of-Bounds Write. (bsc#1266302)
- Font Alias Stack-based Buffer Overflow. (bsc#1266294)
- GLX ChangeDrawableAttributes Out-Of-Bounds Read/Write. (bsc#1266300)
- XKB Key Types Stack-based Buffer Overflow. (bsc#1266296)
- XKB SetMap Request Stack-based Buffer Overflow. (bsc#1266297)
- XSYNC Use-After-Free in FreeCounter(). (bsc#1266298)
- XSYNC Use-After-Free in miSyncDestroyFence(). (bsc#1266295)
- XSYNC Use-After-Free in SyncChangeCounter(). (bsc#1266299)

## Which versions are affected by SUSE-SU-2026:2224-1?


## How do I fix SUSE-SU-2026:2224-1?

No fix has been published for SUSE-SU-2026:2224-1 yet. Limit exposure of the affected software until one is available.

## Is SUSE-SU-2026:2224-1 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: SUSE-SU-2026:2224-1 is an use after free vulnerability, published on 2 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of SUSE-SU-2026:2224-1 in the wild and no public exploit code.

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-2026-2224-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2026-2224-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/SUSE-SU-2026:2224-1

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