# GHSA-9hpw-r23r-xgm5: Data race in `Iter` and `IterMut`

> A data race in Rust thread-local iterators can lead to undefined behavior or memory corruption when iterating over values.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Jan 2022
- **Also known as:** RUSTSEC-2022-0006

## What is GHSA-9hpw-r23r-xgm5?

GHSA-9hpw-r23r-xgm5 is a vulnerability in thread_local, published on 23 Jan 2022. 

### Official description

In the affected version of this crate, `{Iter, IterMut}::next` used a weaker memory ordering when loading values than what was required, exposing a potential data race
when iterating over a `ThreadLocal`'s values.

Crates using `Iter::next`, or `IterMut::next` are affected by this issue.

## Which versions are affected by GHSA-9hpw-r23r-xgm5?

3 open source packages ship an affected version, including thread_local.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `thread_local` | crates.io | All versions | 1.1.4 |
| `thread_local` | crates.io | All versions | 1.1.4 |
| `thread_local` | crates.io | From 0.0.0-0 | 1.1.4 |

## How do I fix GHSA-9hpw-r23r-xgm5?

Upgrade thread_local to 1.1.4 or later.

## Is GHSA-9hpw-r23r-xgm5 being exploited?

There is no known exploitation of GHSA-9hpw-r23r-xgm5 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-9hpw-r23r-xgm5 and fix it if it is affected.

What it is: GHSA-9hpw-r23r-xgm5 is a vulnerability in thread_local, published on 23 Jan 2022. 
Exploitation: There is no known exploitation of GHSA-9hpw-r23r-xgm5 in the wild and no public exploit code.

Affected packages and fixed versions:
- thread_local (crates.io): affected all versions; fixed in 1.1.4
- thread_local (crates.io): affected all versions; fixed in 1.1.4
- thread_local (crates.io): affected from 0.0.0-0; fixed in 1.1.4

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/GHSA-9hpw-r23r-xgm5/ (Markdown: https://insights.sbomify.com/GHSA-9hpw-r23r-xgm5/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-9hpw-r23r-xgm5

---
From sbomify Insights: https://insights.sbomify.com/GHSA-9hpw-r23r-xgm5/
Summaries are generated and may contain mistakes; the official description above is the record.