{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-98093 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98093 is a high-severity denial of service vulnerability in Linux kernel, 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-98093 and fix it if it is affected.\n\nWhat it is: CVE-2026-98093 is a high-severity denial of service vulnerability in Linux kernel, 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-98093 in the wild and no public exploit code.\n\nAffected product: Linux kernel. 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-98093/ (Markdown: https://insights.sbomify.com/CVE-2026-98093/index.md)","id":"CVE-2026-98093","markdown":"https://insights.sbomify.com/CVE-2026-98093/index.md","name":"CVE-2026-98093","record":{"aliases":["BELL-CVE-2026-98093","DEBIAN-CVE-2026-98093","GHSA-c37f-rq9m-6c5r","UBUNTU-CVE-2026-98093"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A logic error in the Linux kernel's fsl_micfil driver causes clock reference leaks, potentially leading to denial of service by preventing clock gating.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-404","name":"Improper Resource Shutdown or Release"}],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nASoC: fsl_micfil: balance mclk enable/disable\n\nhw_params() enables mclk unconditionally and hw_free() disables it\nunconditionally, but the PCM core does not guarantee 1:1 pairing:\nhw_free() can run without hw_params(), and hw_params() can be called\nmultiple times from the SETUP state. This triggers an \"already\ndisabled\" WARN() in the first case and leaks an enable reference in\nthe second, leaving the clock ungateable.\n\nGuard both sides with the existing mclk_flag, as fsl_sai.c does with\nmclk_streams.","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":"ASoC: fsl_micfil: balance mclk enable/disable","id":"CVE-2026-98093","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"staging: fbtft: make dirty_lock IRQ-safe","id":"CVE-2026-98094"},"packages":[],"prev":{"headline":"ASoC: amd: yc: fix memory leak in acp6x_pdm_dma_close()","id":"CVE-2026-98092"},"products":["Linux"],"published":"2026-09-25","related":[{"cvss_score":8.8,"headline":"Linux Kernel Out-of-Bounds Write","id":"CVE-2026-53266","kev_date_added":"2026-09-18","published":"2026-06-25"},{"cvss_score":8.8,"headline":"Linux Kernel Improper Input Validation","id":"CVE-2013-6282","kev_date_added":"2022-09-15","published":"2013-11-19"},{"cvss_score":8.4,"headline":"Linux Kernel Heap-Based Buffer Overflow","id":"CVE-2022-0185","kev_date_added":"2024-08-21","published":"2022-02-11"},{"cvss_score":8.4,"headline":"Linux Kernel Privilege Escalation","id":"CVE-2013-2094","kev_date_added":"2022-09-15","published":"2013-05-14"},{"cvss_score":7.8,"headline":"Linux Kernel Unspecified","id":"CVE-2026-53362","kev_date_added":"2026-08-27","published":"2026-07-04"},{"cvss_score":7.8,"headline":"Linux Kernel Missing Initialization of a Variable","id":"CVE-2026-46300","kev_date_added":"2026-10-28","published":"2026-05-23"},{"cvss_score":7.8,"headline":"Linux Kernel Race Condition","id":"CVE-2025-39964","kev_date_added":"2026-09-18","published":"2025-10-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A logic error in the Linux kernel's fsl_micfil driver causes clock reference leaks, potentially leading to denial of service by preventing clock gating.","url":"https://insights.sbomify.com/CVE-2026-98093/"}