<?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://cve.radiocsirt.org</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>Sat, 03 Oct 2026 19:05:57 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-43088</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-43088</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://cve.radiocsirt.org/vuln/bell-cve-2026-43088</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0637 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0637</link>
      <description>certfr-2026-avi-0637</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0637</guid>
    </item>
    <item>
      <title>EUVD-2026-367480</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-367480</link>
      <description>EUVD-2026-367480</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-367480</guid>
    </item>
    <item>
      <title>fkie_cve-2026-43088</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-43088</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: af_key: zero aligned sockaddr tail in PF_KEY exports&lt;/p&gt;
&lt;p&gt;PF_KEY export paths use `pfkey_sockaddr_size()` when reserving sockaddr
payload space, so IPv6 addresses occupy 32 bytes on the wire. However,
`pfkey_sockaddr_fill()` initializes only the first 28 bytes of
`struct sockaddr_in6`, leaving the final 4 aligned bytes uninitialized.&lt;/p&gt;
&lt;p&gt;Not every PF_KEY message is affected. The state and policy dump builders
already zero the whole message buffer before filling the sockaddr
payloads. Keep the fix to the export paths that still append aligned
sockaddr payloads with plain `skb_put()`:&lt;/p&gt;
&lt;p&gt;- `SADB_ACQUIRE`
  - `SADB_X_NAT_T_NEW_MAPPING`
  - `SADB_X_MIGRATE`&lt;/p&gt;
&lt;p&gt;Fix those paths by clearing only the aligned sockaddr tail after
`pfkey_sockaddr_fill()`.&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;net: af_key: zero aligned sockaddr tail in PF_KEY exports&lt;/p&gt;
&lt;p&gt;PF_KEY export paths use `pfkey_sockaddr_size()` when reserving sockaddr
payload space, so IPv6 addresses occupy 32 bytes on the wire. However,
`pfkey_sockaddr_fill()` initializes only the first 28 bytes of
`struct sockaddr_in6`, leaving the final 4 aligned bytes uninitialized.&lt;/p&gt;
&lt;p&gt;Not every PF_KEY message is affected. The state and policy dump builders
already zero the whole message buffer before filling the sockaddr
payloads. Keep the fix to the export paths that still append aligned
sockaddr payloads with plain `skb_put()`:&lt;/p&gt;
&lt;p&gt;- `SADB_ACQUIRE`
  - `SADB_X_NAT_T_NEW_MAPPING`
  - `SADB_X_MIGRATE`&lt;/p&gt;
&lt;p&gt;Fix those paths by clearing only the aligned sockaddr tail after
`pfkey_sockaddr_fill()`.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-43088</guid>
    </item>
    <item>
      <title>GHSA-5858-6g3v-6hmr</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-5858-6g3v-6hmr</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: af_key: zero aligned sockaddr tail in PF_KEY exports&lt;/p&gt;
&lt;p&gt;PF_KEY export paths use `pfkey_sockaddr_size()` when reserving sockaddr
payload space, so IPv6 addresses occupy 32 bytes on the wire. However,
`pfkey_sockaddr_fill()` initializes only the first 28 bytes of
`struct sockaddr_in6`, leaving the final 4 aligned bytes uninitialized.&lt;/p&gt;
&lt;p&gt;Not every PF_KEY message is affected. The state and policy dump builders
already zero the whole message buffer before filling the sockaddr
payloads. Keep the fix to the export paths that still append aligned
sockaddr payloads with plain `skb_put()`:&lt;/p&gt;
&lt;p&gt;- `SADB_ACQUIRE`
  - `SADB_X_NAT_T_NEW_MAPPING`
  - `SADB_X_MIGRATE`&lt;/p&gt;
&lt;p&gt;Fix those paths by clearing only the aligned sockaddr tail after
`pfkey_sockaddr_fill()`.&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;net: af_key: zero aligned sockaddr tail in PF_KEY exports&lt;/p&gt;
&lt;p&gt;PF_KEY export paths use `pfkey_sockaddr_size()` when reserving sockaddr
payload space, so IPv6 addresses occupy 32 bytes on the wire. However,
`pfkey_sockaddr_fill()` initializes only the first 28 bytes of
`struct sockaddr_in6`, leaving the final 4 aligned bytes uninitialized.&lt;/p&gt;
&lt;p&gt;Not every PF_KEY message is affected. The state and policy dump builders
already zero the whole message buffer before filling the sockaddr
payloads. Keep the fix to the export paths that still append aligned
sockaddr payloads with plain `skb_put()`:&lt;/p&gt;
&lt;p&gt;- `SADB_ACQUIRE`
  - `SADB_X_NAT_T_NEW_MAPPING`
  - `SADB_X_MIGRATE`&lt;/p&gt;
