# GSD-2022-1000122: usb: gadget: f_sourcesink: Fix isoc transfer for USB_SPEED_SUPER_PLUS

> Fixes an issue in the Linux kernel USB gadget source sink function for Super Plus speed isochronous transfers, with unproven security impact.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Local or same network only
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 18 Feb 2022

## What is GSD-2022-1000122?

GSD-2022-1000122 is a vulnerability in Kernel, published on 18 Feb 2022. It can only be exploited from the same machine or local network.

### Official description

usb: gadget: f_sourcesink: Fix isoc transfer for USB_SPEED_SUPER_PLUS

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 v4.19.228 by commit 2ad9bf965b1c85248ec4eefdf79df3e0f3a3c9a7, it was introduced in version v4.19.195 by commit 10770d2ac0094b053c8897d96d7b2737cd72f7c5. For more details please see the references link.

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

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

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

## Is GSD-2022-1000122 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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