CVE-2026-64556 perf/core: Detach event groups during remove_on_exec

In the Linux kernel, the following vulnerability has been resolved: perf/core: Detach event groups during removeonexec perfeventremoveonexec removes events by calling perfeventexitevent. For top-level events, this removes the event from the context with DETACHEXIT only. This can leave inconsisten...

CVE-2026-64556

In the Linux kernel, the following vulnerability has been resolved: perf/core: Detach event groups during removeonexec perfeventremoveonexec removes events by calling perfeventexitevent. For top-level events, this removes the event from the context with DETACHEXIT only. This can leave inconsisten...

CVE-2026-64556 perf/core: Detach event groups during remove_on_exec

In the Linux kernel, the following vulnerability has been resolved: perf/core: Detach event groups during removeonexec perfeventremoveonexec removes events by calling perfeventexitevent. For top-level events, this removes the event from the context with DETACHEXIT only. This can leave inconsisten...

EUVD-2026-50201

In the Linux kernel, the following vulnerability has been resolved: perf/core: Detach event groups during removeonexec perfeventremoveonexec removes events by calling perfeventexitevent. For top-level events, this removes the event from the context with DETACHEXIT only. This can leave inconsisten...

CVE-2026-64556

CVE-2026-64556 pertains to the Linux kernel PMU subsystem (perf/core). When a performance event group leader is removed during process exit, its surviving siblings can remain active and still linked to the removed leader’s list, leaving the PMU context active list in a potentially inconsistent st...

PT-2026-65734

In the Linux kernel, the following vulnerability has been resolved: perf/core: Detach event groups during remove on exec perf event remove on exec removes events by calling perf event exit event. For top-level events, this removes the event from the context with DETACH EXIT only. This can leave...

PT-2026-65857

Name of the Vulnerable Software and Affected Versions Linux kernel versions prior to 6.18.41 Linux kernel versions prior to 6.12.100 Linux kernel versions prior to 6.6.147 Linux kernel versions prior to 6.1.180 Linux kernel versions prior to 5.15.213 Linux kernel versions prior to 5.10.262...

CVE-2026-18038

CVE-2026-18038 affects nextlevelbuilder GoClaw up to version 3.13.2. The vulnerability targets the ExecTool.Execute function in goclaw/internal/http/tools_invoke.go (jq Handler), enabling remote manipulation that can lead to information disclosure. An exploit has been published; remediation invol...

CVE-2026-18038 nextlevelbuilder GoClaw jq Handler tools_invoke.go ExecTool.Execute information disclosure

A flaw has been found in nextlevelbuilder GoClaw up to 3.13.2. Affected by this vulnerability is the function ExecTool.Execute of the file goclaw/internal/http/toolsinvoke.go of the component jq Handler. Executing a manipulation can lead to information disclosure. The attack can be launched...

CVE-2026-51266

...

SUSE CVE-2026-64371

In the Linux kernel, the following vulnerability has been resolved: proc: protect ptracemayaccess with execupdatelock part 1 Fix the easy cases where procfs currently calls ptracemayaccess without execupdatelock protection, where the fix is to simply add the extra lock or use mmaccess: -...

CVE-2026-64375

In the Linux kernel, the following vulnerability has been resolved: proc: protect ptracemayaccess with execupdatelock FD links procpidgetlink and procpidreadlink currently look up the task from the pid once, then do the ptrace access check on that task, then look up the task from the pid a second...

CVE-2026-64371

In the Linux kernel, the following vulnerability has been resolved: proc: protect ptracemayaccess with execupdatelock part 1 Fix the easy cases where procfs currently calls ptracemayaccess without execupdatelock protection, where the fix is to simply add the extra lock or use mmaccess: -...

UBUNTU-CVE-2026-64375

In the Linux kernel, the following vulnerability has been resolved: proc: protect ptracemayaccess with execupdatelock FD links procpidgetlink and procpidreadlink currently look up the task from the pid once, then do the ptrace access check on that task, then look up the task from the pid a second...

UBUNTU-CVE-2026-64371

In the Linux kernel, the following vulnerability has been resolved: proc: protect ptracemayaccess with execupdatelock part 1 Fix the easy cases where procfs currently calls ptracemayaccess without execupdatelock protection, where the fix is to simply add the extra lock or use mmaccess: -...

CVE-2026-64375

In the Linux kernel, the following vulnerability has been resolved: proc: protect ptracemayaccess with execupdatelock FD links procpidgetlink and procpidreadlink currently look up the task from the pid once, then do the ptrace access check on that task, then look up the task from the pid a second...

CVE-2026-64375 proc: protect ptrace_may_access() with exec_update_lock (FD links)

In the Linux kernel, the following vulnerability has been resolved: proc: protect ptracemayaccess with execupdatelock FD links procpidgetlink and procpidreadlink currently look up the task from the pid once, then do the ptrace access check on that task, then look up the task from the pid a second...

CVE-2026-64375

In CVE-2026-64375, the Linux kernel fix addresses a race in ptrace access checks. Previously proc_pid_get_link() and proc_pid_readlink() looked up the task from the pid twice (before and after the check). The patch passes the task to the ->proc_get_link() handler and adds call_proc_get_link() ...

EUVD-2026-48919

In the Linux kernel, the following vulnerability has been resolved: proc: protect ptracemayaccess with execupdatelock FD links procpidgetlink and procpidreadlink currently look up the task from the pid once, then do the ptrace access check on that task, then look up the task from the pid a second...

CVE-2026-64371

The CVE-2026-64371 entry concerns a Linux kernel procfs issue where ptrace_may_access() was called without exec_update_lock. The vulnerability has been resolved by ensuring proper locking or using mm_access(): affected paths include do_task_stat(), proc_pid_wchan(), proc_map_files_lookup(), proc_...