{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-92521 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-92521 is an use after free vulnerability in Linux, published on 17 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-92521 and fix it if it is affected.\n\nWhat it is: CVE-2026-92521 is an use after free vulnerability in Linux, published on 17 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-92521 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-92521/ (Markdown: https://insights.sbomify.com/CVE-2026-92521/index.md)","id":"CVE-2026-92521","markdown":"https://insights.sbomify.com/CVE-2026-92521/index.md","name":"CVE-2026-92521","record":{"aliases":["AZL-102986","BELL-CVE-2026-92521","DEBIAN-CVE-2026-92521","GHSA-5pq6-vgcp-vv3f","UBUNTU-CVE-2026-92521"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A use-after-free vulnerability in the Linux kernel ACPI PCI subsystem allows local attackers to cause denial of service or potentially execute code via dangling pointers.","user_interaction":"not_required","vuln_class":"use_after_free"},"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\nACPI: PCI: Clear driver_data on all paths that free the acpi_pci_root\n\nacpi_pci_root_add() assigns the freshly allocated root to\ndevice-\u003edriver_data before dmar_device_add() and pci_acpi_scan_root().\nBoth failure paths reach the end: label where root is kfree()'d, but\nonly the pci_acpi_scan_root() path clears driver_data first.\n\nWhen dmar_device_add() fails during a hot-add, root is freed while\ndevice-\u003edriver_data still points at it.  The ACPI core does not clear\ndriver_data on attach failure, so a later acpi_pci_find_root() call may\ndereference this dangling pointer.\n\nacpi_pci_root_remove() has the same problem: it frees root without\nclearing device-\u003edriver_data, leaving a dangling pointer behind after\nthe root bridge is removed.\n\nMove the NULL assignment to the shared end: label so every error path in\nacpi_pci_root_add() clears driver_data before freeing root, and clear it\nin acpi_pci_root_remove() as well, so the object is never left reachable\nthrough driver_data after being freed.","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":"ACPI: PCI: Clear driver_data on all paths that free the acpi_pci_root","id":"CVE-2026-92521","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"ACPI: processor: validate MADT IOAPIC entry bounds","id":"CVE-2026-92522"},"packages":[],"prev":{"headline":"bpf: Zero queue and stack outputs on lock failure","id":"CVE-2026-92520"},"products":["Linux"],"published":"2026-09-17","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 use-after-free vulnerability in the Linux kernel ACPI PCI subsystem allows local attackers to cause denial of service or potentially execute code via dangling pointers.","url":"https://insights.sbomify.com/CVE-2026-92521/"}