<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-19T23:39:40.119835+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/cve-2026-99234</id>
    <title>CVE-2026-99234 — tracing: Unregister field variable histograms when the command fails</title>
    <updated>2026-11-19T23:39:40.138692+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>tracing: Unregister field variable histograms when the command fails</p>
<p>An action that names a field on another event needs that field as a
variable, so create_field_var_hist() registers a second hist trigger on
that event to provide it, and records it in
target_hist_data-&gt;field_var_hists[].</p>
<p>If a later part of the same command fails, create_actions() returns an
error and event_hist_trigger_parse() jumps to out_free. The write fails
with -EINVAL and sched_switch gets no trigger, but:</p>
<p># echo 'hist:keys=pid:ts0=common_timestamp.usecs' &gt;&gt; \
      events/sched/sched_waking/trigger
  # echo 'my_synth u64 lat; int a; int b' &gt;&gt; synthetic_events
  # echo 'hist:keys=next_pid:wakeup_lat=common_timestamp.usecs-$ts0:\
      onmatch(sched.sched_waking).my_synth($wakeup_lat,prio,nosuchfld)'\
      &gt;&gt; events/sched/sched_switch/trigger
  # cat events/sched/sched_waking/trigger
  hist:keys=pid:vals=hitcount:ts0=common_timestamp.usecs:sort=hitcount:size=2048:clock=global [active]
  hist:keys=pid:vals=hitcount:synthetic_prio=prio:sort=hitcount:size=2048 [active]</p>
<p>The second histogram is the one created for 'prio'. It is still active and
still counting.</p>
<p>out_free reaches destroy_field_var_hists(), which frees the
field_var_hists[] entries, but never unregister_field_var_hists(), which is
what removes the triggers and runs only from event_hist_trigger_free(). The
entry is freed and the trigger is left with nothing tracking it.…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-99234"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/usn-9165-1</id>
    <title>USN-9165-1 — linux vulnerabilities</title>
    <updated>2026-11-19T23:39:40.138842+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:26.10: linux</p>
<p>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)</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/usn-9165-1"/>
  </entry>
</feed>
