# GSD-2022-1007251: ACPI: APEI: do not add task_work to kernel thread to avoid memory leak

> A memory leak in the Linux Kernel ACPI APEI subsystem can lead to resource exhaustion and denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Nov 2022

## What is GSD-2022-1007251?

GSD-2022-1007251 is a memory corruption vulnerability in Kernel, published on 14 Nov 2022. 

### Official description

ACPI: APEI: do not add task_work to kernel thread to avoid memory leak

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.10.150 by commit 110146ce8f84f8f0ef6f09d36e7c5936d5e2f0cf, it was introduced in version v5.8 by commit 7f17b4a121d0d50eca22cb1edebf0a157f3e43bf. For more details please see the references link.

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

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-1007251?

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

## Is GSD-2022-1007251 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: GSD-2022-1007251 is a memory corruption vulnerability in Kernel, published on 14 Nov 2022. 
Exploitation: There is no known exploitation of GSD-2022-1007251 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-1007251/ (Markdown: https://insights.sbomify.com/GSD-2022-1007251/index.md)
```

## Sources

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

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