# GSD-2021-1000971: mm/memory-failure: make sure wait for page writeback in memory_failure

> A race condition in the Linux kernel memory failure handler could lead to system instability or 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:** 30 Jun 2021

## What is GSD-2021-1000971?

GSD-2021-1000971 is a vulnerability in Kernel, published on 30 Jun 2021. 

### Official description

mm/memory-failure: make sure wait for page writeback in memory_failure

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.46 by commit 9e379da727a7a031be9b877cde7b9c34a0fb8306, it was introduced in version v3.16 by commit 0bc1f8b0682caa39f45ce1e0228ebf43acb46111. For more details please see the references link.

## Which versions are affected by GSD-2021-1000971?

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-2021-1000971?

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

## Is GSD-2021-1000971 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for GSD-2021-1000971 and fix it if it is affected.

What it is: GSD-2021-1000971 is a vulnerability in Kernel, published on 30 Jun 2021. 
Exploitation: There is no known exploitation of GSD-2021-1000971 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-2021-1000971/ (Markdown: https://insights.sbomify.com/GSD-2021-1000971/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GSD-2021-1000971

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