# ALBA-2020:5504: xorg-x11-server bug fix and enhancement update

> A bug in the X.Org modesetting driver causes a crash when handling missing connectors, leading to a local denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Dec 2020

## What is ALBA-2020:5504?

ALBA-2020:5504 is a denial of service vulnerability in xorg-x11-server-devel, published on 15 Dec 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

X.Org is an open-source implementation of the X Window System. It provides
the basic low-level functionality that full-fledged graphical user
interfaces are designed upon.

Bug Fix(es) and Enhancement(s):

* [DELL 8.2 BUG]The modesetting driver does not gracefully handle missing
connectors on EnterVT (BZ#1883491)

## Which versions are affected by ALBA-2020:5504?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `xorg-x11-server-devel` | AlmaLinux:8 | All versions | 1.20.8-6.1.el8_3 |
| `xorg-x11-server-source` | AlmaLinux:8 | All versions | 1.20.8-6.1.el8_3 |

## How do I fix ALBA-2020:5504?

Apply the vendor's patch.

## Is ALBA-2020:5504 being exploited?

There is no known exploitation of ALBA-2020:5504 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for ALBA-2020:5504 and fix it if it is affected.

What it is: ALBA-2020:5504 is a denial of service vulnerability in xorg-x11-server-devel, published on 15 Dec 2020. 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 ALBA-2020:5504 in the wild and no public exploit code.

Affected product: xorg-x11-server-devel. 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/ALBA-2020-5504/ (Markdown: https://insights.sbomify.com/ALBA-2020-5504/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/ALBA-2020:5504

---
From sbomify Insights: https://insights.sbomify.com/ALBA-2020-5504/
Summaries are generated and may contain mistakes; the official description above is the record.