<?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>Mon, 28 Sep 2026 16:08:53 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-93256</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2026-93256</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bell-cve-2026-93256</guid>
    </item>
    <item>
      <title>fkie_cve-2026-93256</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-93256</link>
      <description>&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;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/fkie_cve-2026-93256</guid>
    </item>
    <item>
      <title>GHSA-jf3q-gp4f-qwvj</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-jf3q-gp4f-qwvj</link>
      <description>&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;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/ghsa-jf3q-gp4f-qwvj</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-93256</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-93256</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 246 more&lt;/p&gt;
&lt;p&gt;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&amp;#39;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…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 246 more&lt;/p&gt;
&lt;p&gt;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&amp;#39;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…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-93256</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3579 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://vulnerability.circl.lu/vuln/wid-sec-w-2026-3579</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand herbeizuführen oder nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand herbeizuführen oder nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/wid-sec-w-2026-3579</guid>
    </item>
  </channel>
</rss>
