{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93274 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93274 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-93274 and fix it if it is affected.\n\nWhat it is: CVE-2026-93274 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-93274 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-93274/ (Markdown: https://insights.sbomify.com/CVE-2026-93274/index.md)","id":"CVE-2026-93274","markdown":"https://insights.sbomify.com/CVE-2026-93274/index.md","name":"CVE-2026-93274","record":{"aliases":["BELL-CVE-2026-93274","DEBIAN-CVE-2026-93274","GHSA-6v4f-r38f-j6j4","UBUNTU-CVE-2026-93274"],"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 BCM2835 pinctrl driver can cause a kernel panic if GPIO registration fails, 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\npinctrl: bcm2835: Don't remove an unregistered GPIO chip\n\nIf the devm_pinctrl_register() function fails,\nbcm2835_pinctrl_probe() calls gpiochip_remove()\nbefore gpiochip_add_data() has registered the GPIO chip.\n\nThis means that upon failure the gpio_chip.gpiodev\n is NULL resulting in a null pointer dereference\ninside the gpiochip_remove() function.\n\nRemove the unnecessary function call to gpiochip_remove().\nNo GPIO cleanup is required because the GPIO chip\nhas not yet been registered. Without this change there\nis potential for a kernel panic upon registration failure","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":"pinctrl: bcm2835: Don't remove an unregistered GPIO chip","id":"CVE-2026-93274","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"perf/x86/intel/pt: Fix stop/start with no update","id":"CVE-2026-93275"},"packages":[],"prev":{"headline":"regulator: tps6594: Fix device node reference leaks in multiphase loop","id":"CVE-2026-93273"},"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 null pointer dereference in the BCM2835 pinctrl driver can cause a kernel panic if GPIO registration fails, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2026-93274/"}