<?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 14:52:12 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-93275</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2026-93275</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-93275</guid>
    </item>
    <item>
      <title>fkie_cve-2026-93275</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-93275</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;perf/x86/intel/pt: Fix stop/start with no update&lt;/p&gt;
&lt;p&gt;If pt_event_stop() is called without PERF_EF_UPDATE flag, then
perf_aux_output_end() is not called.  A subsequent call to pt_event_start()
will call perf_aux_output_begin() again which violates the rule against
nesting and triggers a WARNING in perf_aux_output_begin().&lt;/p&gt;
&lt;p&gt;Originally, pt_event_stop() was never called without PERF_EF_UPDATE,
because the only code paths to do so are from event overflow, and Intel PT
does not do that.&lt;/p&gt;
&lt;p&gt;However the introduction of group throttling by commit 9734e25fbf5ae
(&amp;#34;perf: Fix the throttle logic for a group&amp;#34;) meant that an Intel PT event
could be throttled if it was part of a group.  Throttling calls PMU
 -&amp;gt;stop() / -&amp;gt;start() callbacks without flags.&lt;/p&gt;
&lt;p&gt;An example is when AUX area sampling is used. The following commands
hit the issue:&lt;/p&gt;
&lt;p&gt;echo 10000 &amp;gt; /proc/sys/kernel/perf_event_max_sample_rate&lt;/p&gt;
&lt;p&gt;perf record -F32000 --aux-sample -e &amp;#39;{intel_pt//u,cycles:u}&amp;#39; \
  -- bash -c &amp;#39;for i in `seq 1 100000` ; do true ; done&amp;#39;&lt;/p&gt;
&lt;p&gt;Use PERF_HES_UPTODATE to track whether perf_aux_output_begin() and
perf_aux_output_end() are balanced.  A cleared PERF_HES_UPTODATE bit
indicates that an AUX output context is still open.&lt;/p&gt;
&lt;p&gt;Amend pt_event_start() / pt_event_stop() accordingly so that begin/end
stay balanced:&lt;/p&gt;
&lt;p&gt;- In non-snapshot mode, stop() always closes the buffer (the buffer may
   have run out of space, and that accounting is done by the update), s…&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;perf/x86/intel/pt: Fix stop/start with no update&lt;/p&gt;
&lt;p&gt;If pt_event_stop() is called without PERF_EF_UPDATE flag, then
perf_aux_output_end() is not called.  A subsequent call to pt_event_start()
will call perf_aux_output_begin() again which violates the rule against
nesting and triggers a WARNING in perf_aux_output_begin().&lt;/p&gt;
&lt;p&gt;Originally, pt_event_stop() was never called without PERF_EF_UPDATE,
because the only code paths to do so are from event overflow, and Intel PT
does not do that.&lt;/p&gt;
&lt;p&gt;However the introduction of group throttling by commit 9734e25fbf5ae
(&amp;#34;perf: Fix the throttle logic for a group&amp;#34;) meant that an Intel PT event
could be throttled if it was part of a group.  Throttling calls PMU
 -&amp;gt;stop() / -&amp;gt;start() callbacks without flags.&lt;/p&gt;
&lt;p&gt;An example is when AUX area sampling is used. The following commands
hit the issue:&lt;/p&gt;
&lt;p&gt;echo 10000 &amp;gt; /proc/sys/kernel/perf_event_max_sample_rate&lt;/p&gt;
&lt;p&gt;perf record -F32000 --aux-sample -e &amp;#39;{intel_pt//u,cycles:u}&amp;#39; \
  -- bash -c &amp;#39;for i in `seq 1 100000` ; do true ; done&amp;#39;&lt;/p&gt;
&lt;p&gt;Use PERF_HES_UPTODATE to track whether perf_aux_output_begin() and
perf_aux_output_end() are balanced.  A cleared PERF_HES_UPTODATE bit
indicates that an AUX output context is still open.&lt;/p&gt;
&lt;p&gt;Amend pt_event_start() / pt_event_stop() accordingly so that begin/end
stay balanced:&lt;/p&gt;
&lt;p&gt;- In non-snapshot mode, stop() always closes the buffer (the buffer may
   have run out of space, and that accounting is done by the update), s…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-93275</guid>
    </item>
    <item>
      <title>GHSA-j5v2-xwxq-rp3v</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-j5v2-xwxq-rp3v</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;perf/x86/intel/pt: Fix stop/start with no update&lt;/p&gt;
&lt;p&gt;If pt_event_stop() is called without PERF_EF_UPDATE flag, then
perf_aux_output_end() is not called.  A subsequent call to pt_event_start()
will call perf_aux_output_begin() again which violates the rule against
nesting and triggers a WARNING in perf_aux_output_begin().&lt;/p&gt;
&lt;p&gt;Originally, pt_event_stop() was never called without PERF_EF_UPDATE,
because the only code paths to do so are from event overflow, and Intel PT
does not do that.&lt;/p&gt;
&lt;p&gt;However the introduction of group throttling by commit 9734e25fbf5ae
(&amp;#34;perf: Fix the throttle logic for a group&amp;#34;) meant that an Intel PT event
could be throttled if it was part of a group.  Throttling calls PMU
 -&amp;gt;stop() / -&amp;gt;start() callbacks without flags.&lt;/p&gt;
&lt;p&gt;An example is when AUX area sampling is used. The following commands
hit the issue:&lt;/p&gt;
&lt;p&gt;echo 10000 &amp;gt; /proc/sys/kernel/perf_event_max_sample_rate&lt;/p&gt;
&lt;p&gt;perf record -F32000 --aux-sample -e &amp;#39;{intel_pt//u,cycles:u}&amp;#39; \
  -- bash -c &amp;#39;for i in `seq 1 100000` ; do true ; done&amp;#39;&lt;/p&gt;
&lt;p&gt;Use PERF_HES_UPTODATE to track whether perf_aux_output_begin() and
perf_aux_output_end() are balanced.  A cleared PERF_HES_UPTODATE bit
indicates that an AUX output context is still open.&lt;/p&gt;
&lt;p&gt;Amend pt_event_start() / pt_event_stop() accordingly so that begin/end
stay balanced:&lt;/p&gt;
&lt;p&gt;- In non-snapshot mode, stop() always closes the buffer (the buffer may
   have run out of space, and that accounting is done by the update), s…&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;perf/x86/intel/pt: Fix stop/start with no update&lt;/p&gt;
&lt;p&gt;If pt_event_stop() is called without PERF_EF_UPDATE flag, then
perf_aux_output_end() is not called.  A subsequent call to pt_event_start()
will call perf_aux_output_begin() again which violates the rule against
nesting and triggers a WARNING in perf_aux_output_begin().&lt;/p&gt;
&lt;p&gt;Originally, pt_event_stop() was never called without PERF_EF_UPDATE,
because the only code paths to do so are from event overflow, and Intel PT
does not do that.&lt;/p&gt;
&lt;p&gt;However the introduction of group throttling by commit 9734e25fbf5ae
(&amp;#34;perf: Fix the throttle logic for a group&amp;#34;) meant that an Intel PT event
could be throttled if it was part of a group.  Throttling calls PMU
 -&amp;gt;stop() / -&amp;gt;start() callbacks without flags.&lt;/p&gt;
&lt;p&gt;An example is when AUX area sampling is used. The following commands
hit the issue:&lt;/p&gt;
&lt;p&gt;echo 10000 &amp;gt; /proc/sys/kernel/perf_event_max_sample_rate&lt;/p&gt;
&lt;p&gt;perf record -F32000 --aux-sample -e &amp;#39;{intel_pt//u,cycles:u}&amp;#39; \
  -- bash -c &amp;#39;for i in `seq 1 100000` ; do true ; done&amp;#39;&lt;/p&gt;
&lt;p&gt;Use PERF_HES_UPTODATE to track whether perf_aux_output_begin() and
perf_aux_output_end() are balanced.  A cleared PERF_HES_UPTODATE bit
indicates that an AUX output context is still open.&lt;/p&gt;
&lt;p&gt;Amend pt_event_start() / pt_event_stop() accordingly so that begin/end
stay balanced:&lt;/p&gt;
&lt;p&gt;- In non-snapshot mode, stop() always closes the buffer (the buffer may
   have run out of space, and that accounting is done by the update), s…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-j5v2-xwxq-rp3v</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-93275</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-93275</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: perf/x86/intel/pt: Fix stop/start with no update If pt_event_stop() is called without PERF_EF_UPDATE flag, then perf_aux_output_end() is not called.  A subsequent call to pt_event_start() will call perf_aux_output_begin() again which violates the rule against nesting and triggers a WARNING in perf_aux_output_begin(). Originally, pt_event_stop() was never called without PERF_EF_UPDATE, because the only code paths to do so are from event overflow, and Intel PT does not do that. However the introduction of group throttling by commit 9734e25fbf5ae (&amp;#34;perf: Fix the throttle logic for a group&amp;#34;) meant that an Intel PT event could be throttled if it was part of a group.  Throttling calls PMU  -&amp;gt;stop() / -&amp;gt;start() callbacks without flags. An example is when AUX area sampling is used. The following commands hit the issue:   echo 10000 &amp;gt; /proc/sys/kernel/perf_event_max_sample_rate   perf record -F32000 --aux-sample -e &amp;#39;{intel_pt//u,cycles:u}&amp;#39; \   -- bash -c &amp;#39;for i in `seq 1 100000` ; do true ; done&amp;#39; Use PERF_HES_UPTODATE to track whether perf_aux_output_begin() and perf_aux_output_end() are balanced.  A cleared PERF_HES_UPTODATE bit indicates that an AUX output context is still open. Amend pt_event_start() / pt_event_stop() accordingly so that begin/end stay balanced:  - In non-snapshot mode, stop() always closes the buffer (the buffer may    have run out of space, and that accounting is done by the update), so    a fol…&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: perf/x86/intel/pt: Fix stop/start with no update If pt_event_stop() is called without PERF_EF_UPDATE flag, then perf_aux_output_end() is not called.  A subsequent call to pt_event_start() will call perf_aux_output_begin() again which violates the rule against nesting and triggers a WARNING in perf_aux_output_begin(). Originally, pt_event_stop() was never called without PERF_EF_UPDATE, because the only code paths to do so are from event overflow, and Intel PT does not do that. However the introduction of group throttling by commit 9734e25fbf5ae (&amp;#34;perf: Fix the throttle logic for a group&amp;#34;) meant that an Intel PT event could be throttled if it was part of a group.  Throttling calls PMU  -&amp;gt;stop() / -&amp;gt;start() callbacks without flags. An example is when AUX area sampling is used. The following commands hit the issue:   echo 10000 &amp;gt; /proc/sys/kernel/perf_event_max_sample_rate   perf record -F32000 --aux-sample -e &amp;#39;{intel_pt//u,cycles:u}&amp;#39; \   -- bash -c &amp;#39;for i in `seq 1 100000` ; do true ; done&amp;#39; Use PERF_HES_UPTODATE to track whether perf_aux_output_begin() and perf_aux_output_end() are balanced.  A cleared PERF_HES_UPTODATE bit indicates that an AUX output context is still open. Amend pt_event_start() / pt_event_stop() accordingly so that begin/end stay balanced:  - In non-snapshot mode, stop() always closes the buffer (the buffer may    have run out of space, and that accounting is done by the update), so    a fol…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-93275</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>
