# GSD-2022-1004200: mm: sparsemem: fix missing higher order allocation splitting

> A bug in Linux kernel sparsemem allocation splitting was fixed, with unproven security impact and attack plausibility.

- **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:** 31 Jul 2022

## What is GSD-2022-1004200?

GSD-2022-1004200 is a vulnerability in Kernel, published on 31 Jul 2022. 

### Official description

mm: sparsemem: fix missing higher order allocation splitting

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.13 by commit 6ebbd46d2ef5f6ab815907e1137bdea6e1a3ec3f, it was introduced in version v5.18 by commit d8d55f5616cf3b900a23a72dd24e7b07211e7859. For more details please see the references link.

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

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

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

## Is GSD-2022-1004200 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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