<?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://db.gcve.eu</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>Fri, 20 Nov 2026 21:30:33 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99558</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99558</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;blk-crypto: fix NULL deref and UAF in __blk_crypto_evict_key()&lt;/p&gt;
&lt;p&gt;Sashiko reported a possible NULL pointer dereference, triggered by the
following flow:&lt;/p&gt;
&lt;p&gt;dm-inlinecrypt ctor            # first use of the fallback
   ├─ blk_crypto_init_key()      # succeeds, ctx-&amp;gt;key.size != 0
   ├─ blk_crypto_start_using_key()
   │   ├─ hw-wrapped key: -EOPNOTSUPP
   │   │    # profile never allocated (NULL)
   │   └─ raw key: fallback_start_using_mode()
   │      └─ blk_crypto_fallback_init() fails
   │         └─ kfree(profile)   # not NULLed
   ├─ goto bad
   └─ inlinecrypt_dtr()          # evicts whenever key.size is set
      └─ blk_crypto_evict_key()
         └─ blk_crypto_config_supported_natively() = false
            └─ blk_crypto_fallback_evict_key()
               └─ __blk_crypto_evict_key(blk_crypto_fallback_profile)
                  └─ profile-&amp;gt;num_slots # BOOM!!!&lt;/p&gt;
&lt;p&gt;This issue can be reproduced using the following commands:&lt;/p&gt;
&lt;p&gt;dd if=/dev/zero of=/tmp/backing bs=1M count=64
  LOOP=$(losetup -f --show /tmp/backing)
  SZ=$(blockdev --getsz $LOOP)
  KEY=$(head -c 64 /dev/urandom | od -An -tx1 | tr -d &amp;#39; \n&amp;#39;)
  dmsetup create ic --table &amp;#34;0 $SZ inlinecrypt aes-xts-plain64 \
    $KEY 0 $LOOP 0 1 keytype:hw-wrapped&amp;#34;&lt;/p&gt;
&lt;p&gt;And the following oops is triggered:&lt;/p&gt;
&lt;p&gt;==================================================================
  blk-crypto: loop0: no support for wrapped keys
  Oops: general protection fault, probably for non…&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;blk-crypto: fix NULL deref and UAF in __blk_crypto_evict_key()&lt;/p&gt;
&lt;p&gt;Sashiko reported a possible NULL pointer dereference, triggered by the
following flow:&lt;/p&gt;
&lt;p&gt;dm-inlinecrypt ctor            # first use of the fallback
   ├─ blk_crypto_init_key()      # succeeds, ctx-&amp;gt;key.size != 0
   ├─ blk_crypto_start_using_key()
   │   ├─ hw-wrapped key: -EOPNOTSUPP
   │   │    # profile never allocated (NULL)
   │   └─ raw key: fallback_start_using_mode()
   │      └─ blk_crypto_fallback_init() fails
   │         └─ kfree(profile)   # not NULLed
   ├─ goto bad
   └─ inlinecrypt_dtr()          # evicts whenever key.size is set
      └─ blk_crypto_evict_key()
         └─ blk_crypto_config_supported_natively() = false
            └─ blk_crypto_fallback_evict_key()
               └─ __blk_crypto_evict_key(blk_crypto_fallback_profile)
                  └─ profile-&amp;gt;num_slots # BOOM!!!&lt;/p&gt;
&lt;p&gt;This issue can be reproduced using the following commands:&lt;/p&gt;
&lt;p&gt;dd if=/dev/zero of=/tmp/backing bs=1M count=64
  LOOP=$(losetup -f --show /tmp/backing)
  SZ=$(blockdev --getsz $LOOP)
  KEY=$(head -c 64 /dev/urandom | od -An -tx1 | tr -d &amp;#39; \n&amp;#39;)
  dmsetup create ic --table &amp;#34;0 $SZ inlinecrypt aes-xts-plain64 \
    $KEY 0 $LOOP 0 1 keytype:hw-wrapped&amp;#34;&lt;/p&gt;
&lt;p&gt;And the following oops is triggered:&lt;/p&gt;
&lt;p&gt;==================================================================
  blk-crypto: loop0: no support for wrapped keys
  Oops: general protection fault, probably for non…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99558</guid>
    </item>
    <item>
      <title>GHSA-953q-c43g-ch7x</title>
      <link>https://db.gcve.eu/vuln/ghsa-953q-c43g-ch7x</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;blk-crypto: fix NULL deref and UAF in __blk_crypto_evict_key()&lt;/p&gt;
&lt;p&gt;Sashiko reported a possible NULL pointer dereference, triggered by the
following flow:&lt;/p&gt;
&lt;p&gt;dm-inlinecrypt ctor            # first use of the fallback
   ├─ blk_crypto_init_key()      # succeeds, ctx-&amp;gt;key.size != 0
   ├─ blk_crypto_start_using_key()
   │   ├─ hw-wrapped key: -EOPNOTSUPP
   │   │    # profile never allocated (NULL)
   │   └─ raw key: fallback_start_using_mode()
   │      └─ blk_crypto_fallback_init() fails
   │         └─ kfree(profile)   # not NULLed
   ├─ goto bad
   └─ inlinecrypt_dtr()          # evicts whenever key.size is set
      └─ blk_crypto_evict_key()
         └─ blk_crypto_config_supported_natively() = false
            └─ blk_crypto_fallback_evict_key()
               └─ __blk_crypto_evict_key(blk_crypto_fallback_profile)
                  └─ profile-&amp;gt;num_slots # BOOM!!!&lt;/p&gt;
&lt;p&gt;This issue can be reproduced using the following commands:&lt;/p&gt;
&lt;p&gt;dd if=/dev/zero of=/tmp/backing bs=1M count=64
  LOOP=$(losetup -f --show /tmp/backing)
  SZ=$(blockdev --getsz $LOOP)
  KEY=$(head -c 64 /dev/urandom | od -An -tx1 | tr -d &amp;#39; \n&amp;#39;)
  dmsetup create ic --table &amp;#34;0 $SZ inlinecrypt aes-xts-plain64 \
    $KEY 0 $LOOP 0 1 keytype:hw-wrapped&amp;#34;&lt;/p&gt;
&lt;p&gt;And the following oops is triggered:&lt;/p&gt;
&lt;p&gt;==================================================================
  blk-crypto: loop0: no support for wrapped keys
  Oops: general protection fault, probably for non…&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;blk-crypto: fix NULL deref and UAF in __blk_crypto_evict_key()&lt;/p&gt;
&lt;p&gt;Sashiko reported a possible NULL pointer dereference, triggered by the
following flow:&lt;/p&gt;
&lt;p&gt;dm-inlinecrypt ctor            # first use of the fallback
   ├─ blk_crypto_init_key()      # succeeds, ctx-&amp;gt;key.size != 0
   ├─ blk_crypto_start_using_key()
   │   ├─ hw-wrapped key: -EOPNOTSUPP
   │   │    # profile never allocated (NULL)
   │   └─ raw key: fallback_start_using_mode()
   │      └─ blk_crypto_fallback_init() fails
   │         └─ kfree(profile)   # not NULLed
   ├─ goto bad
   └─ inlinecrypt_dtr()          # evicts whenever key.size is set
      └─ blk_crypto_evict_key()
         └─ blk_crypto_config_supported_natively() = false
            └─ blk_crypto_fallback_evict_key()
               └─ __blk_crypto_evict_key(blk_crypto_fallback_profile)
                  └─ profile-&amp;gt;num_slots # BOOM!!!&lt;/p&gt;
&lt;p&gt;This issue can be reproduced using the following commands:&lt;/p&gt;
&lt;p&gt;dd if=/dev/zero of=/tmp/backing bs=1M count=64
  LOOP=$(losetup -f --show /tmp/backing)
  SZ=$(blockdev --getsz $LOOP)
  KEY=$(head -c 64 /dev/urandom | od -An -tx1 | tr -d &amp;#39; \n&amp;#39;)
  dmsetup create ic --table &amp;#34;0 $SZ inlinecrypt aes-xts-plain64 \
    $KEY 0 $LOOP 0 1 keytype:hw-wrapped&amp;#34;&lt;/p&gt;
&lt;p&gt;And the following oops is triggered:&lt;/p&gt;
&lt;p&gt;==================================================================
  blk-crypto: loop0: no support for wrapped keys
  Oops: general protection fault, probably for non…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-953q-c43g-ch7x</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4695 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2026-4695</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/wid-sec-w-2026-4695</guid>
    </item>
  </channel>
</rss>
