{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72008 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72008 is a vulnerability in Linux, published on 15 Aug 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-72008 and fix it if it is affected.\n\nWhat it is: CVE-2026-72008 is a vulnerability in Linux, published on 15 Aug 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-72008 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-72008/ (Markdown: https://insights.sbomify.com/CVE-2026-72008/index.md)","id":"CVE-2026-72008","markdown":"https://insights.sbomify.com/CVE-2026-72008/index.md","name":"CVE-2026-72008","record":{"aliases":["DEBIAN-CVE-2026-72008","GHSA-crr9-wcjh-36g7","UBUNTU-CVE-2026-72008"],"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 null pointer dereference in the MediaTek power domain driver can cause a kernel crash during probe failure or cleanup, leading to denial of service.","user_interaction":"not_required","vuln_class":"null_dereference"},"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\npmdomain: mediatek: Fix possible nullptr KP in HWV cleanup/on-check\n\nShould probe fail for HW_VOTER type power domains, this driver was\nunconditionally trying to perform cleanup for DIRECT_CTL domains,\nbut only after checking if the target domain is powered on... with\nthe DIRECT_CTL scpsys_domain_is_on() code again.\n\nAnd there's more: the scpsys_domain_is_on() function is also being\nunconditionally used in the probe path, for any power domain that\nhas flag MTK_SCPD_KEEP_DEFAULT_OFF!\n\nThis bug was never experienced by anyone because the HWV domains\nnever failed probe, and because none of those is declared with the\naforementioned flag - but it's still something critical.\n\nIn order to fix this, add a check for MTCMOS Type and, based on\nthat, call the correct functions for an \"is on\" check, and also\ndo the same for the cleanup path, calling the correct functions\nfor the \"power off\" action.\n\nFor the latter, since there's a call to pm_genpd_remove() right\nbefore calling power_off, be cautious and add a variation of the\npower off functions (with a _internal suffix) for those to get a\npointer to scpsys_domain instead of one to generic_pm_domain as,\neven if that's still working, this is way too much fragile and\nwould break at some point.","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":"pmdomain: mediatek: Fix possible nullptr KP in HWV cleanup/on-check","id":"CVE-2026-72008","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"pmdomain: imx93-blk-ctrl: Extract PHY as shared domain for DSI/CSI","id":"CVE-2026-72009"},"packages":[],"prev":{"headline":"pmdomain: imx: Fix i.MX8MP VC8000E power up sequence","id":"CVE-2026-72007"},"products":["Linux"],"published":"2026-08-15","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-08-17","vendors":["Linux"]},"summary":"A null pointer dereference in the MediaTek power domain driver can cause a kernel crash during probe failure or cleanup, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2026-72008/"}