kernel: USB: ULPI: fix memory leak with using debugfs_lookup()

In the Linux kernel, the following vulnerability has been resolved: USB: ULPI: fix memory leak with using debugfslookup When calling debugfslookup the result must have dput called on it, otherwise the memory will leak over time. To make things simpler, just call debugfslookupandremove instead whi...

kernel: USB: uhci: fix memory leak with using debugfs_lookup()

In the Linux kernel, the following vulnerability has been resolved: USB: uhci: fix memory leak with using debugfslookup When calling debugfslookup the result must have dput called on it, otherwise the memory will leak over time. To make things simpler, just call debugfslookupandremove instead whi...

kernel: trace/blktrace: fix memory leak with using debugfs_lookup()

In the Linux kernel, the following vulnerability has been resolved: trace/blktrace: fix memory leak with using debugfslookup When calling debugfslookup the result must have dput called on it, otherwise the memory will leak over time. To make things simpler, just call debugfslookupandremove instea...

PT-2025-38392

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description A memory leak exists when using the debugfs lookup function in the USB ULPI subsystem. The result of calling debugfs lookup requires dput to be called on it to prevent memory leaks over...

PT-2025-38390

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description A memory leak exists in the trace/blktrace module when using the debugfs lookup function. Failing to call dput on the result of debugfs lookup leads to a memory leak over time. The issue...

PT-2024-14688

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description A null pointer error in the debugfs of the Linux kernel's drm/amd/display component has been resolved. The issue was caused by not checking if the get subvp en callback exists before...

Unbreakable Enterprise kernel security update

5.15.0-102.110.5 - RISC-V: Fix up a cherry-pick warning in setupvmfinal Alexandre Ghiti - Revert 'Bluetooth: btsdio: fix use after free bug in btsdioremove due to unfinished work' Liu Jian - riscv: mm: remove redundant parameter of createfdtearlypagetable Song Shuai - kernfs: change...

kernel: Linux kernel: Hard lockup in lpfc driver leads to Denial of Service

A flaw was found in the Linux kernel. A local user could trigger a hard lockup by concurrently reading the rxmonitor from debugfs during I/O operations in the lpfc driver. This concurrency issue, caused by insufficient spin lock protection, leads to a system crash and results in a Denial of Servi...

kernel: Linux kernel: Hard lockup in lpfc driver leads to Denial of Service

A flaw was found in the Linux kernel. A local user could trigger a hard lockup by concurrently reading the rxmonitor from debugfs during I/O operations in the lpfc driver. This concurrency issue, caused by insufficient spin lock protection, leads to a system crash and results in a Denial of Servi...

K68692291: Linux kernel vulnerability CVE-2018-7754

Security Advisory Description The aoediskdebugfsshow function in drivers/block/aoe/aoeblk.c in the Linux kernel through 4.16.4rc4 allows local users to obtain sensitive address information by reading "ffree: " lines in a debugfs file. CVE-2018-7754 Impact There is no impact; F5 products are not...

SUSE CVE-2010-3079

kernel/trace/ftrace.c in the Linux kernel before 2.6.35.5, when debugfs is enabled, does not properly handle interaction between mutex possession and llseek operations, which allows local users to cause a denial of service NULL pointer dereference and outage of all function tracing files via an...

SUSE CVE-2010-4347

The ACPI subsystem in the Linux kernel before 2.6.36.2 uses 0222 permissions for the debugfs custommethod file, which allows local users to gain privileges by placing a custom ACPI method in the ACPI interpreter tables, related to the acpidebugfsinit function in drivers/acpi/debugfs.c...

SUSE CVE-2011-1021

drivers/acpi/debugfs.c in the Linux kernel before 3.0 allows local users to modify arbitrary kernel memory locations by leveraging root privileges to write to the /sys/kernel/debug/acpi/custommethod file. NOTE: this vulnerability exists because of an incomplete fix for CVE-2010-4347...

SUSE CVE-2013-6378

The lbsdebugfswrite function in drivers/net/wireless/libertas/debugfs.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service OOPS by leveraging root privileges for a zero-length write operation...

SUSE CVE-2017-6899

The msmbusdbgupdaterequestwrite function in drivers/platform/msm/msmbus/msmbusdbg.c in androidkernelhuaweimsm8916 through 2017-06-16 in LineageOS, and possibly other kernels for MSM devices, allows attackers to cause a denial of service NULL pointer dereference and device crash via a crafted...

SUSE CVE-2017-18261

The archtimerregreadstable macro in arch/arm64/include/asm/archtimer.h in the Linux kernel before 4.13 allows local users to cause a denial of service infinite recursion by writing to a file under /sys/kernel/debug in certain circumstances, as demonstrated by a scenario involving debugfs, ftrace,...

SUSE CVE-2018-7754

The aoediskdebugfsshow function in drivers/block/aoe/aoeblk.c in the Linux kernel through 4.16.4rc4 allows local users to obtain sensitive address information by reading "ffree: " lines in a debugfs file...

SUSE CVE-2018-20449

The hidmachanstats function in drivers/dma/qcom/hidmadbg.c in the Linux kernel 4.14.90 allows local users to obtain sensitive address information by reading "callback=" lines in a debugfs file...

SUSE CVE-2018-20509

The printbinderrefolocked function in drivers/android/binder.c in the Linux kernel 4.14.90 allows local users to obtain sensitive address information by reading " ref desc node" lines in a debugfs file...

SUSE CVE-2018-20510

The printbindertransactionilocked function in drivers/android/binder.c in the Linux kernel 4.14.90 allows local users to obtain sensitive address information by reading "from code flags" lines in a debugfs file...