{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-97968 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-97968 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-97968 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-97968/ (Markdown: https://insights.sbomify.com/CVE-2026-97968/index.md)","id":"CVE-2026-97968","markdown":"https://insights.sbomify.com/CVE-2026-97968/index.md","name":"CVE-2026-97968","record":{"aliases":["BELL-CVE-2026-97968","DEBIAN-CVE-2026-97968","GHSA-fqg8-p65w-8fh2","UBUNTU-CVE-2026-97968"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"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.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nhwmon: (corsair-cpro) Create debugfs entries after hwmon registration\n\nccp_debugfs_init() registers debugfs files whose private data is the devm\nallocated ccp.  It runs before hwmon_device_register_with_info(), so when\nthat registration fails, ccp_probe() returns with the files still in\nplace.  The HID core then frees ccp, and ccp_remove() is not called for a\nfailed probe, so nothing removes them later either.  Reading one of the\nfiles dereferences the freed pointer.\n\nCreate the debugfs entries only after the hwmon device has been\nregistered, so no failing path can leave them behind.\n\nThe two version queries stay where they are.  They send USB commands\nwithout holding ccp-\u003emutex, which is only safe as long as nothing else\ncan call send_usb_cmd(); once the hwmon device is registered its\ncallbacks can do so concurrently.  Only the debugfs creation moves, and\nit is told which queries succeeded.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"hwmon: (corsair-cpro) Create debugfs entries after hwmon registration","id":"CVE-2026-97968","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"watchdog: msc313e: Fix clock leak and spurious timer in settimeout()","id":"CVE-2026-97969"},"packages":[],"prev":{"headline":"hwmon: (corsair-cpro) Remove debugfs entries when probe fails","id":"CVE-2026-97967"},"products":["Linux"],"published":"2026-09-25","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"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.","url":"https://insights.sbomify.com/CVE-2026-97968/"}