2899 matches found
CVE-2023-54171 tracing: Fix memory leak of iter->temp when reading trace_pipe
In the Linux kernel, the following vulnerability has been resolved: tracing: Fix memory leak of iter-temp when reading tracepipe kmemleak reports: unreferenced object 0xffff88814d14e200 size 256: comm "cat", pid 336, jiffies 4294871818 age 779.490s hex dump first 32 bytes: 04 00 01 03 00 00 00 00...
PT-2025-54040
Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description The Linux kernel contains an issue within the tracing subsystem related to the trace buffered event disable function. A warning occurs when trace buffered event disable is called twice...
Linux Distros Unpatched Vulnerability : CVE-2023-54211
The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - tracing: Fix warning in tracebufferedeventdisable Warning happened in tracebufferedeventdisable at WARNONONCE!tracebufferedeventref Call Trace: ? warn+0xa5/0x1b...
Unity Linux 20.1060e / 20.1070e Security Update: kernel (UTSA-2025-992498)
The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2025-992498 advisory. In the Linux kernel, the following vulnerability has been resolved: spmi: trace: fix stack-out-of-bound access in SPMI tracing functions tracespmiwritebegin and...
PT-2025-54000
Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description A memory leak exists when reading the 'trace pipe' file within the Linux kernel's tracing subsystem. Specifically, the iter-temp memory is allocated or relocated in the trace find next...
Tracing + Assessments Access
This report is not public...
SUSE CVE-2023-54139
In the Linux kernel, the following vulnerability has been resolved: tracing/userevents: Ensure write index cannot be negative The write index indicates which event the data is for and accesses a per-file array. The index is passed by user processes during write calls as the first 4 bytes. Ensure...
EUVD-2023-60306
In the Linux kernel, the following vulnerability has been resolved: tracing/userevents: Ensure write index cannot be negative The write index indicates which event the data is for and accesses a per-file array. The index is passed by user processes during write calls as the first 4 bytes. Ensure...
EUVD-2023-60281
In the Linux kernel, the following vulnerability has been resolved: audit: fix possible soft lockup in auditinodechild Tracefs or debugfs maybe cause hundreds to thousands of PATH records, too many PATH records maybe cause soft lockup. For example: 1. CONFIGKASAN=y && CONFIGPREEMPTION=n 2. auditc...
CVE-2023-54139
In the Linux kernel, the following vulnerability has been resolved: tracing/userevents: Ensure write index cannot be negative The write index indicates which event the data is for and accesses a per-file array. The index is passed by user processes during write calls as the first 4 bytes. Ensure...
CVE-2023-54139
In the Linux kernel, the following vulnerability has been resolved: tracing/userevents: Ensure write index cannot be negative The write index indicates which event the data is for and accesses a per-file array. The index is passed by user processes during write calls as the first 4 bytes. Ensure...
UBUNTU-CVE-2023-54045
In the Linux kernel, the following vulnerability has been resolved: audit: fix possible soft lockup in auditinodechild Tracefs or debugfs maybe cause hundreds to thousands of PATH records, too many PATH records maybe cause soft lockup. For example: 1. CONFIGKASAN=y && CONFIGPREEMPTION=n 2. auditc...
UBUNTU-CVE-2023-54139
In the Linux kernel, the following vulnerability has been resolved: tracing/userevents: Ensure write index cannot be negative The write index indicates which event the data is for and accesses a per-file array. The index is passed by user processes during write calls as the first 4 bytes. Ensure...
CVE-2023-54139 tracing/user_events: Ensure write index cannot be negative
In the Linux kernel, the following vulnerability has been resolved: tracing/userevents: Ensure write index cannot be negative The write index indicates which event the data is for and accesses a per-file array. The index is passed by user processes during write calls as the first 4 bytes. Ensure...
CVE-2023-54139
CVE-2023-54139: In the Linux kernel, the tracing/user_events path was fixed to ensure the write index used for per-file event data cannot be negative. The vulnerability could allow out-of-bounds access if a signed index is provided via write() (first 4 bytes). The fix returns -EINVAL to reject ne...
CVE-2023-54139 tracing/user_events: Ensure write index cannot be negative
In the Linux kernel, the following vulnerability has been resolved: tracing/userevents: Ensure write index cannot be negative The write index indicates which event the data is for and accesses a per-file array. The index is passed by user processes during write calls as the first 4 bytes. Ensure...
EUVD-2025-205078
In the Linux kernel, the following vulnerability has been resolved: coresight: ETR: Fix ETR buffer use-after-free issue When ETR is enabled as CSMODESYSFS, if the buffer size is changed and enabled again, currently sysfsbuf will point to the newly allocated memorybufnew and free the old...
CVE-2025-68376
In the Linux kernel, the following vulnerability has been resolved: coresight: ETR: Fix ETR buffer use-after-free issue When ETR is enabled as CSMODESYSFS, if the buffer size is changed and enabled again, currently sysfsbuf will point to the newly allocated memorybufnew and free the old...
CVE-2025-68378
In the Linux kernel, the following vulnerability has been resolved: bpf: Fix stackmap overflow check in bpfgetstackid Syzkaller reported a KASAN slab-out-of-bounds write in bpfgetstackid when copying stack trace data. The issue occurs when the perf trace contains more stack entries than the stack...
UBUNTU-CVE-2025-68359
In the Linux kernel, the following vulnerability has been resolved: btrfs: fix double free of qgroup record after failure to add delayed ref head In the previous code it was possible to incur into a double kfree scenario when calling adddelayedrefhead. This could happen if the record was reported...