# GSD-2021-1001992: isofs: Fix out of bound access for corrupted isofs image

> A local attacker can cause a denial of service by mounting a corrupted ISO9660 filesystem image in the Linux kernel.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Nov 2021

## What is GSD-2021-1001992?

GSD-2021-1001992 is a memory corruption vulnerability in Kernel, published on 14 Nov 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

isofs: Fix out of bound access for corrupted isofs image

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.19.217 by commit b0ddff8d68f2e43857a84dce54c3deab181c8ae1. For more details please see the references link.

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

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

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

## Is GSD-2021-1001992 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: GSD-2021-1001992 is a memory corruption vulnerability in Kernel, published on 14 Nov 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GSD-2021-1001992 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-1001992/ (Markdown: https://insights.sbomify.com/GSD-2021-1001992/index.md)
```

## Sources

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

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