# GSD-2022-1002654: um: Fix out-of-bounds read in LDT setup

> A local attacker can trigger an out-of-bounds read in the Linux Kernel LDT setup, potentially causing a crash or leaking memory.

- **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:** 28 Jun 2022

## What is GSD-2022-1002654?

GSD-2022-1002654 is a memory corruption vulnerability in Kernel, published on 28 Jun 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

um: Fix out-of-bounds read in LDT setup

This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v5.18.3 by commit 91e5ba2af2d729d5126aefd5aa3eadc69b8426e5, it was introduced in version v2.6.15 by commit 858259cf7d1c443c836a2022b78cb281f0a9b95e. For more details please see the references link.

## Which versions are affected by GSD-2022-1002654?

1 open source package ship an affected version, including Kernel.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `Kernel` | Linux | All versions | None |

## How do I fix GSD-2022-1002654?

No fix has been published for GSD-2022-1002654 yet. Limit exposure of the affected software until one is available.

## Is GSD-2022-1002654 being exploited?

There is no known exploitation of GSD-2022-1002654 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GSD-2022-1002654 and fix it if it is affected.

What it is: GSD-2022-1002654 is a memory corruption vulnerability in Kernel, published on 28 Jun 2022. 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 GSD-2022-1002654 in the wild and no public exploit code.

Affected packages and fixed versions:
- Kernel (Linux): affected all versions; no fix listed

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/GSD-2022-1002654/ (Markdown: https://insights.sbomify.com/GSD-2022-1002654/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GSD-2022-1002654

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