GSD-2022-1007212 nvmet-tcp: add bounds check on Transfer Tag
Not scored
Published
Check this codebase for GSD-2022-1007212 and fix it if it is affected.
What it is: GSD-2022-1007212 is a vulnerability in Kernel, published on 14 Nov 2022.
Exploitation: There is no known exploitation of GSD-2022-1007212 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-1007212/ (Markdown: https://insights.sbomify.com/GSD-2022-1007212/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is GSD-2022-1007212?
GSD-2022-1007212 is a vulnerability in Kernel, published on 14 Nov 2022.
Official description
nvmet-tcp: add bounds check on Transfer Tag
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.10.150 by commit d5bb45f47b37d10f010355686b28c9ebacb361d4. For more details please see the references link.
Which versions are affected by GSD-2022-1007212?
1 open source package ship an affected version, including Kernel.
| Package | Affected | Fixed in |
|---|---|---|
Kernel Linux | All versions | None |
How do I fix GSD-2022-1007212?
No fix has been published for GSD-2022-1007212 yet. Limit exposure of the affected software until one is available.
Is GSD-2022-1007212 being exploited?
There is no known exploitation of GSD-2022-1007212 in the wild and no public exploit code.