<?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>Sun, 04 Oct 2026 08:18:47 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-81014</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-81014</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-81014</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1253 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Certaines d'entre elles permettent à un…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1253</link>
      <description>certfr-2026-avi-1253</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1253</guid>
    </item>
    <item>
      <title>EUVD-2026-367563</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-367563</link>
      <description>EUVD-2026-367563</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-367563</guid>
    </item>
    <item>
      <title>fkie_cve-2026-81014</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-81014</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;platform/x86: hp-bioscfg: fix heap OOB read in sk_store() and kek_store()&lt;/p&gt;
&lt;p&gt;sk_store() and kek_store() strip a trailing newline from the sysfs
write before allocating the key buffer:&lt;/p&gt;
&lt;p&gt;length = count;
	if (buf[length - 1] == &amp;#39;\n&amp;#39;)
		length--;
	bioscfg_drv.spm_data.signing_key = kmemdup(buf, length, GFP_KERNEL);&lt;/p&gt;
&lt;p&gt;but then pass the original &amp;#34;count&amp;#34; (not &amp;#34;length&amp;#34;) as the copy size to
hp_wmi_perform_query(), which memcpy()s that many bytes out of the
&amp;#34;length&amp;#34;-sized allocation, reading one byte past it whenever the write
ends in a newline, the normal case for a shell &amp;#34;echo&amp;#34; into sysfs.&lt;/p&gt;
&lt;p&gt;KASAN confirms this directly:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-out-of-bounds in hp_wmi_perform_query+0x1e9/0x460 [hp_bioscfg]
  Read of size 28 at addr ffff88813c8e2b80 by task python3/16022
  ...
  sk_store+0xa7/0x240 [hp_bioscfg]
  kernfs_fop_write_iter+0x3e1/0x5d0
  ...
  The buggy address is located 0 bytes inside of
  allocated 27-byte region [ffff88813c8e2b80, ffff88813c8e2b9b)&lt;/p&gt;
&lt;p&gt;Reproduced identically for kek_store, and at multiple write sizes
(28, 57, 201 bytes), each time reading exactly one byte past a
kmemdup() allocation one byte smaller than the write.&lt;/p&gt;
&lt;p&gt;Fix by passing &amp;#34;length&amp;#34; instead of &amp;#34;count&amp;#34; to hp_wmi_perform_query()
in both functions.&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;platform/x86: hp-bioscfg: fix heap OOB read in sk_store() and kek_store()&lt;/p&gt;
&lt;p&gt;sk_store() and kek_store() strip a trailing newline from the sysfs
write before allocating the key buffer:&lt;/p&gt;
&lt;p&gt;length = count;
	if (buf[length - 1] == &amp;#39;\n&amp;#39;)
		length--;
	bioscfg_drv.spm_data.signing_key = kmemdup(buf, length, GFP_KERNEL);&lt;/p&gt;
&lt;p&gt;but then pass the original &amp;#34;count&amp;#34; (not &amp;#34;length&amp;#34;) as the copy size to
hp_wmi_perform_query(), which memcpy()s that many bytes out of the
&amp;#34;length&amp;#34;-sized allocation, reading one byte past it whenever the write
ends in a newline, the normal case for a shell &amp;#34;echo&amp;#34; into sysfs.&lt;/p&gt;
&lt;p&gt;KASAN confirms this directly:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-out-of-bounds in hp_wmi_perform_query+0x1e9/0x460 [hp_bioscfg]
  Read of size 28 at addr ffff88813c8e2b80 by task python3/16022
  ...
  sk_store+0xa7/0x240 [hp_bioscfg]
  kernfs_fop_write_iter+0x3e1/0x5d0
  ...
  The buggy address is located 0 bytes inside of
  allocated 27-byte region [ffff88813c8e2b80, ffff88813c8e2b9b)&lt;/p&gt;
&lt;p&gt;Reproduced identically for kek_store, and at multiple write sizes
(28, 57, 201 bytes), each time reading exactly one byte past a
kmemdup() allocation one byte smaller than the write.&lt;/p&gt;
&lt;p&gt;Fix by passing &amp;#34;length&amp;#34; instead of &amp;#34;count&amp;#34; to hp_wmi_perform_query()
in both functions.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-81014</guid>
    </item>
    <item>
      <title>GHSA-rjrm-jj77-cvq6</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-rjrm-jj77-cvq6</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;platform/x86: hp-bioscfg: fix heap OOB read in sk_store() and kek_store()&lt;/p&gt;
&lt;p&gt;sk_store() and kek_store() strip a trailing newline from the sysfs
write before allocating the key buffer:&lt;/p&gt;
&lt;p&gt;length = count;
	if (buf[length - 1] == &amp;#39;\n&amp;#39;)
		length--;
	bioscfg_drv.spm_data.signing_key = kmemdup(buf, length, GFP_KERNEL);&lt;/p&gt;
&lt;p&gt;but then pass the original &amp;#34;count&amp;#34; (not &amp;#34;length&amp;#34;) as the copy size to
hp_wmi_perform_query(), which memcpy()s that many bytes out of the
&amp;#34;length&amp;#34;-sized allocation, reading one byte past it whenever the write
ends in a newline, the normal case for a shell &amp;#34;echo&amp;#34; into sysfs.&lt;/p&gt;
&lt;p&gt;KASAN confirms this directly:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-out-of-bounds in hp_wmi_perform_query+0x1e9/0x460 [hp_bioscfg]
  Read of size 28 at addr ffff88813c8e2b80 by task python3/16022
  ...
  sk_store+0xa7/0x240 [hp_bioscfg]
  kernfs_fop_write_iter+0x3e1/0x5d0
  ...
  The buggy address is located 0 bytes inside of
  allocated 27-byte region [ffff88813c8e2b80, ffff88813c8e2b9b)&lt;/p&gt;
&lt;p&gt;Reproduced identically for kek_store, and at multiple write sizes
(28, 57, 201 bytes), each time reading exactly one byte past a
kmemdup() allocation one byte smaller than the write.&lt;/p&gt;
&lt;p&gt;Fix by passing &amp;#34;length&amp;#34; instead of &amp;#34;count&amp;#34; to hp_wmi_perform_query()
in both functions.&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;platform/x86: hp-bioscfg: fix heap OOB read in sk_store() and kek_store()&lt;/p&gt;
&lt;p&gt;sk_store() and kek_store() strip a trailing newline from the sysfs
write before allocating the key buffer:&lt;/p&gt;
&lt;p&gt;length = count;
	if (buf[length - 1] == &amp;#39;\n&amp;#39;)
		length--;
	bioscfg_drv.spm_data.signing_key = kmemdup(buf, length, GFP_KERNEL);&lt;/p&gt;
&lt;p&gt;but then pass the original &amp;#34;count&amp;#34; (not &amp;#34;length&amp;#34;) as the copy size to
hp_wmi_perform_query(), which memcpy()s that many bytes out of the
&amp;#34;length&amp;#34;-sized allocation, reading one byte past it whenever the write
ends in a newline, the normal case for a shell &amp;#34;echo&amp;#34; into sysfs.&lt;/p&gt;
&lt;p&gt;KASAN confirms this directly:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-out-of-bounds in hp_wmi_perform_query+0x1e9/0x460 [hp_bioscfg]
  Read of size 28 at addr ffff88813c8e2b80 by task python3/16022
  ...
  sk_store+0xa7/0x240 [hp_bioscfg]
  kernfs_fop_write_iter+0x3e1/0x5d0
  ...
  The buggy address is located 0 bytes inside of
  allocated 27-byte region [ffff88813c8e2b80, ffff88813c8e2b9b)&lt;/p&gt;
&lt;p&gt;Reproduced identically for kek_store, and at multiple write sizes
(28, 57, 201 bytes), each time reading exactly one byte past a
kmemdup() allocation one byte smaller than the write.&lt;/p&gt;
&lt;p&gt;Fix by passing &amp;#34;length&amp;#34; instead of &amp;#34;count&amp;#34; to hp_wmi_perform_query()
in both functions.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-rjrm-jj77-cvq6</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-81014 — platform/x86: hp-bioscfg: fix heap OOB read in sk_store() and kek_store()</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-81014</link>
      <description>msrc_CVE-2026-81014</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-81014</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11805-1 — kernel-devel-7.2.6-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:11805-1</link>
      <description>&lt;p&gt;kernel-devel-7.2.6-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.2.6-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:11805-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-81014</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-81014</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 154 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: platform/x86: hp-bioscfg: fix heap OOB read in sk_store() and kek_store() sk_store() and kek_store() strip a trailing newline from the sysfs write before allocating the key buffer: 	length = count; 	if (buf[length - 1] == &amp;#39;\n&amp;#39;) 		length--; 	bioscfg_drv.spm_data.signing_key = kmemdup(buf, length, GFP_KERNEL); but then pass the original &amp;#34;count&amp;#34; (not &amp;#34;length&amp;#34;) as the copy size to hp_wmi_perform_query(), which memcpy()s that many bytes out of the &amp;#34;length&amp;#34;-sized allocation, reading one byte past it whenever the write ends in a newline, the normal case for a shell &amp;#34;echo&amp;#34; into sysfs. KASAN confirms this directly:   BUG: KASAN: slab-out-of-bounds in hp_wmi_perform_query+0x1e9/0x460 [hp_bioscfg]   Read of size 28 at addr ffff88813c8e2b80 by task python3/16022   ...   sk_store+0xa7/0x240 [hp_bioscfg]   kernfs_fop_write_iter+0x3e1/0x5d0   ...   The buggy address is located 0 bytes inside of   allocated 27-byte region [ffff88813c8e2b80, ffff88813c8e2b9b) Reproduced identically for kek_store, and at multiple write sizes (28, 57, 201 bytes), each time reading exactly one byte past a kmemdup() allocation one byte smaller than the write. Fix by passing &amp;#34;length&amp;#34; instead of &amp;#34;count&amp;#34; to hp_wmi_perform_query() in both functions.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 154 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: platform/x86: hp-bioscfg: fix heap OOB read in sk_store() and kek_store() sk_store() and kek_store() strip a trailing newline from the sysfs write before allocating the key buffer: 	length = count; 	if (buf[length - 1] == &amp;#39;\n&amp;#39;) 		length--; 	bioscfg_drv.spm_data.signing_key = kmemdup(buf, length, GFP_KERNEL); but then pass the original &amp;#34;count&amp;#34; (not &amp;#34;length&amp;#34;) as the copy size to hp_wmi_perform_query(), which memcpy()s that many bytes out of the &amp;#34;length&amp;#34;-sized allocation, reading one byte past it whenever the write ends in a newline, the normal case for a shell &amp;#34;echo&amp;#34; into sysfs. KASAN confirms this directly:   BUG: KASAN: slab-out-of-bounds in hp_wmi_perform_query+0x1e9/0x460 [hp_bioscfg]   Read of size 28 at addr ffff88813c8e2b80 by task python3/16022   ...   sk_store+0xa7/0x240 [hp_bioscfg]   kernfs_fop_write_iter+0x3e1/0x5d0   ...   The buggy address is located 0 bytes inside of   allocated 27-byte region [ffff88813c8e2b80, ffff88813c8e2b9b) Reproduced identically for kek_store, and at multiple write sizes (28, 57, 201 bytes), each time reading exactly one byte past a kmemdup() allocation one byte smaller than the write. Fix by passing &amp;#34;length&amp;#34; instead of &amp;#34;count&amp;#34; to hp_wmi_perform_query() in both functions.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-81014</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3321 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3321</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsmaßnahmen zu umgehen, Daten oder den Systemzustand zu manipulieren, Denial-of-Service-Zustände herbeizuführen oder andere, nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsmaßnahmen zu umgehen, Daten oder den Systemzustand zu manipulieren, Denial-of-Service-Zustände herbeizuführen oder andere, nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3321</guid>
    </item>
  </channel>
</rss>
