356458 matches found
CVE-2026-99248 i2c: xiic: restore non-managed runtime PM to fix clk WARN flood
In the Linux kernel, the following vulnerability has been resolved: i2c: xiic: restore non-managed runtime PM to fix clk WARN flood The devres conversion replaced manual pmruntimeenable/disable with devmpmruntimesetactiveenabled and dropped the remove-time runtime PM teardown. The managed release...
EUVD-2026-115777
In the Linux kernel, the following vulnerability has been resolved: tracing: Do not initialize tracefs work if tracing is disabled If trace buffer allocation fails during early boot e.g. in earlytraceinit - allocatetracebuffers, tracingdisabled is left set to 1 and the global trace array events...
CVE-2026-99248
The Linux kernel contains a vulnerability in the i2c: xiic driver where a devres conversion caused a clk WARN flood during teardown. The managed runtime PM helper executed teardowns in the incorrect order, leading to clk_core_disable() being called on already-disabled clocks. The fix involves dro...
EUVD-2026-115778
In the Linux kernel, the following vulnerability has been resolved: i2c: xiic: restore non-managed runtime PM to fix clk WARN flood The devres conversion replaced manual pmruntimeenable/disable with devmpmruntimesetactiveenabled and dropped the remove-time runtime PM teardown. The managed release...
EUVD-2026-115779
In the Linux kernel, the following vulnerability has been resolved: pidnamespace: make zappidnsprocesses freezable When the init of a pid namespace exits, zappidnsprocesses waits until all other pids in the namespace are freed. A tracer outside the namespace that does not reap its traced zombies...
CVE-2026-99247
The Linux kernel contains a vulnerability where failing to allocate trace buffers during early boot leaves the tracing_disabled flag set and the global trace array events list uninitialized. Subsequently, tracer_init_tracefs() queues asynchronous work without verifying this status, leading to a N...
CVE-2026-99249
In the Linux kernel , a vulnerability in pid_namespace was identified where the zap_pid_ns_processes() function would cause suspend attempts to fail. When the init of a pid namespace exits, this function waits for all other pids in the namespace to be freed. However, if an external tracer fails t...
CVE-2026-99248 i2c: xiic: restore non-managed runtime PM to fix clk WARN flood
In the Linux kernel, the following vulnerability has been resolved: i2c: xiic: restore non-managed runtime PM to fix clk WARN flood The devres conversion replaced manual pmruntimeenable/disable with devmpmruntimesetactiveenabled and dropped the remove-time runtime PM teardown. The managed release...
CVE-2026-99246 tipc: protect node reset trace dump with node lock
In the Linux kernel, the following vulnerability has been resolved: tipc: protect node reset trace dump with node lock The tipcnoderesetlinks trace event asks tipcnodedump to walk the node's link entries. Unlike the other node events that request link data, this event runs without the node lock...
CVE-2026-99246 tipc: protect node reset trace dump with node lock
In the Linux kernel, the following vulnerability has been resolved: tipc: protect node reset trace dump with node lock The tipcnoderesetlinks trace event asks tipcnodedump to walk the node's link entries. Unlike the other node events that request link data, this event runs without the node lock...
EUVD-2026-115776
In the Linux kernel, the following vulnerability has been resolved: tipc: protect node reset trace dump with node lock The tipcnoderesetlinks trace event asks tipcnodedump to walk the node's link entries. Unlike the other node events that request link data, this event runs without the node lock...
CVE-2026-99246
The Linux kernel contains a slab-use-after-free vulnerability in the tipc (Transparent Inter-Process Communication) component. The tipc_node_reset_links trace event calls tipc_node_dump() without acquiring the necessary node lock . This allows a concurrent bearer teardown to free a link via tipc_...
CVE-2026-99245
The Linux kernel contains a race condition in the keyring subsystem. Specifically, the restrict_link check in key_reject_and_link() occurs before the keyring semaphore is acquired, creating a race window with a concurrent keyring_restrict() call that installs restrictions while holding the semaph...
CVE-2026-99245 KEYS: Fix key_reject_and_link() race with keyring restriction
In the Linux kernel, the following vulnerability has been resolved: KEYS: Fix keyrejectandlink race with keyring restriction The restrictlink check in keyrejectandlink is done before taking the keyring semaphore, racing with a concurrent keyringrestrict that installs the restriction while holding...
CVE-2026-99245 KEYS: Fix key_reject_and_link() race with keyring restriction
In the Linux kernel, the following vulnerability has been resolved: KEYS: Fix keyrejectandlink race with keyring restriction The restrictlink check in keyrejectandlink is done before taking the keyring semaphore, racing with a concurrent keyringrestrict that installs the restriction while holding...
EUVD-2026-115775
In the Linux kernel, the following vulnerability has been resolved: KEYS: Fix keyrejectandlink race with keyring restriction The restrictlink check in keyrejectandlink is done before taking the keyring semaphore, racing with a concurrent keyringrestrict that installs the restriction while holding...
EUVD-2026-115774
In the Linux kernel, the following vulnerability has been resolved: pidnamespace: prevent TIFNOTIFYSIGNAL from interrupting the reaper Since commit 7fea700e04bd "zappidnsprocesses: clear TIFNOTIFYSIGNAL along with TIFSIGPENDING" zappidnsprocesses clears TIFNOTIFYSIGNAL before every kernelwait4...
CVE-2026-99244 pid_namespace: prevent TIF_NOTIFY_SIGNAL from interrupting the reaper
In the Linux kernel, the following vulnerability has been resolved: pidnamespace: prevent TIFNOTIFYSIGNAL from interrupting the reaper Since commit 7fea700e04bd "zappidnsprocesses: clear TIFNOTIFYSIGNAL along with TIFSIGPENDING" zappidnsprocesses clears TIFNOTIFYSIGNAL before every kernelwait4...
CVE-2026-99244
The Linux kernel contains a vulnerability in the pid_namespace where the reaper could enter a busy-wait state. This occurs because kernel_wait4() does not sleep and returns -ERESTARTSYS if signal_pending() is true. Previous attempts to clear TIF_NOTIFY_SIGNAL were insufficient as it could be re-r...
CVE-2026-99244 pid_namespace: prevent TIF_NOTIFY_SIGNAL from interrupting the reaper
In the Linux kernel, the following vulnerability has been resolved: pidnamespace: prevent TIFNOTIFYSIGNAL from interrupting the reaper Since commit 7fea700e04bd "zappidnsprocesses: clear TIFNOTIFYSIGNAL along with TIFSIGPENDING" zappidnsprocesses clears TIFNOTIFYSIGNAL before every kernelwait4...