# GSD-2023-1001635: mtd: Fix device name leak when register device failed in add_mtd_device()

> A memory leak in the Linux Kernel MTD subsystem allows local attackers to potentially disclose sensitive kernel memory contents.

- **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:** 17 Jan 2023

## What is GSD-2023-1001635?

GSD-2023-1001635 is a vulnerability in Kernel, published on 17 Jan 2023. 

### Official description

mtd: Fix device name leak when register device failed in add_mtd_device()

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 v4.9.337 by commit a75f45afa932bfb24a2603ebcea5efd2e7cdcfd6, it was introduced in version v2.6.30 by commit 1f24b5a8ecbb2a3c7080f418974d40e3ffedb221. For more details please see the references link.

## Which versions are affected by GSD-2023-1001635?

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-2023-1001635?

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

## Is GSD-2023-1001635 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for GSD-2023-1001635 and fix it if it is affected.

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

## Sources

- OSV: https://osv.dev/vulnerability/GSD-2023-1001635

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