# GSD-2023-1000005: igb: Initialize mailbox message for VF reset

> A vulnerability in the igb driver allows local attackers to read uninitialized memory during VF reset, potentially exposing sensitive kernel data.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jan 2023

## What is GSD-2023-1000005?

GSD-2023-1000005 is a vulnerability in Kernel, published on 17 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

igb: Initialize mailbox message for VF reset

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 v6.0.15 by commit 51fd5ede7ed42f272682a0c33d6f0767b3484a3d, it was introduced in version v4.0 by commit 6ddbc4cf1f4d5a3a58b4223c80881f299dae3774. For more details please see the references link.

## Which versions are affected by GSD-2023-1000005?

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-2023-1000005?

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

## Is GSD-2023-1000005 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for GSD-2023-1000005 and fix it if it is affected.

What it is: GSD-2023-1000005 is a vulnerability in Kernel, published on 17 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of GSD-2023-1000005 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-2023-1000005/ (Markdown: https://insights.sbomify.com/GSD-2023-1000005/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GSD-2023-1000005

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