<?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 17:51:04 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-97919</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-97919</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tracing: Take the reference before publishing the named histogram trigger&lt;/p&gt;
&lt;p&gt;event_hist_trigger_named_init() puts the trigger on the global
named_triggers list and only then takes the reference on the trigger it
shares its histogram with:&lt;/p&gt;
&lt;p&gt;data-&amp;gt;ref++;&lt;/p&gt;
&lt;p&gt;save_named_trigger(data-&amp;gt;named_data-&amp;gt;name, data);&lt;/p&gt;
&lt;p&gt;ret = event_hist_trigger_init(data-&amp;gt;named_data);
	if (ret &amp;lt; 0) {
		kfree(data-&amp;gt;cmd_ops);
		data-&amp;gt;cmd_ops = &amp;amp;trigger_hist_cmd;
	}&lt;/p&gt;
&lt;p&gt;return ret;&lt;/p&gt;
&lt;p&gt;event_hist_trigger_init() fails when alloc_hist_pad() cannot allocate, and
nothing takes the trigger back off the list on the way out.
event_hist_trigger_parse() frees it, and the next lookup by name reads the
freed object:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in find_named_trigger+0xac/0xc0
 Read of size 8 at addr ffff888009346860 by task init/1
  find_named_trigger+0xac/0xc0
  hist_register_trigger+0xc1/0xa00
  event_hist_trigger_parse+0x3146/0x6af0
  event_trigger_write+0xce/0x160
 Freed by task 67:
  kfree+0x154/0x420
  trigger_kthread_fn+0xfd/0x160&lt;/p&gt;
&lt;p&gt;Do the reference first and publish once it has succeeded, so that nothing
which can fail runs after the trigger becomes findable.&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;tracing: Take the reference before publishing the named histogram trigger&lt;/p&gt;
&lt;p&gt;event_hist_trigger_named_init() puts the trigger on the global
named_triggers list and only then takes the reference on the trigger it
shares its histogram with:&lt;/p&gt;
&lt;p&gt;data-&amp;gt;ref++;&lt;/p&gt;
&lt;p&gt;save_named_trigger(data-&amp;gt;named_data-&amp;gt;name, data);&lt;/p&gt;
&lt;p&gt;ret = event_hist_trigger_init(data-&amp;gt;named_data);
	if (ret &amp;lt; 0) {
		kfree(data-&amp;gt;cmd_ops);
		data-&amp;gt;cmd_ops = &amp;amp;trigger_hist_cmd;
	}&lt;/p&gt;
&lt;p&gt;return ret;&lt;/p&gt;
&lt;p&gt;event_hist_trigger_init() fails when alloc_hist_pad() cannot allocate, and
nothing takes the trigger back off the list on the way out.
event_hist_trigger_parse() frees it, and the next lookup by name reads the
freed object:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in find_named_trigger+0xac/0xc0
 Read of size 8 at addr ffff888009346860 by task init/1
  find_named_trigger+0xac/0xc0
  hist_register_trigger+0xc1/0xa00
  event_hist_trigger_parse+0x3146/0x6af0
  event_trigger_write+0xce/0x160
 Freed by task 67:
  kfree+0x154/0x420
  trigger_kthread_fn+0xfd/0x160&lt;/p&gt;
&lt;p&gt;Do the reference first and publish once it has succeeded, so that nothing
which can fail runs after the trigger becomes findable.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-97919</guid>
    </item>
    <item>
      <title>GHSA-6vf7-pxhp-xpjv</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-6vf7-pxhp-xpjv</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tracing: Take the reference before publishing the named histogram trigger&lt;/p&gt;
&lt;p&gt;event_hist_trigger_named_init() puts the trigger on the global
named_triggers list and only then takes the reference on the trigger it
shares its histogram with:&lt;/p&gt;
&lt;p&gt;data-&amp;gt;ref++;&lt;/p&gt;
&lt;p&gt;save_named_trigger(data-&amp;gt;named_data-&amp;gt;name, data);&lt;/p&gt;
&lt;p&gt;ret = event_hist_trigger_init(data-&amp;gt;named_data);
	if (ret &amp;lt; 0) {
		kfree(data-&amp;gt;cmd_ops);
		data-&amp;gt;cmd_ops = &amp;amp;trigger_hist_cmd;
	}&lt;/p&gt;
&lt;p&gt;return ret;&lt;/p&gt;
&lt;p&gt;event_hist_trigger_init() fails when alloc_hist_pad() cannot allocate, and
nothing takes the trigger back off the list on the way out.
event_hist_trigger_parse() frees it, and the next lookup by name reads the
freed object:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in find_named_trigger+0xac/0xc0
 Read of size 8 at addr ffff888009346860 by task init/1
  find_named_trigger+0xac/0xc0
  hist_register_trigger+0xc1/0xa00
  event_hist_trigger_parse+0x3146/0x6af0
  event_trigger_write+0xce/0x160
 Freed by task 67:
  kfree+0x154/0x420
  trigger_kthread_fn+0xfd/0x160&lt;/p&gt;
