{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93254 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93254 is a denial of service vulnerability in Linux, published on 24 Sep 2026."},"fix_prompt":"Check this codebase for CVE-2026-93254 and fix it if it is affected.\n\nWhat it is: CVE-2026-93254 is a denial of service vulnerability in Linux, published on 24 Sep 2026. \nExploitation: There is no known exploitation of CVE-2026-93254 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-93254/ (Markdown: https://insights.sbomify.com/CVE-2026-93254/index.md)","id":"CVE-2026-93254","markdown":"https://insights.sbomify.com/CVE-2026-93254/index.md","name":"CVE-2026-93254","record":{"aliases":["DEBIAN-CVE-2026-93254","GHSA-fh67-pc46-97cw","UBUNTU-CVE-2026-93254"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"unknown","non_default_config":true,"product_category":"Linux kernel","requires_auth":"none","summary":"A logic error in the Linux kernel arm64 entry path causes unnecessary IRQ disabling and potential warnings, potentially leading to system instability or 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\narm64: entry: Avoid unnecessary local_irq_disable() on kernel exit\n\nCurrently, when exiting to kernel mode, we attempt involuntary\npreemption. The preemption logic expects IRQs to be disabled, which is\nwhy we call local_irq_disable() before attempting preemption.\n\nHowever, depending on the context, local_irq_disable() may be\nunnecessary:\n\n- __el1_irq(), the non-NMI EL1 IRQ path, already has IRQs disabled, so\n  local_irq_disable() is redundant.\n\n- irqentry_exit_to_kernel_mode_preempt() immediately returns when\n  exiting from an NMI-like context, so calling local_irq_disable()\n  beforehand is unnecessary work.\n\nFurthermore, it confuses the pNMI state tracking when we are in a\ncontext with interrupts disabled and the GIC_PRIO_PSR_I_SET bit is set\nin the PMR, leading to a warning when\nCONFIG_ARM64_DEBUG_PRIORITY_MASKING=y:\n\n     WARNING: ./arch/arm64/include/asm/irqflags.h:63 at arm64_exit_to_kernel_mode+0xb8/0xc0, CPU#40: retsnoop/31805\n     CPU: 40 UID: 0 PID: 31805 Comm: retsnoop Not tainted 7.2.0-rc6-next-20260805 #7 PREEMPTLAZY\n     pstate: 234013c9 (nzCv DAIF +PAN -UAO +TCO +DIT +SSBS BTYPE=--)\n     pc : arm64_exit_to_kernel_mode (arch/arm64/kernel/entry-common.c:63)\n     lr : el1_abort (arch/arm64/kernel/entry-common.c:323)\n     pmr: 000000f0\n     Call trace:\n      arm64_exit_to_kernel_mode (arch/arm64/kernel/entry-common.c:63) (P)\n      el1_abort (arch/arm64/kernel/entry-common.c:323)\n      el1h_64_sync_handler (arch/arm64/kernel/entry-common.c:449)\n      el1h_64_sync (arch/arm64/kernel/entry.S:589)\n      [...]\n\nSplit arm64_exit_to_kernel_mode() into preempt, non-preempt, and\ndispatch parts so that we can avoid this extra work where it is not\nneeded and avoid breaking the pNMI tracking logic.","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":"arm64: entry: Avoid unnecessary local_irq_disable() on kernel exit","id":"CVE-2026-93254","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"btrfs: make sure EXTENT_BUFFER_READING is cleared under refs_lock","id":"CVE-2026-93255"},"packages":[],"prev":{"headline":"sched/isolation: Defer freeing of cpumask memblock memory to initcall","id":"CVE-2026-93253"},"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 logic error in the Linux kernel arm64 entry path causes unnecessary IRQ disabling and potential warnings, potentially leading to system instability or denial of service.","url":"https://insights.sbomify.com/CVE-2026-93254/"}