OSV-2021-617 Stack-use-after-return in v9fs_setattr
Not scored
Published
Check this codebase for OSV-2021-617 and fix it if it is affected.
What it is: OSV-2021-617 is an use after free vulnerability in qemu, published on 9 Apr 2021.
Exploitation: There is no known exploitation of OSV-2021-617 in the wild and no public exploit code.
Affected packages and fixed versions:
- qemu (OSS-Fuzz): 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/OSV-2021-617/ (Markdown: https://insights.sbomify.com/OSV-2021-617/index.md)
A stack-use-after-return vulnerability in the v9fs_setattr function can cause a crash, potentially leading to denial of service.
- Exploited in the wild
- Not known
- Login needed
- Not stated
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- None listed
What is OSV-2021-617?
OSV-2021-617 is an use after free vulnerability in qemu, published on 9 Apr 2021.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=32995
Crash type: Stack-use-after-return READ 4
Crash state:
v9fs_setattr
coroutine_trampoline
Which versions are affected by OSV-2021-617?
1 open source package ship an affected version, including qemu.
| Package | Affected | Fixed in |
|---|---|---|
qemu OSS-Fuzz | All versions | None |
How do I fix OSV-2021-617?
No fix has been published for OSV-2021-617 yet. Limit exposure of the affected software until one is available.
Upgrade to the fixed version. These bugs are found with fuzzing and sanitisers and avoided by memory-safe languages. More about Use after free.
Is OSV-2021-617 being exploited?
There is no known exploitation of OSV-2021-617 in the wild and no public exploit code.