# GSD-2022-1008300: nilfs2: fix deadlock in nilfs_count_free_blocks()

> A deadlock in the nilfs2 filesystem can cause a denial of service, requiring a kernel patch to resolve.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Dec 2022

## What is GSD-2022-1008300?

GSD-2022-1008300 is a denial of service vulnerability in Kernel, published on 8 Dec 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

nilfs2: fix deadlock in nilfs_count_free_blocks()

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.14.300 by commit 8b4506cff6630bb474bb46a2a75c31e533a756ba, it was introduced in version v2.6.38 by commit e828949e5b42bfd234ee537cdb7c5e3a577958a3. For more details please see the references link.

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

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

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

## Is GSD-2022-1008300 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: GSD-2022-1008300 is a denial of service vulnerability in Kernel, published on 8 Dec 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of GSD-2022-1008300 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-1008300/ (Markdown: https://insights.sbomify.com/GSD-2022-1008300/index.md)
```

## Sources

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

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