<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 07:29:58 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-93256 — arm64: hibernate: mask DAIF before restoring hibernated kernel</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-93256</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;arm64: hibernate: mask DAIF before restoring hibernated kernel&lt;/p&gt;
&lt;p&gt;The arm64 hibernate code manages the exception masking in an unsound
way, leading to potential crashes and/or warnings during resume.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;This means that there are two problems:&lt;/p&gt;
&lt;p&gt;(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&amp;#39;t retain
    an executable mapping of any exception vectors.&lt;/p&gt;
&lt;p&gt;Any exception taken here will be fatal and silent.&lt;/p&gt;
&lt;p&gt;(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.&lt;/p&gt;
&lt;p&gt;This is detected by CONFIG_ARM64_DEBUG_PRIORIT…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;arm64: hibernate: mask DAIF before restoring hibernated kernel&lt;/p&gt;
&lt;p&gt;The arm64 hibernate code manages the exception masking in an unsound
way, leading to potential crashes and/or warnings during resume.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;This means that there are two problems:&lt;/p&gt;
&lt;p&gt;(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&amp;#39;t retain
    an executable mapping of any exception vectors.&lt;/p&gt;
&lt;p&gt;Any exception taken here will be fatal and silent.&lt;/p&gt;
&lt;p&gt;(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.&lt;/p&gt;
&lt;p&gt;This is detected by CONFIG_ARM64_DEBUG_PRIORIT…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-93256</guid>
    </item>
  </channel>
</rss>
