{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93256 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93256 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-93256 and fix it if it is affected.\n\nWhat it is: CVE-2026-93256 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-93256 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-93256/ (Markdown: https://insights.sbomify.com/CVE-2026-93256/index.md)","id":"CVE-2026-93256","markdown":"https://insights.sbomify.com/CVE-2026-93256/index.md","name":"CVE-2026-93256","record":{"aliases":["BELL-CVE-2026-93256","DEBIAN-CVE-2026-93256","GHSA-jf3q-gp4f-qwvj","UBUNTU-CVE-2026-93256"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A flaw in Linux kernel arm64 hibernation resume allows fatal crashes or warnings due to improper exception masking, requiring local access to trigger.","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: hibernate: mask DAIF before restoring hibernated kernel\n\nThe arm64 hibernate code manages the exception masking in an unsound\nway, leading to potential crashes and/or warnings during resume.\n\nWhen a hibernation image is saved in `swsusp_arch_suspend()`, all DAIF\nexceptions are masked (by virtue of `local_daif_save()`), and the\nsuspended image is saved assuming that all DAIF exceptions will remain\nmasked when the image is restored.\n\nWhen a hibernation image is resumed by `swsusp_arch_resume()`, only\ninterrupts are masked (by virtue of `local_irq_disable()` in\n`resume_target_kernel()`). When pseudo-NMI is enabled the DAIF.IF bits\nwill be clear, and regardless of pseudo-NMI the DAIF.DA bits will be\nclear.\n\nThis means that there are two problems:\n\n(1) It is possible to take Debug, SError, or pseudo-NMI exceptions\n    during the resume process. This is unsafe, as during the resume\n    process both the old ane new kernels will tranisently be in an\n    inconsistent state, and swsusp_arch_suspend_exit() won't retain\n    an executable mapping of any exception vectors.\n\n    Any exception taken here will be fatal and silent.\n\n(2) When re-entering the resumed kernel, some DAIF bits will be clear\n    unexpectedly. This permits Debug, SError, or pseudo-NMI exceptions\n    to be taken for a short period while the resumed kernel is not yet\n    in a consistent state.\n\n    This is detected by CONFIG_ARM64_DEBUG_PRIORITY_MASKING.\n\nAvoid these issues by masking all DAIF exceptions during resume.","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: hibernate: mask DAIF before restoring hibernated kernel","id":"CVE-2026-93256","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"block: handle nogenerate/noverify properly in fs-integrity","id":"CVE-2026-93257"},"packages":[],"prev":{"headline":"btrfs: make sure EXTENT_BUFFER_READING is cleared under refs_lock","id":"CVE-2026-93255"},"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 flaw in Linux kernel arm64 hibernation resume allows fatal crashes or warnings due to improper exception masking, requiring local access to trigger.","url":"https://insights.sbomify.com/CVE-2026-93256/"}