{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89822 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89822 is a vulnerability in Linux, published on 16 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-89822 and fix it if it is affected.\n\nWhat it is: CVE-2026-89822 is a vulnerability in Linux, published on 16 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-89822 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-89822/ (Markdown: https://insights.sbomify.com/CVE-2026-89822/index.md)","id":"CVE-2026-89822","markdown":"https://insights.sbomify.com/CVE-2026-89822/index.md","name":"CVE-2026-89822","record":{"aliases":["AZL-101136","BELL-CVE-2026-89822","DEBIAN-CVE-2026-89822","GHSA-2c46-6532-v7c3","UBUNTU-CVE-2026-89822"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel driver","requires_auth":"high_privilege","summary":"A local attacker with high privileges can cause a kernel crash by force-binding a device, leading to a NULL pointer dereference in the i915 driver.","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\ndrm/i915: Guard against NULL driver_data in i915_pci_probe()\n\npci_match_device() can return the dummy pci_device_id_any entry\nwhen a device is force-bound via sysfs driver_override, in which\ncase -\u003edriver_data is unset (NULL). i915_pci_probe() casts it to\nstruct intel_device_info * unconditionally and dereferences\nintel_info-\u003erequire_force_probe, causing a NULL-ptr-deref.\n\n(cherry picked from commit 2727922084672cc274ecea726ea00363c2893731)","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":"drm/i915: Guard against NULL driver_data in i915_pci_probe()","id":"CVE-2026-89822","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"drm: fix race between partial drm_dev_register() failure and ioctl","id":"CVE-2026-89823"},"packages":[],"prev":{"headline":"drm/amd/display: avoid divide-by-zero in __is_lut_linear()","id":"CVE-2026-89821"},"products":["Linux"],"published":"2026-09-16","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 kernel crash by force-binding a device, leading to a NULL pointer dereference in the i915 driver.","url":"https://insights.sbomify.com/CVE-2026-89822/"}