540819 matches found
CVE-2026-97918
A slab-use-after-free vulnerability exists in the Linux kernel tracing subsystem. The issue occurs because a trigger registered during a failed hist_trigger_enable() operation remains on the global named_triggers list but is not on the file->triggers list. This causes hist_unregister_trigger()...
EUVD-2026-86772
In the Linux kernel, the following vulnerability has been resolved: tracing: Undo the registration when enabling the histogram trigger fails Commit 6f86bdeab633 "tracing: Fix bad hist from corrupting namedtriggers list" described how a trigger that is registered but not on file-triggers ends up...
CVE-2026-97919 tracing: Take the reference before publishing the named histogram trigger
In the Linux kernel, the following vulnerability has been resolved: tracing: Take the reference before publishing the named histogram trigger eventhisttriggernamedinit puts the trigger on the global namedtriggers list and only then takes the reference on the trigger it shares its histogram with:...
CVE-2026-97918 tracing: Undo the registration when enabling the histogram trigger fails
In the Linux kernel, the following vulnerability has been resolved: tracing: Undo the registration when enabling the histogram trigger fails Commit 6f86bdeab633 "tracing: Fix bad hist from corrupting namedtriggers list" described how a trigger that is registered but not on file-triggers ends up...
CVE-2026-97919
A slab-use-after-free vulnerability exists in the Linux kernel tracing subsystem. The issue occurs in event_hist_trigger_named_init() because the function publishes a trigger to the global named_triggers list before ensuring the subsequent initialization (event_hist_trigger_init()) succeeds. If a...
CVE-2026-97918 tracing: Undo the registration when enabling the histogram trigger fails
In the Linux kernel, the following vulnerability has been resolved: tracing: Undo the registration when enabling the histogram trigger fails Commit 6f86bdeab633 "tracing: Fix bad hist from corrupting namedtriggers list" described how a trigger that is registered but not on file-triggers ends up...
CVE-2026-97919 tracing: Take the reference before publishing the named histogram trigger
In the Linux kernel, the following vulnerability has been resolved: tracing: Take the reference before publishing the named histogram trigger eventhisttriggernamedinit puts the trigger on the global namedtriggers list and only then takes the reference on the trigger it shares its histogram with:...
EUVD-2026-86773
In the Linux kernel, the following vulnerability has been resolved: tracing: Take the reference before publishing the named histogram trigger eventhisttriggernamedinit puts the trigger on the global namedtriggers list and only then takes the reference on the trigger it shares its histogram with:...
EUVD-2026-86771
In the Linux kernel, the following vulnerability has been resolved: accel/ivpu: Validate full buffer range in ivputocpuaddr Add a size parameter to ivputocpuaddr and validate that the whole vpuaddr, vpuaddr + size range stays within the BO...
CVE-2026-97917 accel/ivpu: Validate full buffer range in ivpu_to_cpu_addr
In the Linux kernel, the following vulnerability has been resolved: accel/ivpu: Validate full buffer range in ivputocpuaddr Add a size parameter to ivputocpuaddr and validate that the whole vpuaddr, vpuaddr + size range stays within the BO...
CVE-2026-97917
The Linux kernel contains a vulnerability in the accel/ivpu component. The issue stems from a lack of range validation in the ivpu_to_cpu_addr function. To resolve this, a size parameter was added to ensure that the entire range from vpu_addr to vpu_addr + size remains within the buffer object (B...
CVE-2026-97916 accel/ivpu: Validate firmware log buffer metadata
In the Linux kernel, the following vulnerability has been resolved: accel/ivpu: Validate firmware log buffer metadata The tracing log headers parsed by fwlogprintbuffer reside in DMA-shared BOs that the NPU firmware can write to. fwlogfrombo validated log-headersize and log-size, but...
CVE-2026-97915 accel/ivpu: Limit firmware log name prints to field size
In the Linux kernel, the following vulnerability has been resolved: accel/ivpu: Limit firmware log name prints to field size The name in struct vputracingbufferheader is a fixed-size array populated by the NPU firmware. It is expected to be NUL-terminated, but nothing on the host side enforces...
CVE-2026-97916
The Linux kernel contains a vulnerability in the accel/ivpu driver related to how firmware log buffer metadata is handled. The tracing log headers are stored in DMA-shared Buffer Objects (BOs) , which the NPU firmware can modify. While fw_log_from_bo() validates the header_size and size fields, f...
EUVD-2026-86770
In the Linux kernel, the following vulnerability has been resolved: accel/ivpu: Validate firmware log buffer metadata The tracing log headers parsed by fwlogprintbuffer reside in DMA-shared BOs that the NPU firmware can write to. fwlogfrombo validated log-headersize and log-size, but...
EUVD-2026-86769
In the Linux kernel, the following vulnerability has been resolved: accel/ivpu: Limit firmware log name prints to field size The name in struct vputracingbufferheader is a fixed-size array populated by the NPU firmware. It is expected to be NUL-terminated, but nothing on the host side enforces...
CVE-2026-97915
The Linux kernel contains a vulnerability in the accel/ivpu component where the name field in struct vpu_tracing_buffer_header is populated by the NPU firmware. Because the host side does not enforce NUL-termination on this fixed-size array, using an unbounded string conversion can lead to an out...
EUVD-2026-86768
In the Linux kernel, the following vulnerability has been resolved: accel: ethosu: Fix ethosujobopen return value A WARNON returns a 0 or 1, not the original negative errno. Just drop the WARNON as the FD open will pass the return code to userspace and there's only one possible source of the erro...
CVE-2026-97914
In the Linux kernel , a vulnerability was identified in the ethosu accelerator component within the ethosu_job_open() function. The issue occurred because a WARN_ON() macro returned a 0 or 1 instead of the original negative error code (errno), potentially leading to incorrect error reporting to u...
CVE-2026-97914 accel: ethosu: Fix ethosu_job_open() return value
In the Linux kernel, the following vulnerability has been resolved: accel: ethosu: Fix ethosujobopen return value A WARNON returns a 0 or 1, not the original negative errno. Just drop the WARNON as the FD open will pass the return code to userspace and there's only one possible source of the erro...