# GSD-2022-1006949: x86/unwind/orc: Fix unreliable stack dump with gcov

> Unreliable stack dumps in the Linux kernel x86 ORC unwinder when gcov is enabled, potentially affecting debugging and profiling accuracy.

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

## What is GSD-2022-1006949?

GSD-2022-1006949 is a vulnerability in Kernel, published on 14 Nov 2022. 

### Official description

x86/unwind/orc: Fix unreliable stack dump with gcov

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.15.77 by commit 98bada8fa0e38bc6986f50a3c70c474ade5a2f22, it was introduced in version v5.7 by commit f1d9a2abff66aa8156fbc1493abed468db63ea48. For more details please see the references link.

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

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

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

## Is GSD-2022-1006949 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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