{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-97969 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-97969 is a denial of service 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-97969 and fix it if it is affected.\n\nWhat it is: CVE-2026-97969 is a denial of service 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-97969 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-97969/ (Markdown: https://insights.sbomify.com/CVE-2026-97969/index.md)","id":"CVE-2026-97969","markdown":"https://insights.sbomify.com/CVE-2026-97969/index.md","name":"CVE-2026-97969","record":{"aliases":["AZL-104220","BELL-CVE-2026-97969","DEBIAN-CVE-2026-97969","GHSA-c6r8-8m99-q662","UBUNTU-CVE-2026-97969"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel watchdog","requires_auth":"high_privilege","summary":"A local attacker with high privileges can cause a clock reference leak and spurious timer activation in the MSC313E watchdog driver, leading to potential denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"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\nwatchdog: msc313e: Fix clock leak and spurious timer in settimeout()\n\nmsc313e_wdt_settimeout() unconditionally calls msc313e_wdt_start() which\nintroduces two severe bugs:\n\n1. If the watchdog is already active, calling start() again will\n   increase the reference count of the clock again.  However stop() is\n   only called once, the reference count is unbalance.\n2. If the watchdog is stopped, calling settimeout() will start\n   the hardware timer accidentally.\n\nFactor out the register-writing logic into a helper function.  Only call\nit in settimeout() if the watchdog is running.  Otherwise, simply update\n`wdev-\u003etimeout`.","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":"watchdog: msc313e: Fix clock leak and spurious timer in settimeout()","id":"CVE-2026-97969","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"watchdog: msc313e: Avoid division by zero","id":"CVE-2026-97970"},"packages":[],"prev":{"headline":"hwmon: (corsair-cpro) Create debugfs entries after hwmon registration","id":"CVE-2026-97968"},"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 local attacker with high privileges can cause a clock reference leak and spurious timer activation in the MSC313E watchdog driver, leading to potential denial of service.","url":"https://insights.sbomify.com/CVE-2026-97969/"}