{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90410 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90410 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-90410 and fix it if it is affected.\n\nWhat it is: CVE-2026-90410 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-90410 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-90410/ (Markdown: https://insights.sbomify.com/CVE-2026-90410/index.md)","id":"CVE-2026-90410","markdown":"https://insights.sbomify.com/CVE-2026-90410/index.md","name":"CVE-2026-90410","record":{"aliases":["AZL-102788","BELL-CVE-2026-90410","DEBIAN-CVE-2026-90410","GHSA-j436-5fx7-7xpm","UBUNTU-CVE-2026-90410"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A use-after-free vulnerability in the Linux kernel's Davinci SPI driver allows attackers to cause a denial of service or potentially execute code via race conditions during device removal.","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\nspi: davinci: switch to managed controller allocation\n\nThe controller is allocated with the non-managed spi_alloc_host() while\nthe interrupt is registered with devm_request_threaded_irq().  During\nremoval, spi_bitbang_stop() only unregisters the controller; the\nsubsequent spi_controller_put() then frees the controller together with\nits embedded davinci_spi devdata, which is the IRQ handler's dev_id.\nThe devm_request_threaded_irq() release action (free_irq()), which\ndrains the handler, does not run until after .remove() returns.  A late\nor latched interrupt can therefore reach davinci_spi_irq() and\ndereference already-freed memory.\n\nSwitch to devm_spi_alloc_host() so that the devres LIFO order releases\nthe controller only after free_irq() has drained the handler, and drop\nthe now-redundant spi_controller_put() from .remove().  The probe error\npath is simplified to direct returns.\n\nThe clock is acquired with devm_clk_get_enabled(), which is registered\nafter the IRQ and thus released before it by the devres LIFO order.\nDrain the interrupt explicitly with devm_free_irq() before disabling the\ncontroller so that a late interrupt cannot access the registers of a\nclock-gated controller.\n\nThis issue was found by an in-house static analysis tool.","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":"spi: davinci: switch to managed controller allocation","id":"CVE-2026-90410","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"nvme-fc: unmap cmd_iu DMA on rsp_iu mapping failure in init_request","id":"CVE-2026-90411"},"packages":[],"prev":{"headline":"drm/panthor: Add vm_bind region with kbo range overlap check","id":"CVE-2026-90409"},"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's Davinci SPI driver allows attackers to cause a denial of service or potentially execute code via race conditions during device removal.","url":"https://insights.sbomify.com/CVE-2026-90410/"}