<?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://db.gcve.eu</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, 19 Nov 2026 23:39:39 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-99235 — tracing: Save the event file instead of the compatible histogram</title>
      <link>https://db.gcve.eu/vuln/cve-2026-99235</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tracing: Save the event file instead of the compatible histogram&lt;/p&gt;
&lt;p&gt;create_field_var_hist() creates a histogram on the matched event to
supply a field variable, and records it on the target so it can be torn
down later:&lt;/p&gt;
&lt;p&gt;hist_data = find_compatible_hist(target_hist_data, file);
	...
	/* Save the compatible histogram information */
	var_hist-&amp;gt;hist_data = hist_data;&lt;/p&gt;
&lt;p&gt;hist_data is not the histogram it creates. It is one that was already
there, whose keys the new one copies. The saved pointer has a single
user, unregister_field_var_hists(), which runs when the target is
removed:&lt;/p&gt;
&lt;p&gt;file = hist_data-&amp;gt;field_var_hists[i]-&amp;gt;hist_data-&amp;gt;event_file;&lt;/p&gt;
&lt;p&gt;find_compatible_hist() matches on keys alone, so it can pick one with no
variables of its own. check_var_refs() then returns false and the user
can remove it while the target still points at it:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in event_hist_trigger_free+0x2b2/0x320
 Read of size 8 at addr ffff8880093b90e0 by task init/1&lt;/p&gt;
&lt;p&gt;Freed by task 1:
  kfree+0x154/0x420
  event_hist_trigger_free+0x1d5/0x320
  event_hist_trigger_parse+0x35f3/0x69e0
  trigger_process_regex+0x1a6/0x250&lt;/p&gt;
&lt;p&gt;Save the event file instead. It is all the dereference ever wanted, and
it does not go away when the user removes a trigger.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tracing: Save the event file instead of the compatible histogram&lt;/p&gt;
&lt;p&gt;create_field_var_hist() creates a histogram on the matched event to
supply a field variable, and records it on the target so it can be torn
down later:&lt;/p&gt;
&lt;p&gt;hist_data = find_compatible_hist(target_hist_data, file);
	...
	/* Save the compatible histogram information */
	var_hist-&amp;gt;hist_data = hist_data;&lt;/p&gt;
&lt;p&gt;hist_data is not the histogram it creates. It is one that was already
there, whose keys the new one copies. The saved pointer has a single
user, unregister_field_var_hists(), which runs when the target is
removed:&lt;/p&gt;
&lt;p&gt;file = hist_data-&amp;gt;field_var_hists[i]-&amp;gt;hist_data-&amp;gt;event_file;&lt;/p&gt;
&lt;p&gt;find_compatible_hist() matches on keys alone, so it can pick one with no
variables of its own. check_var_refs() then returns false and the user
can remove it while the target still points at it:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in event_hist_trigger_free+0x2b2/0x320
 Read of size 8 at addr ffff8880093b90e0 by task init/1&lt;/p&gt;
&lt;p&gt;Freed by task 1:
  kfree+0x154/0x420
  event_hist_trigger_free+0x1d5/0x320
  event_hist_trigger_parse+0x35f3/0x69e0
  trigger_process_regex+0x1a6/0x250&lt;/p&gt;
&lt;p&gt;Save the event file instead. It is all the dereference ever wanted, and
it does not go away when the user removes a trigger.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-99235</guid>
    </item>
    <item>
      <title>USN-9165-1 — linux vulnerabilities</title>
      <link>https://db.gcve.eu/vuln/usn-9165-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:26.10: linux&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - Cryptographic API;
  - File systems infrastructure;
  - Key management;
  - Key Management;
  - io_uring subsystem;
  - PID namespace;
  - Tracing infrastructure;
(CVE-2026-99218, CVE-2026-99219, CVE-2026-99220, CVE-2026-99221,
CVE-2026-99222, CVE-2026-99223, CVE-2026-99224, CVE-2026-99225,
CVE-2026-99226, CVE-2026-99227, CVE-2026-99232, CVE-2026-99233,
CVE-2026-99234, CVE-2026-99235, CVE-2026-99236, CVE-2026-99237,
CVE-2026-99238, CVE-2026-99244, CVE-2026-99245)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:26.10: linux&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - Cryptographic API;
  - File systems infrastructure;
  - Key management;
  - Key Management;
  - io_uring subsystem;
  - PID namespace;
  - Tracing infrastructure;
(CVE-2026-99218, CVE-2026-99219, CVE-2026-99220, CVE-2026-99221,
CVE-2026-99222, CVE-2026-99223, CVE-2026-99224, CVE-2026-99225,
CVE-2026-99226, CVE-2026-99227, CVE-2026-99232, CVE-2026-99233,
CVE-2026-99234, CVE-2026-99235, CVE-2026-99236, CVE-2026-99237,
CVE-2026-99238, CVE-2026-99244, CVE-2026-99245)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-9165-1</guid>
    </item>
  </channel>
</rss>
