<?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>Thu, 01 Oct 2026 10:12:27 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-64318</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2026-64318</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-64318</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0982 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Elles permettent à un attaquant de p…</title>
      <link>https://vulnerability.circl.lu/vuln/certfr-2026-avi-0982</link>
      <description>certfr-2026-avi-0982</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/certfr-2026-avi-0982</guid>
    </item>
    <item>
      <title>fkie_cve-2026-64318</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-64318</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;partitions: aix: bound the pp_count scan to the ppe array&lt;/p&gt;
&lt;p&gt;aix_partition() reads the physical volume descriptor into a fixed-size
struct pvd and then scans its physical-partition-extent array:&lt;/p&gt;
&lt;p&gt;int numpps = be16_to_cpu(pvd-&amp;gt;pp_count);
	...
	for (i = 0; i &amp;lt; numpps; i += 1) {
		struct ppe *p = pvd-&amp;gt;ppe + i;
		...
		lp_ix = be16_to_cpu(p-&amp;gt;lp_ix);&lt;/p&gt;
&lt;p&gt;pvd points at a single kmalloc()&amp;#39;d struct pvd whose ppe[] member holds a
fixed ARRAY_SIZE(pvd-&amp;gt;ppe) (1016) entries, but the loop runs up to the
on-disk pp_count.  pp_count is an unvalidated __be16 read straight from
the descriptor, so a crafted AIX image with pp_count larger than 1016
drives the loop to read pvd-&amp;gt;ppe[i] past the end of the allocation (up
to 65535 entries, ~2 MB out of bounds).&lt;/p&gt;
&lt;p&gt;The partition scan runs without mounting anything, when a block device
with a crafted AIX/IBM partition table appears (an attacker-supplied
image attached with losetup -P, or a device auto-scanned by udev), via
msdos_partition() -&amp;gt; aix_partition().&lt;/p&gt;
&lt;p&gt;Clamp the scan to the number of entries the ppe[] array can hold.&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;partitions: aix: bound the pp_count scan to the ppe array&lt;/p&gt;
&lt;p&gt;aix_partition() reads the physical volume descriptor into a fixed-size
struct pvd and then scans its physical-partition-extent array:&lt;/p&gt;
&lt;p&gt;int numpps = be16_to_cpu(pvd-&amp;gt;pp_count);
	...
	for (i = 0; i &amp;lt; numpps; i += 1) {
		struct ppe *p = pvd-&amp;gt;ppe + i;
		...
		lp_ix = be16_to_cpu(p-&amp;gt;lp_ix);&lt;/p&gt;
&lt;p&gt;pvd points at a single kmalloc()&amp;#39;d struct pvd whose ppe[] member holds a
fixed ARRAY_SIZE(pvd-&amp;gt;ppe) (1016) entries, but the loop runs up to the
on-disk pp_count.  pp_count is an unvalidated __be16 read straight from
the descriptor, so a crafted AIX image with pp_count larger than 1016
drives the loop to read pvd-&amp;gt;ppe[i] past the end of the allocation (up
to 65535 entries, ~2 MB out of bounds).&lt;/p&gt;
&lt;p&gt;The partition scan runs without mounting anything, when a block device
with a crafted AIX/IBM partition table appears (an attacker-supplied
image attached with losetup -P, or a device auto-scanned by udev), via
msdos_partition() -&amp;gt; aix_partition().&lt;/p&gt;
&lt;p&gt;Clamp the scan to the number of entries the ppe[] array can hold.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-64318</guid>
    </item>
    <item>
      <title>GHSA-499p-p84w-r6w8</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-499p-p84w-r6w8</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;partitions: aix: bound the pp_count scan to the ppe array&lt;/p&gt;
&lt;p&gt;aix_partition() reads the physical volume descriptor into a fixed-size
struct pvd and then scans its physical-partition-extent array:&lt;/p&gt;
&lt;p&gt;int numpps = be16_to_cpu(pvd-&amp;gt;pp_count);
	...
	for (i = 0; i &amp;lt; numpps; i += 1) {
		struct ppe *p = pvd-&amp;gt;ppe + i;
		...
		lp_ix = be16_to_cpu(p-&amp;gt;lp_ix);&lt;/p&gt;
&lt;p&gt;pvd points at a single kmalloc()&amp;#39;d struct pvd whose ppe[] member holds a
fixed ARRAY_SIZE(pvd-&amp;gt;ppe) (1016) entries, but the loop runs up to the
on-disk pp_count.  pp_count is an unvalidated __be16 read straight from
the descriptor, so a crafted AIX image with pp_count larger than 1016
drives the loop to read pvd-&amp;gt;ppe[i] past the end of the allocation (up
to 65535 entries, ~2 MB out of bounds).&lt;/p&gt;
&lt;p&gt;The partition scan runs without mounting anything, when a block device
with a crafted AIX/IBM partition table appears (an attacker-supplied
image attached with losetup -P, or a device auto-scanned by udev), via
msdos_partition() -&amp;gt; aix_partition().&lt;/p&gt;
&lt;p&gt;Clamp the scan to the number of entries the ppe[] array can hold.&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;partitions: aix: bound the pp_count scan to the ppe array&lt;/p&gt;
&lt;p&gt;aix_partition() reads the physical volume descriptor into a fixed-size
struct pvd and then scans its physical-partition-extent array:&lt;/p&gt;
&lt;p&gt;int numpps = be16_to_cpu(pvd-&amp;gt;pp_count);
	...
	for (i = 0; i &amp;lt; numpps; i += 1) {
		struct ppe *p = pvd-&amp;gt;ppe + i;
		...
		lp_ix = be16_to_cpu(p-&amp;gt;lp_ix);&lt;/p&gt;
&lt;p&gt;pvd points at a single kmalloc()&amp;#39;d struct pvd whose ppe[] member holds a
fixed ARRAY_SIZE(pvd-&amp;gt;ppe) (1016) entries, but the loop runs up to the
on-disk pp_count.  pp_count is an unvalidated __be16 read straight from
the descriptor, so a crafted AIX image with pp_count larger than 1016
drives the loop to read pvd-&amp;gt;ppe[i] past the end of the allocation (up
to 65535 entries, ~2 MB out of bounds).&lt;/p&gt;
&lt;p&gt;The partition scan runs without mounting anything, when a block device
with a crafted AIX/IBM partition table appears (an attacker-supplied
image attached with losetup -P, or a device auto-scanned by udev), via
msdos_partition() -&amp;gt; aix_partition().&lt;/p&gt;
&lt;p&gt;Clamp the scan to the number of entries the ppe[] array can hold.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-499p-p84w-r6w8</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-64318 — partitions: aix: bound the pp_count scan to the ppe array</title>
      <link>https://vulnerability.circl.lu/vuln/msrc_cve-2026-64318</link>
      <description>msrc_CVE-2026-64318</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/msrc_cve-2026-64318</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11476-1 — kernel-devel-7.1.7-1.1 on GA media</title>
      <link>https://vulnerability.circl.lu/vuln/opensuse-su-2026:11476-1</link>
      <description>&lt;p&gt;kernel-devel-7.1.7-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.1.7-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/opensuse-su-2026:11476-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-64318</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-64318</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: partitions: aix: bound the pp_count scan to the ppe array aix_partition() reads the physical volume descriptor into a fixed-size struct pvd and then scans its physical-partition-extent array: 	int numpps = be16_to_cpu(pvd-&amp;gt;pp_count); 	... 	for (i = 0; i &amp;lt; numpps; i += 1) { 		struct ppe *p = pvd-&amp;gt;ppe + i; 		... 		lp_ix = be16_to_cpu(p-&amp;gt;lp_ix); pvd points at a single kmalloc()&amp;#39;d struct pvd whose ppe[] member holds a fixed ARRAY_SIZE(pvd-&amp;gt;ppe) (1016) entries, but the loop runs up to the on-disk pp_count.  pp_count is an unvalidated __be16 read straight from the descriptor, so a crafted AIX image with pp_count larger than 1016 drives the loop to read pvd-&amp;gt;ppe[i] past the end of the allocation (up to 65535 entries, ~2 MB out of bounds). The partition scan runs without mounting anything, when a block device with a crafted AIX/IBM partition table appears (an attacker-supplied image attached with losetup -P, or a device auto-scanned by udev), via msdos_partition() -&amp;gt; aix_partition(). Clamp the scan to the number of entries the ppe[] array can hold.&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: partitions: aix: bound the pp_count scan to the ppe array aix_partition() reads the physical volume descriptor into a fixed-size struct pvd and then scans its physical-partition-extent array: 	int numpps = be16_to_cpu(pvd-&amp;gt;pp_count); 	... 	for (i = 0; i &amp;lt; numpps; i += 1) { 		struct ppe *p = pvd-&amp;gt;ppe + i; 		... 		lp_ix = be16_to_cpu(p-&amp;gt;lp_ix); pvd points at a single kmalloc()&amp;#39;d struct pvd whose ppe[] member holds a fixed ARRAY_SIZE(pvd-&amp;gt;ppe) (1016) entries, but the loop runs up to the on-disk pp_count.  pp_count is an unvalidated __be16 read straight from the descriptor, so a crafted AIX image with pp_count larger than 1016 drives the loop to read pvd-&amp;gt;ppe[i] past the end of the allocation (up to 65535 entries, ~2 MB out of bounds). The partition scan runs without mounting anything, when a block device with a crafted AIX/IBM partition table appears (an attacker-supplied image attached with losetup -P, or a device auto-scanned by udev), via msdos_partition() -&amp;gt; aix_partition(). Clamp the scan to the number of entries the ppe[] array can hold.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-64318</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2527 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2527</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, dazu können DoS-Angriffe, die Offenlegung von Informationen, die Beschädigung des Speichers oder die Umgehung von Sicherheitsmaßnahmen gehören.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, dazu können DoS-Angriffe, die Offenlegung von Informationen, die Beschädigung des Speichers oder die Umgehung von Sicherheitsmaßnahmen gehören.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2527</guid>
    </item>
  </channel>
</rss>
