<?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>Mon, 28 Sep 2026 15:46:51 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-98136</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-98136</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ntfs: bound $AttrDef table walk to the loaded table size&lt;/p&gt;
&lt;p&gt;ntfs_attr_find_in_attrdef() walks the in-memory $AttrDef table, but the
loop condition bounds only the start of each entry, not the whole entry:&lt;/p&gt;
&lt;p&gt;for (ad = vol-&amp;gt;attrdef; (u8 *)ad - (u8 *)vol-&amp;gt;attrdef &amp;lt;
			vol-&amp;gt;attrdef_size &amp;amp;&amp;amp; ad-&amp;gt;type; ++ad)&lt;/p&gt;
&lt;p&gt;struct attr_def is 160 bytes; the guard reads ad-&amp;gt;type at offset 128 and
the loop body reads further fields. vol-&amp;gt;attrdef is kvzalloc(i_size),
where i_size is the on-disk $AttrDef data size, checked in
load_and_init_attrdef() only as 0 &amp;lt; i_size &amp;lt;= 0x7fffffff. A volume whose
$AttrDef data size is smaller than one entry (e.g. 120 bytes) makes the
read of ad-&amp;gt;type run past the allocation. Creating a file reaches this
through ntfs_attr_size_bounds_check() and reads out of bounds:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-out-of-bounds in ntfs_attr_find_in_attrdef+0x66/0xa0
  Read of size 4 at addr ffff888005833280 by task init/1
   ntfs_attr_find_in_attrdef
   ntfs_attr_size_bounds_check
   ntfs_attr_can_be_non_resident
   ntfs_attr_add&lt;/p&gt;
&lt;p&gt;Require the whole entry to lie within attrdef_size in the loop guard, and
reject at mount a $AttrDef too small to hold one attr_def entry.&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;ntfs: bound $AttrDef table walk to the loaded table size&lt;/p&gt;
&lt;p&gt;ntfs_attr_find_in_attrdef() walks the in-memory $AttrDef table, but the
loop condition bounds only the start of each entry, not the whole entry:&lt;/p&gt;
&lt;p&gt;for (ad = vol-&amp;gt;attrdef; (u8 *)ad - (u8 *)vol-&amp;gt;attrdef &amp;lt;
			vol-&amp;gt;attrdef_size &amp;amp;&amp;amp; ad-&amp;gt;type; ++ad)&lt;/p&gt;
&lt;p&gt;struct attr_def is 160 bytes; the guard reads ad-&amp;gt;type at offset 128 and
the loop body reads further fields. vol-&amp;gt;attrdef is kvzalloc(i_size),
where i_size is the on-disk $AttrDef data size, checked in
load_and_init_attrdef() only as 0 &amp;lt; i_size &amp;lt;= 0x7fffffff. A volume whose
$AttrDef data size is smaller than one entry (e.g. 120 bytes) makes the
read of ad-&amp;gt;type run past the allocation. Creating a file reaches this
through ntfs_attr_size_bounds_check() and reads out of bounds:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-out-of-bounds in ntfs_attr_find_in_attrdef+0x66/0xa0
  Read of size 4 at addr ffff888005833280 by task init/1
   ntfs_attr_find_in_attrdef
   ntfs_attr_size_bounds_check
   ntfs_attr_can_be_non_resident
   ntfs_attr_add&lt;/p&gt;
&lt;p&gt;Require the whole entry to lie within attrdef_size in the loop guard, and
reject at mount a $AttrDef too small to hold one attr_def entry.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-98136</guid>
    </item>
    <item>
      <title>GHSA-v5r3-r9hr-q598</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-v5r3-r9hr-q598</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ntfs: bound $AttrDef table walk to the loaded table size&lt;/p&gt;
&lt;p&gt;ntfs_attr_find_in_attrdef() walks the in-memory $AttrDef table, but the
loop condition bounds only the start of each entry, not the whole entry:&lt;/p&gt;
&lt;p&gt;for (ad = vol-&amp;gt;attrdef; (u8 *)ad - (u8 *)vol-&amp;gt;attrdef &amp;lt;
			vol-&amp;gt;attrdef_size &amp;amp;&amp;amp; ad-&amp;gt;type; ++ad)&lt;/p&gt;
&lt;p&gt;struct attr_def is 160 bytes; the guard reads ad-&amp;gt;type at offset 128 and
the loop body reads further fields. vol-&amp;gt;attrdef is kvzalloc(i_size),
where i_size is the on-disk $AttrDef data size, checked in
load_and_init_attrdef() only as 0 &amp;lt; i_size &amp;lt;= 0x7fffffff. A volume whose
$AttrDef data size is smaller than one entry (e.g. 120 bytes) makes the
read of ad-&amp;gt;type run past the allocation. Creating a file reaches this
through ntfs_attr_size_bounds_check() and reads out of bounds:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-out-of-bounds in ntfs_attr_find_in_attrdef+0x66/0xa0
  Read of size 4 at addr ffff888005833280 by task init/1
   ntfs_attr_find_in_attrdef
   ntfs_attr_size_bounds_check
   ntfs_attr_can_be_non_resident
   ntfs_attr_add&lt;/p&gt;
