# GSD-2022-1001508: net: bcmgenet: Use stronger register read/writes to assure ordering


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 24 Apr 2022

## What is GSD-2022-1001508?

GSD-2022-1001508 is a vulnerability in Kernel, published on 24 Apr 2022. 

### Official description

net: bcmgenet: Use stronger register read/writes to assure ordering

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.16.19 by commit 1d717816189fd68f9e089cf89ed1f7327d2c2e71, it was introduced in version v4.14 by commit 69d2ea9c798983c4a7157278ec84ff969d1cd8e8. For more details please see the references link.

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

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

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

## Is GSD-2022-1001508 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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