# CVE-2026-97967: hwmon: (corsair-cpro) Remove debugfs entries when probe fails

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

- **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:** 25 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-97967, DEBIAN-CVE-2026-97967, GHSA-w2f2-2vf7-7q6m, UBUNTU-CVE-2026-97967

## What is CVE-2026-97967?

CVE-2026-97967 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) Remove debugfs entries when probe fails

ccp_debugfs_init() registers debugfs files whose private data is the devm
allocated ccp.  If hwmon_device_register_with_info() fails right after it,
ccp_probe() returns without removing them: the HID core then frees ccp,
and ccp_remove() is not called for a failed probe, so the files stay
behind.  Reading one of them dereferences the freed pointer.

Remove the debugfs entries on that error path.  debugfs_remove_recursive()
waits for readers already inside the show callbacks, so ccp is no longer
reachable through debugfs by the time probe returns.

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


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

Apply the vendor's patch.

## Is CVE-2026-97967 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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