{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93815 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93815 is a denial of service 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-93815 and fix it if it is affected.\n\nWhat it is: CVE-2026-93815 is a denial of service 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-93815 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-93815/ (Markdown: https://insights.sbomify.com/CVE-2026-93815/index.md)","id":"CVE-2026-93815","markdown":"https://insights.sbomify.com/CVE-2026-93815/index.md","name":"CVE-2026-93815","record":{"aliases":["AZL-103595","BELL-CVE-2026-93815","DEBIAN-CVE-2026-93815","GHSA-xvh7-3cp2-m6qq","UBUNTU-CVE-2026-93815"],"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 sleeping function called in atomic context in the au1000 network driver can cause a kernel panic, leading to denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"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\nnet: au1000: move free_irq out of the close-time spinlocked section\n\nau1000_close() calls free_irq() while aup-\u003elock is still held with\nspin_lock_irqsave(). free_irq() can sleep because it takes the IRQ\ndescriptor request mutex, so it does not belong inside the close-time\nspinlocked section.\n\nThis was found by our static analysis tool and then confirmed by manual\nreview of the in-tree au1000_close() .ndo_stop path. The reviewed path\nkeeps aup-\u003elock held across the MAC reset, queue stop and\nfree_irq(dev-\u003eirq, dev).\n\nA directed runtime validation kept that ndo_stop carrier and the same\nfree_irq(dev-\u003eirq, dev) operation under the driver lock. Lockdep reported\n\"BUG: sleeping function called from invalid context\" and \"Invalid wait\ncontext\" while free_irq() was taking desc-\u003erequest_mutex, with\nau1000_close() and free_irq() on the stack.\n\nDrop aup-\u003elock before freeing the IRQ. The protected close-time work still\nstops the device and queue before IRQ teardown, but the sleepable IRQ core\npath now runs outside the spinlocked section.","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":"net: au1000: move free_irq out of the close-time spinlocked section","id":"CVE-2026-93815","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"f2fs: validate inline dentry name lengths before conversion","id":"CVE-2026-93816"},"packages":[],"prev":{"headline":"spi: core: Abort active target transfer on controller suspend","id":"CVE-2026-93814"},"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-03","vendors":["Linux"]},"summary":"A sleeping function called in atomic context in the au1000 network driver can cause a kernel panic, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2026-93815/"}