# GSD-2023-1001425: ntb_netdev: Use dev_kfree_skb_any() in interrupt context

> A bug in the ntb_netdev driver caused improper memory freeing in interrupt context, potentially leading to system instability or crashes.

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

## What is GSD-2023-1001425?

GSD-2023-1001425 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

ntb_netdev: Use dev_kfree_skb_any() in interrupt context

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.10.163 by commit 13286ad1c7c49c606fdcba4cf66f953a1a16c1ca, it was introduced in version v3.9 by commit 765ccc7bc3d913e18b887a86de1e86db701a2d78. For more details please see the references link.

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

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

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

## Is GSD-2023-1001425 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: GSD-2023-1001425 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-1001425 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-1001425/ (Markdown: https://insights.sbomify.com/GSD-2023-1001425/index.md)
```

## Sources

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

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