<?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>Tue, 29 Sep 2026 07:44:20 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-04119</title>
      <link>https://db.gcve.eu/vuln/bdu:2026-04119</link>
      <description>bdu:2026-04119</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/bdu:2026-04119</guid>
    </item>
    <item>
      <title>certfr-2025-avi-1009 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Elles permettent à un attaquant de provoqu…</title>
      <link>https://db.gcve.eu/vuln/certfr-2025-avi-1009</link>
      <description>certfr-2025-avi-1009</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/certfr-2025-avi-1009</guid>
    </item>
    <item>
      <title>fkie_cve-2023-53649</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2023-53649</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;perf trace: Really free the evsel-&amp;gt;priv area&lt;/p&gt;
&lt;p&gt;In 3cb4d5e00e037c70 (&amp;#34;perf trace: Free syscall tp fields in
evsel-&amp;gt;priv&amp;#34;) it only was freeing if strcmp(evsel-&amp;gt;tp_format-&amp;gt;system,
&amp;#34;syscalls&amp;#34;) returned zero, while the corresponding initialization of
evsel-&amp;gt;priv was being performed if it was _not_ zero, i.e. if the tp
system wasn&amp;#39;t &amp;#39;syscalls&amp;#39;.&lt;/p&gt;
&lt;p&gt;Just stop looking for that and free it if evsel-&amp;gt;priv was set, which
should be equivalent.&lt;/p&gt;
&lt;p&gt;Also use the pre-existing evsel_trace__delete() function.&lt;/p&gt;
&lt;p&gt;This resolves these leaks, detected with:&lt;/p&gt;
&lt;p&gt;$ make EXTRA_CFLAGS=&amp;#34;-fsanitize=address&amp;#34; BUILD_BPF_SKEL=1 CORESIGHT=1 O=/tmp/build/perf-tools-next -C tools/perf install-bin&lt;/p&gt;
&lt;p&gt;=================================================================
  ==481565==ERROR: LeakSanitizer: detected memory leaks&lt;/p&gt;
&lt;p&gt;Direct leak of 40 byte(s) in 1 object(s) allocated from:
      #0 0x7f7343cba097 in calloc (/lib64/libasan.so.8+0xba097)
      #1 0x987966 in zalloc (/home/acme/bin/perf+0x987966)
      #2 0x52f9b9 in evsel_trace__new /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:307
      #3 0x52f9b9 in evsel__syscall_tp /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:333
      #4 0x52f9b9 in evsel__init_raw_syscall_tp /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:458
      #5 0x52f9b9 in perf_evsel__raw_syscall_newtp /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:480
      #6 0x540e8b in trace__add_sysc…&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 trace: Really free the evsel-&amp;gt;priv area&lt;/p&gt;
&lt;p&gt;In 3cb4d5e00e037c70 (&amp;#34;perf trace: Free syscall tp fields in
evsel-&amp;gt;priv&amp;#34;) it only was freeing if strcmp(evsel-&amp;gt;tp_format-&amp;gt;system,
&amp;#34;syscalls&amp;#34;) returned zero, while the corresponding initialization of
evsel-&amp;gt;priv was being performed if it was _not_ zero, i.e. if the tp
system wasn&amp;#39;t &amp;#39;syscalls&amp;#39;.&lt;/p&gt;
&lt;p&gt;Just stop looking for that and free it if evsel-&amp;gt;priv was set, which
should be equivalent.&lt;/p&gt;
&lt;p&gt;Also use the pre-existing evsel_trace__delete() function.&lt;/p&gt;
&lt;p&gt;This resolves these leaks, detected with:&lt;/p&gt;
&lt;p&gt;$ make EXTRA_CFLAGS=&amp;#34;-fsanitize=address&amp;#34; BUILD_BPF_SKEL=1 CORESIGHT=1 O=/tmp/build/perf-tools-next -C tools/perf install-bin&lt;/p&gt;
&lt;p&gt;=================================================================
  ==481565==ERROR: LeakSanitizer: detected memory leaks&lt;/p&gt;
&lt;p&gt;Direct leak of 40 byte(s) in 1 object(s) allocated from:
      #0 0x7f7343cba097 in calloc (/lib64/libasan.so.8+0xba097)
      #1 0x987966 in zalloc (/home/acme/bin/perf+0x987966)
      #2 0x52f9b9 in evsel_trace__new /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:307
      #3 0x52f9b9 in evsel__syscall_tp /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:333
      #4 0x52f9b9 in evsel__init_raw_syscall_tp /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:458
      #5 0x52f9b9 in perf_evsel__raw_syscall_newtp /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:480
      #6 0x540e8b in trace__add_sysc…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2023-53649</guid>
    </item>
    <item>
      <title>GHSA-933f-4h29-gq7r</title>
      <link>https://db.gcve.eu/vuln/ghsa-933f-4h29-gq7r</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;perf trace: Really free the evsel-&amp;gt;priv area&lt;/p&gt;
&lt;p&gt;In 3cb4d5e00e037c70 (&amp;#34;perf trace: Free syscall tp fields in
evsel-&amp;gt;priv&amp;#34;) it only was freeing if strcmp(evsel-&amp;gt;tp_format-&amp;gt;system,
&amp;#34;syscalls&amp;#34;) returned zero, while the corresponding initialization of
evsel-&amp;gt;priv was being performed if it was _not_ zero, i.e. if the tp
system wasn&amp;#39;t &amp;#39;syscalls&amp;#39;.&lt;/p&gt;
&lt;p&gt;Just stop looking for that and free it if evsel-&amp;gt;priv was set, which
should be equivalent.&lt;/p&gt;
&lt;p&gt;Also use the pre-existing evsel_trace__delete() function.&lt;/p&gt;
&lt;p&gt;This resolves these leaks, detected with:&lt;/p&gt;
&lt;p&gt;$ make EXTRA_CFLAGS=&amp;#34;-fsanitize=address&amp;#34; BUILD_BPF_SKEL=1 CORESIGHT=1 O=/tmp/build/perf-tools-next -C tools/perf install-bin&lt;/p&gt;
&lt;p&gt;=================================================================
  ==481565==ERROR: LeakSanitizer: detected memory leaks&lt;/p&gt;
&lt;p&gt;Direct leak of 40 byte(s) in 1 object(s) allocated from:
      #0 0x7f7343cba097 in calloc (/lib64/libasan.so.8+0xba097)
      #1 0x987966 in zalloc (/home/acme/bin/perf+0x987966)
      #2 0x52f9b9 in evsel_trace__new /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:307
      #3 0x52f9b9 in evsel__syscall_tp /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:333
      #4 0x52f9b9 in evsel__init_raw_syscall_tp /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:458
      #5 0x52f9b9 in perf_evsel__raw_syscall_newtp /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:480
      #6 0x540e8b in trace__add_sysc…&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 trace: Really free the evsel-&amp;gt;priv area&lt;/p&gt;
&lt;p&gt;In 3cb4d5e00e037c70 (&amp;#34;perf trace: Free syscall tp fields in
evsel-&amp;gt;priv&amp;#34;) it only was freeing if strcmp(evsel-&amp;gt;tp_format-&amp;gt;system,
&amp;#34;syscalls&amp;#34;) returned zero, while the corresponding initialization of
evsel-&amp;gt;priv was being performed if it was _not_ zero, i.e. if the tp
system wasn&amp;#39;t &amp;#39;syscalls&amp;#39;.&lt;/p&gt;
&lt;p&gt;Just stop looking for that and free it if evsel-&amp;gt;priv was set, which
should be equivalent.&lt;/p&gt;
&lt;p&gt;Also use the pre-existing evsel_trace__delete() function.&lt;/p&gt;
&lt;p&gt;This resolves these leaks, detected with:&lt;/p&gt;
&lt;p&gt;$ make EXTRA_CFLAGS=&amp;#34;-fsanitize=address&amp;#34; BUILD_BPF_SKEL=1 CORESIGHT=1 O=/tmp/build/perf-tools-next -C tools/perf install-bin&lt;/p&gt;
&lt;p&gt;=================================================================
  ==481565==ERROR: LeakSanitizer: detected memory leaks&lt;/p&gt;
&lt;p&gt;Direct leak of 40 byte(s) in 1 object(s) allocated from:
      #0 0x7f7343cba097 in calloc (/lib64/libasan.so.8+0xba097)
      #1 0x987966 in zalloc (/home/acme/bin/perf+0x987966)
      #2 0x52f9b9 in evsel_trace__new /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:307
      #3 0x52f9b9 in evsel__syscall_tp /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:333
      #4 0x52f9b9 in evsel__init_raw_syscall_tp /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:458
      #5 0x52f9b9 in perf_evsel__raw_syscall_newtp /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:480
      #6 0x540e8b in trace__add_sysc…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-933f-4h29-gq7r</guid>
    </item>
    <item>
      <title>RHSA-2022:1988 — Red Hat Security Advisory: kernel security, bug fix, and enhancement update</title>
      <link>https://db.gcve.eu/vuln/rhsa-2022:1988</link>
      <description>&lt;p&gt;kernel: avoid cyclic entity chains due to malformed USB descriptors kernel: speculation on incompletely validated data on IBM Power9 kernel: integer overflow in k_ascii() in drivers/tty/vt/keyboard.c kernel: use-after-free in nouveau kernel module kernel: out-of-bounds read in bpf_skb_change_head() of filter.c due to a use-after-free kernel: joydev: zero size passed to joydev_handle_JSIOCSBTNMAP() kernel: reading /proc/sysvipc/shm does not scale with large shared memory segment counts kernel: out-of-bound Read in qrtr_endpoint_post in net/qrtr/qrtr.c kernel: crypto: ccp - fix resource leaks in ccp_run_aes_gcm_cmd() kernel: possible use-after-free in bluetooth module kernel: unaccounted ipc objects in Linux kernel lead to breaking memcg limits and DoS attacks kernel: DoS in ccp_run_aes_gcm_cmd() function kernel: sctp: Invalid chunks may be used to remotely remove existing associations kernel: lack of port sanity checking in natd and netfilter leads to exploit of OpenVPN clients kernel: stack information leak in infiniband RDMA kernel: possible leak or coruption of data residing on hugetlbfs kernel: security regression for CVE-2018-13405 kernel: fget: check that the fd still exists after getting a ref to it kernel: KVM: SVM: out-of-bounds read/write in sev_es_string_io kernel: Buffer overwrite in decode_nfs_fh function kernel: cgroup: Use open-time creds and namespace for migration perm checks kernel: Race condition in races in sk_peer_pid and sk_peer_cred accesses kernel: Lin…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: avoid cyclic entity chains due to malformed USB descriptors kernel: speculation on incompletely validated data on IBM Power9 kernel: integer overflow in k_ascii() in drivers/tty/vt/keyboard.c kernel: use-after-free in nouveau kernel module kernel: out-of-bounds read in bpf_skb_change_head() of filter.c due to a use-after-free kernel: joydev: zero size passed to joydev_handle_JSIOCSBTNMAP() kernel: reading /proc/sysvipc/shm does not scale with large shared memory segment counts kernel: out-of-bound Read in qrtr_endpoint_post in net/qrtr/qrtr.c kernel: crypto: ccp - fix resource leaks in ccp_run_aes_gcm_cmd() kernel: possible use-after-free in bluetooth module kernel: unaccounted ipc objects in Linux kernel lead to breaking memcg limits and DoS attacks kernel: DoS in ccp_run_aes_gcm_cmd() function kernel: sctp: Invalid chunks may be used to remotely remove existing associations kernel: lack of port sanity checking in natd and netfilter leads to exploit of OpenVPN clients kernel: stack information leak in infiniband RDMA kernel: possible leak or coruption of data residing on hugetlbfs kernel: security regression for CVE-2018-13405 kernel: fget: check that the fd still exists after getting a ref to it kernel: KVM: SVM: out-of-bounds read/write in sev_es_string_io kernel: Buffer overwrite in decode_nfs_fh function kernel: cgroup: Use open-time creds and namespace for migration perm checks kernel: Race condition in races in sk_peer_pid and sk_peer_cred accesses kernel: Lin…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/rhsa-2022:1988</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:21040-1 — Security update for the Linux Kernel</title>
      <link>https://db.gcve.eu/vuln/suse-su-2025:21040-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/suse-su-2025:21040-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-53649</title>
      <link>https://db.gcve.eu/vuln/ubuntu-cve-2023-53649</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 117 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: perf trace: Really free the evsel-&amp;gt;priv area In 3cb4d5e00e037c70 (&amp;#34;perf trace: Free syscall tp fields in evsel-&amp;gt;priv&amp;#34;) it only was freeing if strcmp(evsel-&amp;gt;tp_format-&amp;gt;system, &amp;#34;syscalls&amp;#34;) returned zero, while the corresponding initialization of evsel-&amp;gt;priv was being performed if it was _not_ zero, i.e. if the tp system wasn&amp;#39;t &amp;#39;syscalls&amp;#39;. Just stop looking for that and free it if evsel-&amp;gt;priv was set, which should be equivalent. Also use the pre-existing evsel_trace__delete() function. This resolves these leaks, detected with:   $ make EXTRA_CFLAGS=&amp;#34;-fsanitize=address&amp;#34; BUILD_BPF_SKEL=1 CORESIGHT=1 O=/tmp/build/perf-tools-next -C tools/perf install-bin   =================================================================   ==481565==ERROR: LeakSanitizer: detected memory leaks   Direct leak of 40 byte(s) in 1 object(s) allocated from:       #0 0x7f7343cba097 in calloc (/lib64/libasan.so.8+0xba097)       #1 0x987966 in zalloc (/home/acme/bin/perf+0x987966)       #2 0x52f9b9 in evsel_trace__new /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:307       #3 0x52f9b9 in evsel__syscall_tp /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:333       #4 0x52f9b9 in evsel__init_raw_syscall_tp /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:458       #5 0x52f9b9 in perf_evsel__raw_syscall_newtp /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:480       #6 0x540e8b in trace__add_syscall_newt…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 117 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: perf trace: Really free the evsel-&amp;gt;priv area In 3cb4d5e00e037c70 (&amp;#34;perf trace: Free syscall tp fields in evsel-&amp;gt;priv&amp;#34;) it only was freeing if strcmp(evsel-&amp;gt;tp_format-&amp;gt;system, &amp;#34;syscalls&amp;#34;) returned zero, while the corresponding initialization of evsel-&amp;gt;priv was being performed if it was _not_ zero, i.e. if the tp system wasn&amp;#39;t &amp;#39;syscalls&amp;#39;. Just stop looking for that and free it if evsel-&amp;gt;priv was set, which should be equivalent. Also use the pre-existing evsel_trace__delete() function. This resolves these leaks, detected with:   $ make EXTRA_CFLAGS=&amp;#34;-fsanitize=address&amp;#34; BUILD_BPF_SKEL=1 CORESIGHT=1 O=/tmp/build/perf-tools-next -C tools/perf install-bin   =================================================================   ==481565==ERROR: LeakSanitizer: detected memory leaks   Direct leak of 40 byte(s) in 1 object(s) allocated from:       #0 0x7f7343cba097 in calloc (/lib64/libasan.so.8+0xba097)       #1 0x987966 in zalloc (/home/acme/bin/perf+0x987966)       #2 0x52f9b9 in evsel_trace__new /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:307       #3 0x52f9b9 in evsel__syscall_tp /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:333       #4 0x52f9b9 in evsel__init_raw_syscall_tp /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:458       #5 0x52f9b9 in perf_evsel__raw_syscall_newtp /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:480       #6 0x540e8b in trace__add_syscall_newt…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ubuntu-cve-2023-53649</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2229 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2025-2229</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und andere nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und andere nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/wid-sec-w-2025-2229</guid>
    </item>
  </channel>
</rss>
