https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 27 Oct 2026 08:22:54 +0000 https://db.gcve.eu/vuln/fkie_cve-2026-98937 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>perf/core: Check kernel access when kernel callchains are requested</p> <p>perf_event_open() currently gates perf_allow_kernel() only on !attr.exclude_kernel.</p> <p>However, users can still request kernel callchain collection with attr.exclude_callchain_kernel == 0 even when attr.exclude_kernel == 1. That still requires kernel profiling privilege, but the existing check does not enforce it.</p> <p>Update the permission check to call perf_allow_kernel() when either kernel sampling is requested or kernel callchains are requested.</p> <p>This keeps permission checks aligned with requested data and prevents unprivileged use of kernel callchain capture.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>perf/core: Check kernel access when kernel callchains are requested</p> <p>perf_event_open() currently gates perf_allow_kernel() only on !attr.exclude_kernel.</p> <p>However, users can still request kernel callchain collection with attr.exclude_callchain_kernel == 0 even when attr.exclude_kernel == 1. That still requires kernel profiling privilege, but the existing check does not enforce it.</p> <p>Update the permission check to call perf_allow_kernel() when either kernel sampling is requested or kernel callchains are requested.</p> <p>This keeps permission checks aligned with requested data and prevents unprivileged use of kernel callchain capture.</p> https://db.gcve.eu/vuln/fkie_cve-2026-98937 https://db.gcve.eu/vuln/ghsa-5cg4-h7ff-5xr5 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>perf/core: Check kernel access when kernel callchains are requested</p> <p>perf_event_open() currently gates perf_allow_kernel() only on !attr.exclude_kernel.</p> <p>However, users can still request kernel callchain collection with attr.exclude_callchain_kernel == 0 even when attr.exclude_kernel == 1. That still requires kernel profiling privilege, but the existing check does not enforce it.</p> <p>Update the permission check to call perf_allow_kernel() when either kernel sampling is requested or kernel callchains are requested.</p> <p>This keeps permission checks aligned with requested data and prevents unprivileged use of kernel callchain capture.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>perf/core: Check kernel access when kernel callchains are requested</p> <p>perf_event_open() currently gates perf_allow_kernel() only on !attr.exclude_kernel.</p> <p>However, users can still request kernel callchain collection with attr.exclude_callchain_kernel == 0 even when attr.exclude_kernel == 1. That still requires kernel profiling privilege, but the existing check does not enforce it.</p> <p>Update the permission check to call perf_allow_kernel() when either kernel sampling is requested or kernel callchains are requested.</p> <p>This keeps permission checks aligned with requested data and prevents unprivileged use of kernel callchain capture.</p> https://db.gcve.eu/vuln/ghsa-5cg4-h7ff-5xr5 https://db.gcve.eu/vuln/msrc_cve-2026-98937 msrc_CVE-2026-98937 https://db.gcve.eu/vuln/msrc_cve-2026-98937 https://db.gcve.eu/vuln/ubuntu-cve-2026-98937 <p><strong>Affected:</strong> 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 257 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: perf/core: Check kernel access when kernel callchains are requested perf_event_open() currently gates perf_allow_kernel() only on !attr.exclude_kernel. However, users can still request kernel callchain collection with attr.exclude_callchain_kernel == 0 even when attr.exclude_kernel == 1. That still requires kernel profiling privilege, but the existing check does not enforce it. Update the permission check to call perf_allow_kernel() when either kernel sampling is requested or kernel callchains are requested. This keeps permission checks aligned with requested data and prevents unprivileged use of kernel callchain capture.</p> <p><strong>Affected:</strong> 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 257 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: perf/core: Check kernel access when kernel callchains are requested perf_event_open() currently gates perf_allow_kernel() only on !attr.exclude_kernel. However, users can still request kernel callchain collection with attr.exclude_callchain_kernel == 0 even when attr.exclude_kernel == 1. That still requires kernel profiling privilege, but the existing check does not enforce it. Update the permission check to call perf_allow_kernel() when either kernel sampling is requested or kernel callchains are requested. This keeps permission checks aligned with requested data and prevents unprivileged use of kernel callchain capture.</p> https://db.gcve.eu/vuln/ubuntu-cve-2026-98937