# CVE-2026-72075: Input: ims-pcu - fix race condition in reset_device sysfs callback

> A race condition in the Linux kernel ims-pcu driver allows local attackers to corrupt shared command buffers, potentially causing system instability or denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 27 Aug 2026
- **Also known as:** BELL-CVE-2026-72075, DEBIAN-CVE-2026-72075, GHSA-h7gg-4wfx-9hw5, UBUNTU-CVE-2026-72075

## What is CVE-2026-72075?

CVE-2026-72075 is a vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

Input: ims-pcu - fix race condition in reset_device sysfs callback

The ims_pcu_reset_device() sysfs callback calls ims_pcu_execute_command()
without acquiring pcu->cmd_mutex. This can lead to data races and
corruption of the shared command buffer if triggered concurrently with
other commands.

Acquire pcu->cmd_mutex before calling ims_pcu_execute_command().

## Which versions are affected by CVE-2026-72075?


## How do I fix CVE-2026-72075?

Apply the vendor's patch.

## Is CVE-2026-72075 being exploited?

There is no known exploitation of CVE-2026-72075 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-72075 and fix it if it is affected.

What it is: CVE-2026-72075 is a vulnerability in Linux, published on 15 Aug 2026. 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 CVE-2026-72075 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

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/CVE-2026-72075/ (Markdown: https://insights.sbomify.com/CVE-2026-72075/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-72075
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-72075
- OSV: https://osv.dev/vulnerability/CVE-2026-72075

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