CVE-2026-93256

CVE CVE-2026-93256EUVD EUVD-2026-86128Published 2026-09-24T15:51:43.000Z

What the advisory describes

In the Linux kernel, the following vulnerability has been resolved: arm64: hibernate: mask DAIF before restoring hibernated kernel The arm64 hibernate code manages the exception masking in an unsound way, leading to potential crashes and/or warnings during resume. When a hibernation image is saved in `swsusp_arch_suspend()`, all DAIF exceptions are masked (by virtue of `local_daif_save()`), and the suspended image is saved assuming that all DAIF exceptions will remain masked when the image is restored. When a hibernation image is resumed by `swsusp_arch_resume()`, only interrupts are masked (by virtue of `local_irq_disable()` in `resume_target_kernel()`). When pseudo-NMI is enabled the DAIF.IF bits will be clear, and regardless of pseudo-NMI the DAIF.DA bits will be clear. This means that there are two problems: (1) It is possible to take Debug, SError, or pseudo-NMI exceptions during the resume process. This is unsafe, as during the resume process both the old ane new kernels will tranisently be in an inconsistent state, and swsusp_arch_suspend_exit() won't retain an executable mapping of any exception vectors. Any exception taken here will be fatal and silent. (2) When re-entering the resumed kernel, some DAIF bits will be clear unexpectedly. This permits Debug, SError, or pseudo-NMI exceptions to be taken for a short period while the resumed kernel is not yet in a consistent state. This is detected by CONFIG_ARM64_DEBUG_PRIORITY_MASKING. Avoid these issues by masking all DAIF exceptions during resume.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

• Linux — Linux 82869ac57b5d3b550446932c918dbf2caf020c9e <684bde100117931f4c51c644a95f42f2dab041bc; patch: 6.1.188; 82869ac57b5d3b550446932c918dbf2caf020c9e <d736ace2c491623c9ab5e73744085e93e9ae3ebe; patch: 6.18.52; patch: 5.15.221; 4.7; 82869ac57b5d3b550446932c918dbf2caf020c9e <c9c671e9ab87b639720db8f7f8648bdf0f3bc8ec; patch: 7.3-rc1; 82869ac57b5d3b550446932c918dbf2caf020c9e <716c41bd476334afb943308be9ff2142e34461b7; 82869ac57b5d3b550446932c918dbf2caf020c9e <099ad3edcef1d955d9f5d6aab16ae78ecdfd4cda; patch: 7.2.6; 82869ac57b5d3b550446932c918dbf2caf020c9e <5370853041a3cb53a125b77528586278f64b378b; patch: 6.12.110; 82869ac57b5d3b550446932c918dbf2caf020c9e <012823494e20c3cce622982ebd3fd6971be39ad2; patch: 0; patch: 6.6.157; 82869ac57b5d3b550446932c918dbf2caf020c9e <290c5b0c9fc0c61fb1c41421ed2394f955206ea0; patch: 5.10.270

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

• Linux — Linux

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.