&lt;p&gt;Do the reference first and publish once it has succeeded, so that nothing
which can fail runs after the trigger becomes findable.&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;tracing: Take the reference before publishing the named histogram trigger&lt;/p&gt;
&lt;p&gt;event_hist_trigger_named_init() puts the trigger on the global
named_triggers list and only then takes the reference on the trigger it
shares its histogram with:&lt;/p&gt;
&lt;p&gt;data-&amp;gt;ref++;&lt;/p&gt;
&lt;p&gt;save_named_trigger(data-&amp;gt;named_data-&amp;gt;name, data);&lt;/p&gt;
&lt;p&gt;ret = event_hist_trigger_init(data-&amp;gt;named_data);
	if (ret &amp;lt; 0) {
		kfree(data-&amp;gt;cmd_ops);
		data-&amp;gt;cmd_ops = &amp;amp;trigger_hist_cmd;
	}&lt;/p&gt;
&lt;p&gt;return ret;&lt;/p&gt;
&lt;p&gt;event_hist_trigger_init() fails when alloc_hist_pad() cannot allocate, and
nothing takes the trigger back off the list on the way out.
event_hist_trigger_parse() frees it, and the next lookup by name reads the
freed object:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in find_named_trigger+0xac/0xc0
 Read of size 8 at addr ffff888009346860 by task init/1
  find_named_trigger+0xac/0xc0
  hist_register_trigger+0xc1/0xa00
  event_hist_trigger_parse+0x3146/0x6af0
  event_trigger_write+0xce/0x160
 Freed by task 67:
  kfree+0x154/0x420
  trigger_kthread_fn+0xfd/0x160&lt;/p&gt;
&lt;p&gt;Do the reference first and publish once it has succeeded, so that nothing
which can fail runs after the trigger becomes findable.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-6vf7-pxhp-xpjv</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-97919</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-97919</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: tracing: Take the reference before publishing the named histogram trigger event_hist_trigger_named_init() puts the trigger on the global named_triggers list and only then takes the reference on the trigger it shares its histogram with: 	data-&amp;gt;ref++; 	save_named_trigger(data-&amp;gt;named_data-&amp;gt;name, data); 	ret = event_hist_trigger_init(data-&amp;gt;named_data); 	if (ret &amp;lt; 0) { 		kfree(data-&amp;gt;cmd_ops); 		data-&amp;gt;cmd_ops = &amp;amp;trigger_hist_cmd; 	} 	return ret; event_hist_trigger_init() fails when alloc_hist_pad() cannot allocate, and nothing takes the trigger back off the list on the way out. event_hist_trigger_parse() frees it, and the next lookup by name reads the freed object:  BUG: KASAN: slab-use-after-free in find_named_trigger+0xac/0xc0  Read of size 8 at addr ffff888009346860 by task init/1   find_named_trigger+0xac/0xc0   hist_register_trigger+0xc1/0xa00   event_hist_trigger_parse+0x3146/0x6af0   event_trigger_write+0xce/0x160  Freed by task 67:   kfree+0x154/0x420   trigger_kthread_fn+0xfd/0x160 Do the reference first and publish once it has succeeded, so that nothing which can fail runs after the trigger becomes findable.&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: tracing: Take the reference before publishing the named histogram trigger event_hist_trigger_named_init() puts the trigger on the global named_triggers list and only then takes the reference on the trigger it shares its histogram with: 	data-&amp;gt;ref++; 	save_named_trigger(data-&amp;gt;named_data-&amp;gt;name, data); 	ret = event_hist_trigger_init(data-&amp;gt;named_data); 	if (ret &amp;lt; 0) { 		kfree(data-&amp;gt;cmd_ops); 		data-&amp;gt;cmd_ops = &amp;amp;trigger_hist_cmd; 	} 	return ret; event_hist_trigger_init() fails when alloc_hist_pad() cannot allocate, and nothing takes the trigger back off the list on the way out. event_hist_trigger_parse() frees it, and the next lookup by name reads the freed object:  BUG: KASAN: slab-use-after-free in find_named_trigger+0xac/0xc0  Read of size 8 at addr ffff888009346860 by task init/1   find_named_trigger+0xac/0xc0   hist_register_trigger+0xc1/0xa00   event_hist_trigger_parse+0x3146/0x6af0   event_trigger_write+0xce/0x160  Freed by task 67:   kfree+0x154/0x420   trigger_kthread_fn+0xfd/0x160 Do the reference first and publish once it has succeeded, so that nothing which can fail runs after the trigger becomes findable.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-97919</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>
