# GSD-2021-1002658: media: mxl111sf: change mutex_init() location

> A potential security issue in the mxl111sf media driver involving mutex initialization location, with unproven impact.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 27 Dec 2021

## What is GSD-2021-1002658?

GSD-2021-1002658 is a vulnerability in Kernel, published on 27 Dec 2021. 

### Official description

media: mxl111sf: change mutex_init() location

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.222 by commit 4b2d9600b31f9ba7adbc9f3c54a068615d27b390, it was introduced in version v3.7 by commit 8572211842afc53c8450fb470f2b8d02ba7592e0. For more details please see the references link.

## Which versions are affected by GSD-2021-1002658?

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-2021-1002658?

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

## Is GSD-2021-1002658 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for GSD-2021-1002658 and fix it if it is affected.

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

## Sources

- OSV: https://osv.dev/vulnerability/GSD-2021-1002658

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