Bug 2541169 (CVE-2026-97968) - CVE-2026-97968 kernel: hwmon: (corsair-cpro) Create debugfs entries after hwmon registration
Summary: CVE-2026-97968 kernel: hwmon: (corsair-cpro) Create debugfs entries after hwm...
Keywords:
Status: NEW
Alias: CVE-2026-97968
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-25 10:54 UTC by OSIDB Bzimport
Modified: 2026-09-30 04:50 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-09-25 10:54:17 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.