&lt;p&gt;Require the whole entry to lie within attrdef_size in the loop guard, and
reject at mount a $AttrDef too small to hold one attr_def entry.&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;ntfs: bound $AttrDef table walk to the loaded table size&lt;/p&gt;
&lt;p&gt;ntfs_attr_find_in_attrdef() walks the in-memory $AttrDef table, but the
loop condition bounds only the start of each entry, not the whole entry:&lt;/p&gt;
&lt;p&gt;for (ad = vol-&amp;gt;attrdef; (u8 *)ad - (u8 *)vol-&amp;gt;attrdef &amp;lt;
			vol-&amp;gt;attrdef_size &amp;amp;&amp;amp; ad-&amp;gt;type; ++ad)&lt;/p&gt;
&lt;p&gt;struct attr_def is 160 bytes; the guard reads ad-&amp;gt;type at offset 128 and
the loop body reads further fields. vol-&amp;gt;attrdef is kvzalloc(i_size),
where i_size is the on-disk $AttrDef data size, checked in
load_and_init_attrdef() only as 0 &amp;lt; i_size &amp;lt;= 0x7fffffff. A volume whose
$AttrDef data size is smaller than one entry (e.g. 120 bytes) makes the
read of ad-&amp;gt;type run past the allocation. Creating a file reaches this
through ntfs_attr_size_bounds_check() and reads out of bounds:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-out-of-bounds in ntfs_attr_find_in_attrdef+0x66/0xa0
  Read of size 4 at addr ffff888005833280 by task init/1
   ntfs_attr_find_in_attrdef
   ntfs_attr_size_bounds_check
   ntfs_attr_can_be_non_resident
   ntfs_attr_add&lt;/p&gt;
&lt;p&gt;Require the whole entry to lie within attrdef_size in the loop guard, and
reject at mount a $AttrDef too small to hold one attr_def entry.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-v5r3-r9hr-q598</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98136</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-98136</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: ntfs: bound $AttrDef table walk to the loaded table size ntfs_attr_find_in_attrdef() walks the in-memory $AttrDef table, but the loop condition bounds only the start of each entry, not the whole entry: 	for (ad = vol-&amp;gt;attrdef; (u8 *)ad - (u8 *)vol-&amp;gt;attrdef &amp;lt; 			vol-&amp;gt;attrdef_size &amp;amp;&amp;amp; ad-&amp;gt;type; ++ad) struct attr_def is 160 bytes; the guard reads ad-&amp;gt;type at offset 128 and the loop body reads further fields. vol-&amp;gt;attrdef is kvzalloc(i_size), where i_size is the on-disk $AttrDef data size, checked in load_and_init_attrdef() only as 0 &amp;lt; i_size &amp;lt;= 0x7fffffff. A volume whose $AttrDef data size is smaller than one entry (e.g. 120 bytes) makes the read of ad-&amp;gt;type run past the allocation. Creating a file reaches this through ntfs_attr_size_bounds_check() and reads out of bounds:   BUG: KASAN: slab-out-of-bounds in ntfs_attr_find_in_attrdef+0x66/0xa0   Read of size 4 at addr ffff888005833280 by task init/1    ntfs_attr_find_in_attrdef    ntfs_attr_size_bounds_check    ntfs_attr_can_be_non_resident    ntfs_attr_add Require the whole entry to lie within attrdef_size in the loop guard, and reject at mount a $AttrDef too small to hold one attr_def entry.&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: ntfs: bound $AttrDef table walk to the loaded table size ntfs_attr_find_in_attrdef() walks the in-memory $AttrDef table, but the loop condition bounds only the start of each entry, not the whole entry: 	for (ad = vol-&amp;gt;attrdef; (u8 *)ad - (u8 *)vol-&amp;gt;attrdef &amp;lt; 			vol-&amp;gt;attrdef_size &amp;amp;&amp;amp; ad-&amp;gt;type; ++ad) struct attr_def is 160 bytes; the guard reads ad-&amp;gt;type at offset 128 and the loop body reads further fields. vol-&amp;gt;attrdef is kvzalloc(i_size), where i_size is the on-disk $AttrDef data size, checked in load_and_init_attrdef() only as 0 &amp;lt; i_size &amp;lt;= 0x7fffffff. A volume whose $AttrDef data size is smaller than one entry (e.g. 120 bytes) makes the read of ad-&amp;gt;type run past the allocation. Creating a file reaches this through ntfs_attr_size_bounds_check() and reads out of bounds:   BUG: KASAN: slab-out-of-bounds in ntfs_attr_find_in_attrdef+0x66/0xa0   Read of size 4 at addr ffff888005833280 by task init/1    ntfs_attr_find_in_attrdef    ntfs_attr_size_bounds_check    ntfs_attr_can_be_non_resident    ntfs_attr_add Require the whole entry to lie within attrdef_size in the loop guard, and reject at mount a $AttrDef too small to hold one attr_def entry.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-98136</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3579 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://vulnerability.circl.lu/vuln/wid-sec-w-2026-3579</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand herbeizuführen oder nicht näher spezifizierten Angriff durchzufü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 Zustand herbeizuführen oder nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/wid-sec-w-2026-3579</guid>
    </item>
  </channel>
</rss>
