<?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>Fri, 02 Oct 2026 10:55:53 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-11727</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-11727</link>
      <description>bdu:2026-11727</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-11727</guid>
    </item>
    <item>
      <title>BELL-CVE-2026-43266</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-43266</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-43266</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0696 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0696</link>
      <description>certfr-2026-avi-0696</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0696</guid>
    </item>
    <item>
      <title>EUVD-2026-315846</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-315846</link>
      <description>EUVD-2026-315846</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-315846</guid>
    </item>
    <item>
      <title>fkie_cve-2026-43266</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-43266</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;EFI/CPER: don&amp;#39;t go past the ARM processor CPER record buffer&lt;/p&gt;
&lt;p&gt;There&amp;#39;s a logic inside GHES/CPER to detect if the section_length
is too small, but it doesn&amp;#39;t detect if it is too big.&lt;/p&gt;
&lt;p&gt;Currently, if the firmware receives an ARM processor CPER record
stating that a section length is big, kernel will blindly trust
section_length, producing a very long dump. For instance, a 67
bytes record with ERR_INFO_NUM set 46198 and section length
set to 854918320 would dump a lot of data going a way past the
firmware memory-mapped area.&lt;/p&gt;
&lt;p&gt;Fix it by adding a logic to prevent it to go past the buffer
if ERR_INFO_NUM is too big, making it report instead:&lt;/p&gt;
&lt;p&gt;[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1
	[Hardware Error]: event severity: recoverable
	[Hardware Error]:  Error 0, type: recoverable
	[Hardware Error]:   section_type: ARM processor error
	[Hardware Error]:   MIDR: 0xff304b2f8476870a
	[Hardware Error]:   section length: 854918320, CPER size: 67
	[Hardware Error]:   section length is too big
	[Hardware Error]:   firmware-generated error record is incorrect
	[Hardware Error]:   ERR_INFO_NUM is 46198&lt;/p&gt;
&lt;p&gt;[ rjw: Subject and changelog tweaks ]&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;EFI/CPER: don&amp;#39;t go past the ARM processor CPER record buffer&lt;/p&gt;
&lt;p&gt;There&amp;#39;s a logic inside GHES/CPER to detect if the section_length
is too small, but it doesn&amp;#39;t detect if it is too big.&lt;/p&gt;
&lt;p&gt;Currently, if the firmware receives an ARM processor CPER record
stating that a section length is big, kernel will blindly trust
section_length, producing a very long dump. For instance, a 67
bytes record with ERR_INFO_NUM set 46198 and section length
set to 854918320 would dump a lot of data going a way past the
firmware memory-mapped area.&lt;/p&gt;
&lt;p&gt;Fix it by adding a logic to prevent it to go past the buffer
if ERR_INFO_NUM is too big, making it report instead:&lt;/p&gt;
&lt;p&gt;[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1
	[Hardware Error]: event severity: recoverable
	[Hardware Error]:  Error 0, type: recoverable
	[Hardware Error]:   section_type: ARM processor error
	[Hardware Error]:   MIDR: 0xff304b2f8476870a
	[Hardware Error]:   section length: 854918320, CPER size: 67
	[Hardware Error]:   section length is too big
	[Hardware Error]:   firmware-generated error record is incorrect
	[Hardware Error]:   ERR_INFO_NUM is 46198&lt;/p&gt;
&lt;p&gt;[ rjw: Subject and changelog tweaks ]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-43266</guid>
    </item>
    <item>
      <title>GHSA-r9ph-9m45-xj6w</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-r9ph-9m45-xj6w</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;EFI/CPER: don&amp;#39;t go past the ARM processor CPER record buffer&lt;/p&gt;
&lt;p&gt;There&amp;#39;s a logic inside GHES/CPER to detect if the section_length
is too small, but it doesn&amp;#39;t detect if it is too big.&lt;/p&gt;
&lt;p&gt;Currently, if the firmware receives an ARM processor CPER record
stating that a section length is big, kernel will blindly trust
section_length, producing a very long dump. For instance, a 67
bytes record with ERR_INFO_NUM set 46198 and section length
set to 854918320 would dump a lot of data going a way past the
firmware memory-mapped area.&lt;/p&gt;
&lt;p&gt;Fix it by adding a logic to prevent it to go past the buffer
if ERR_INFO_NUM is too big, making it report instead:&lt;/p&gt;
&lt;p&gt;[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1
	[Hardware Error]: event severity: recoverable
	[Hardware Error]:  Error 0, type: recoverable
	[Hardware Error]:   section_type: ARM processor error
	[Hardware Error]:   MIDR: 0xff304b2f8476870a
	[Hardware Error]:   section length: 854918320, CPER size: 67
	[Hardware Error]:   section length is too big
	[Hardware Error]:   firmware-generated error record is incorrect
	[Hardware Error]:   ERR_INFO_NUM is 46198&lt;/p&gt;
&lt;p&gt;[ rjw: Subject and changelog tweaks ]&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;EFI/CPER: don&amp;#39;t go past the ARM processor CPER record buffer&lt;/p&gt;
&lt;p&gt;There&amp;#39;s a logic inside GHES/CPER to detect if the section_length
is too small, but it doesn&amp;#39;t detect if it is too big.&lt;/p&gt;
&lt;p&gt;Currently, if the firmware receives an ARM processor CPER record
stating that a section length is big, kernel will blindly trust
section_length, producing a very long dump. For instance, a 67
bytes record with ERR_INFO_NUM set 46198 and section length
set to 854918320 would dump a lot of data going a way past the
firmware memory-mapped area.&lt;/p&gt;
&lt;p&gt;Fix it by adding a logic to prevent it to go past the buffer
if ERR_INFO_NUM is too big, making it report instead:&lt;/p&gt;
&lt;p&gt;[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1
	[Hardware Error]: event severity: recoverable
	[Hardware Error]:  Error 0, type: recoverable
	[Hardware Error]:   section_type: ARM processor error
	[Hardware Error]:   MIDR: 0xff304b2f8476870a
	[Hardware Error]:   section length: 854918320, CPER size: 67
	[Hardware Error]:   section length is too big
	[Hardware Error]:   firmware-generated error record is incorrect
	[Hardware Error]:   ERR_INFO_NUM is 46198&lt;/p&gt;
&lt;p&gt;[ rjw: Subject and changelog tweaks ]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-r9ph-9m45-xj6w</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:21555-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:21555-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:21555-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:23066-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:23066-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:23066-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-43266</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-43266</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 232 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: EFI/CPER: don&amp;#39;t go past the ARM processor CPER record buffer There&amp;#39;s a logic inside GHES/CPER to detect if the section_length is too small, but it doesn&amp;#39;t detect if it is too big. Currently, if the firmware receives an ARM processor CPER record stating that a section length is big, kernel will blindly trust section_length, producing a very long dump. For instance, a 67 bytes record with ERR_INFO_NUM set 46198 and section length set to 854918320 would dump a lot of data going a way past the firmware memory-mapped area. Fix it by adding a logic to prevent it to go past the buffer if ERR_INFO_NUM is too big, making it report instead: 	[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1 	[Hardware Error]: event severity: recoverable 	[Hardware Error]:  Error 0, type: recoverable 	[Hardware Error]:   section_type: ARM processor error 	[Hardware Error]:   MIDR: 0xff304b2f8476870a 	[Hardware Error]:   section length: 854918320, CPER size: 67 	[Hardware Error]:   section length is too big 	[Hardware Error]:   firmware-generated error record is incorrect 	[Hardware Error]:   ERR_INFO_NUM is 46198 [ rjw: Subject and changelog tweaks ]&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 232 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: EFI/CPER: don&amp;#39;t go past the ARM processor CPER record buffer There&amp;#39;s a logic inside GHES/CPER to detect if the section_length is too small, but it doesn&amp;#39;t detect if it is too big. Currently, if the firmware receives an ARM processor CPER record stating that a section length is big, kernel will blindly trust section_length, producing a very long dump. For instance, a 67 bytes record with ERR_INFO_NUM set 46198 and section length set to 854918320 would dump a lot of data going a way past the firmware memory-mapped area. Fix it by adding a logic to prevent it to go past the buffer if ERR_INFO_NUM is too big, making it report instead: 	[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1 	[Hardware Error]: event severity: recoverable 	[Hardware Error]:  Error 0, type: recoverable 	[Hardware Error]:   section_type: ARM processor error 	[Hardware Error]:   MIDR: 0xff304b2f8476870a 	[Hardware Error]:   section length: 854918320, CPER size: 67 	[Hardware Error]:   section length is too big 	[Hardware Error]:   firmware-generated error record is incorrect 	[Hardware Error]:   ERR_INFO_NUM is 46198 [ rjw: Subject and changelog tweaks ]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-43266</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-1405 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1405</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht spezifizierte Angriffe durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren oder offenzulegen oder einen Denial-of-Service-Zustand zu verursachen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht spezifizierte Angriffe durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren oder offenzulegen oder einen Denial-of-Service-Zustand zu verursachen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1405</guid>
    </item>
  </channel>
</rss>
