# GSD-2022-1000461: ipv6: fix data-race in fib6_info_hw_flags_set / fib6_purge_rt

> A data race in the Linux kernel IPv6 routing code can lead to system instability or denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Feb 2022

## What is GSD-2022-1000461?

GSD-2022-1000461 is a vulnerability in Kernel, published on 27 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ipv6: fix data-race in fib6_info_hw_flags_set / fib6_purge_rt

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.25 by commit 9ed25183e6d47a71f5385dbc52419c473646c768, it was introduced in version v5.12 by commit 0c5fcf9e249ee1d94cf872c99baf9cba7ff9ce27. For more details please see the references link.

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

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

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

## Is GSD-2022-1000461 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: GSD-2022-1000461 is a vulnerability in Kernel, published on 27 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GSD-2022-1000461 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-1000461/ (Markdown: https://insights.sbomify.com/GSD-2022-1000461/index.md)
```

## Sources

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

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