# CVE-2026-97968: hwmon: (corsair-cpro) Create debugfs entries after hwmon registration

> A use-after-free in the Linux kernel corsair-cpro driver allows local attackers to crash the system or potentially execute code via debugfs files.

- **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:** Yes
- **Published:** 25 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-97968, DEBIAN-CVE-2026-97968, GHSA-fqg8-p65w-8fh2, UBUNTU-CVE-2026-97968

## What is CVE-2026-97968?

CVE-2026-97968 is an use after free vulnerability in Linux, published on 25 Sep 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:

hwmon: (corsair-cpro) Create debugfs entries after hwmon registration

ccp_debugfs_init() registers debugfs files whose private data is the devm
allocated ccp.  It runs before hwmon_device_register_with_info(), so when
that registration fails, ccp_probe() returns with the files still in
place.  The HID core then frees ccp, and ccp_remove() is not called for a
failed probe, so nothing removes them later either.  Reading one of the
files dereferences the freed pointer.

Create the debugfs entries only after the hwmon device has been
registered, so no failing path can leave them behind.

The two version queries stay where they are.  They send USB commands
without holding ccp->mutex, which is only safe as long as nothing else
can call send_usb_cmd(); once the hwmon device is registered its
callbacks can do so concurrently.  Only the debugfs creation moves, and
it is told which queries succeeded.

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


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

Apply the vendor's patch.

## Is CVE-2026-97968 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-97968 is an use after free vulnerability in Linux, published on 25 Sep 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-97968 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-97968/ (Markdown: https://insights.sbomify.com/CVE-2026-97968/index.md)
```

## Sources

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

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