# GSD-2022-1002430: NFS: remove unneeded check in decode_devicenotify_args()

> An unneeded check in the NFS device notify decoder was removed, potentially addressing a minor logic flaw or cleanup issue in the Linux kernel.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 24 Apr 2022

## What is GSD-2022-1002430?

GSD-2022-1002430 is a vulnerability in Kernel, published on 24 Apr 2022. 

### Official description

NFS: remove unneeded check in decode_devicenotify_args()

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.276 by commit a5ddd85bad671bee4a98e1dee3c23e8aff78288f, it was introduced in version v4.0 by commit a4f743a6bb201662962fa888e3f978583d61691e. For more details please see the references link.

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

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

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

## Is GSD-2022-1002430 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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