{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93273 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93273 is a vulnerability in Linux, published on 24 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-93273 and fix it if it is affected.\n\nWhat it is: CVE-2026-93273 is a vulnerability in Linux, published on 24 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-93273 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-93273/ (Markdown: https://insights.sbomify.com/CVE-2026-93273/index.md)","id":"CVE-2026-93273","markdown":"https://insights.sbomify.com/CVE-2026-93273/index.md","name":"CVE-2026-93273","record":{"aliases":["BELL-CVE-2026-93273","DEBIAN-CVE-2026-93273","GHSA-f775-wj9m-j2c6","UBUNTU-CVE-2026-93273"],"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 missing NULL check in the TPS6594 regulator driver can cause a kernel crash via null pointer dereference during device probing.","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\nregulator: tps6594: Fix device node reference leaks in multiphase loop\n\nIn tps6594_regulator_probe(), the multi-phase configuration loop calls\nof_find_node_by_name() to find buck nodes by name, and of_get_parent()\ntwice to navigate to the PMIC parent node. None of the acquired node\nreferences (np, intermediate parent, np_pmic_parent) are ever released\nvia of_node_put(), causing a reference leak on every loop iteration.\n\nAdditionally, of_find_node_by_name() can return NULL, but the result was\nimmediately passed to of_node_full_name() and of_get_parent() without a\nNULL check, which could lead to a NULL pointer dereference.\n\nFix this by:\n- Adding a NULL check for np after of_find_node_by_name()\n- Storing the intermediate parent node in a local variable np_parent\n- Calling of_node_put() on np, np_parent and np_pmic_parent at the\n  end of each loop iteration","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":"regulator: tps6594: Fix device node reference leaks in multiphase loop","id":"CVE-2026-93273","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"pinctrl: bcm2835: Don't remove an unregistered GPIO chip","id":"CVE-2026-93274"},"packages":[],"prev":{"headline":"remoteproc: qcom_wcnss: Fix handling the lack of PD regulators in v3","id":"CVE-2026-93272"},"products":["Linux"],"published":"2026-09-24","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 missing NULL check in the TPS6594 regulator driver can cause a kernel crash via null pointer dereference during device probing.","url":"https://insights.sbomify.com/CVE-2026-93273/"}