&lt;p&gt;Fix those paths by clearing only the aligned sockaddr tail after
`pfkey_sockaddr_fill()`.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-5858-6g3v-6hmr</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-43088 — net: af_key: zero aligned sockaddr tail in PF_KEY exports</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-43088</link>
      <description>msrc_CVE-2026-43088</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-43088</guid>
    </item>
    <item>
      <title>OESA-2026-2675 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2026-2675</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/i915/gt: Fix timeline left held on VMA alloc error&lt;/p&gt;
&lt;p&gt;The following error has been reported sporadically by CI when a test
unbinds the i915 driver on a ring submission platform:&lt;/p&gt;
&lt;p&gt;&amp;amp;lt;4&amp;amp;gt; [239.330153] ------------[ cut here ]------------
&amp;amp;lt;4&amp;amp;gt; [239.330166] i915 0000:00:02.0: [drm] drm_WARN_ON(dev_priv-&amp;amp;gt;mm.shrink_count)
&amp;amp;lt;4&amp;amp;gt; [239.330196] WARNING: CPU: 1 PID: 18570 at drivers/gpu/drm/i915/i915_gem.c:1309 i915_gem_cleanup_early+0x13e/0x150 [i915]
...
&amp;amp;lt;4&amp;amp;gt; [239.330640] RIP: 0010:i915_gem_cleanup_early+0x13e/0x150 [i915]
...
&amp;amp;lt;4&amp;amp;gt; [239.330942] Call Trace:
&amp;amp;lt;4&amp;amp;gt; [239.330944]  &amp;amp;lt;TASK&amp;amp;gt;
&amp;amp;lt;4&amp;amp;gt; [239.330949]  i915_driver_late_release+0x2b/0xa0 [i915]
&amp;amp;lt;4&amp;amp;gt; [239.331202]  i915_driver_release+0x86/0xa0 [i915]
&amp;amp;lt;4&amp;amp;gt; [239.331482]  devm_drm_dev_init_release+0x61/0x90
&amp;amp;lt;4&amp;amp;gt; [239.331494]  devm_action_release+0x15/0x30
&amp;amp;lt;4&amp;amp;gt; [239.331504]  release_nodes+0x3d/0x120
&amp;amp;lt;4&amp;amp;gt; [239.331517]  devres_release_all+0x96/0xd0
&amp;amp;lt;4&amp;amp;gt; [239.331533]  device_unbind_cleanup+0x12/0x80
&amp;amp;lt;4&amp;amp;gt; [239.331543]  device_release_driver_internal+0x23a/0x280
&amp;amp;lt;4&amp;amp;gt; [239.331550]  ? bus_find_device+0xa5/0xe0
&amp;amp;lt;4&amp;amp;gt; [239.331563]  device_driver_detach+0x14/0x20
...
&amp;amp;lt;4&amp;amp;gt; [357.719679] ---[ end trace 0000000000000000 ]---&lt;/p&gt;
&lt;p&gt;If the test also unloads the i915 module then that&amp;amp;apos;s followed with:&lt;/p&gt;
&lt;p&gt;&amp;amp;lt;3&amp;amp;gt; [357.787478] ===…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/i915/gt: Fix timeline left held on VMA alloc error&lt;/p&gt;
&lt;p&gt;The following error has been reported sporadically by CI when a test
unbinds the i915 driver on a ring submission platform:&lt;/p&gt;
&lt;p&gt;&amp;amp;lt;4&amp;amp;gt; [239.330153] ------------[ cut here ]------------
&amp;amp;lt;4&amp;amp;gt; [239.330166] i915 0000:00:02.0: [drm] drm_WARN_ON(dev_priv-&amp;amp;gt;mm.shrink_count)
&amp;amp;lt;4&amp;amp;gt; [239.330196] WARNING: CPU: 1 PID: 18570 at drivers/gpu/drm/i915/i915_gem.c:1309 i915_gem_cleanup_early+0x13e/0x150 [i915]
...
&amp;amp;lt;4&amp;amp;gt; [239.330640] RIP: 0010:i915_gem_cleanup_early+0x13e/0x150 [i915]
...
&amp;amp;lt;4&amp;amp;gt; [239.330942] Call Trace:
&amp;amp;lt;4&amp;amp;gt; [239.330944]  &amp;amp;lt;TASK&amp;amp;gt;
&amp;amp;lt;4&amp;amp;gt; [239.330949]  i915_driver_late_release+0x2b/0xa0 [i915]
&amp;amp;lt;4&amp;amp;gt; [239.331202]  i915_driver_release+0x86/0xa0 [i915]
&amp;amp;lt;4&amp;amp;gt; [239.331482]  devm_drm_dev_init_release+0x61/0x90
&amp;amp;lt;4&amp;amp;gt; [239.331494]  devm_action_release+0x15/0x30
&amp;amp;lt;4&amp;amp;gt; [239.331504]  release_nodes+0x3d/0x120
&amp;amp;lt;4&amp;amp;gt; [239.331517]  devres_release_all+0x96/0xd0
&amp;amp;lt;4&amp;amp;gt; [239.331533]  device_unbind_cleanup+0x12/0x80
&amp;amp;lt;4&amp;amp;gt; [239.331543]  device_release_driver_internal+0x23a/0x280
&amp;amp;lt;4&amp;amp;gt; [239.331550]  ? bus_find_device+0xa5/0xe0
&amp;amp;lt;4&amp;amp;gt; [239.331563]  device_driver_detach+0x14/0x20
...
&amp;amp;lt;4&amp;amp;gt; [357.719679] ---[ end trace 0000000000000000 ]---&lt;/p&gt;
&lt;p&gt;If the test also unloads the i915 module then that&amp;amp;apos;s followed with:&lt;/p&gt;
&lt;p&gt;&amp;amp;lt;3&amp;amp;gt; [357.787478] ===…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2026-2675</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:20826-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:20826-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:20826-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:2068-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:2068-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2026:2068-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-43088</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-43088</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 233 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: af_key: zero aligned sockaddr tail in PF_KEY exports PF_KEY export paths use `pfkey_sockaddr_size()` when reserving sockaddr payload space, so IPv6 addresses occupy 32 bytes on the wire. However, `pfkey_sockaddr_fill()` initializes only the first 28 bytes of `struct sockaddr_in6`, leaving the final 4 aligned bytes uninitialized. Not every PF_KEY message is affected. The state and policy dump builders already zero the whole message buffer before filling the sockaddr payloads. Keep the fix to the export paths that still append aligned sockaddr payloads with plain `skb_put()`:   - `SADB_ACQUIRE`   - `SADB_X_NAT_T_NEW_MAPPING`   - `SADB_X_MIGRATE` Fix those paths by clearing only the aligned sockaddr tail after `pfkey_sockaddr_fill()`.&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 233 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: af_key: zero aligned sockaddr tail in PF_KEY exports PF_KEY export paths use `pfkey_sockaddr_size()` when reserving sockaddr payload space, so IPv6 addresses occupy 32 bytes on the wire. However, `pfkey_sockaddr_fill()` initializes only the first 28 bytes of `struct sockaddr_in6`, leaving the final 4 aligned bytes uninitialized. Not every PF_KEY message is affected. The state and policy dump builders already zero the whole message buffer before filling the sockaddr payloads. Keep the fix to the export paths that still append aligned sockaddr payloads with plain `skb_put()`:   - `SADB_ACQUIRE`   - `SADB_X_NAT_T_NEW_MAPPING`   - `SADB_X_MIGRATE` Fix those paths by clearing only the aligned sockaddr tail after `pfkey_sockaddr_fill()`.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-43088</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-1385 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1385</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service zu verursachen, Informationen offenzulegen, Sicherheitsmaßnahmen zu umgehen oder potentiell beliebigen Programmcode auszufü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 zu verursachen, Informationen offenzulegen, Sicherheitsmaßnahmen zu umgehen oder potentiell beliebigen Programmcode auszuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1385</guid>
    </item>
  </channel>
</rss>
