6423 matches found
CVE-2022-49873 bpf: Fix wrong reg type conversion in release_reference()
In the Linux kernel, the following vulnerability has been resolved: bpf: Fix wrong reg type conversion in releasereference Some helper functions will allocate memory. To avoid memory leaks, the verifier requires the eBPF program to release these memories by calling the corresponding helper...
CVE-2022-49860 dmaengine: ti: k3-udma-glue: fix memory leak when register device fail
In the Linux kernel, the following vulnerability has been resolved: dmaengine: ti: k3-udma-glue: fix memory leak when register device fail If deviceregister fails, it should call putdevice to give up reference, the name allocated in devsetname can be freed in callback function kobjectcleanup...
CVE-2022-49836 siox: fix possible memory leak in siox_device_add()
In the Linux kernel, the following vulnerability has been resolved: siox: fix possible memory leak in sioxdeviceadd If deviceregister returns error in sioxdeviceadd, the name allocated by devsetname need be freed. As comment of deviceregister says, it should use putdevice to give up the reference...
CVE-2022-49804 s390: avoid using global register for current_stack_pointer
In the Linux kernel, the following vulnerability has been resolved: s390: avoid using global register for currentstackpointer Commit 30de14b1884b "s390: currentstackpointer shouldn't be a function" made currentstackpointer a global register variable like on many other architectures. Unfortunately...
CVE-2022-49804
CVE-2022-49804 refers to a Linux kernel issue affecting s390 where making current_stack_pointer a global register variable exposed a gcc bug. The vulnerability is tied to stack pointer handling and can lead to stack corruption on affected builds. Public description notes that to mitigate, the min...
CVE-2022-49804 s390: avoid using global register for current_stack_pointer
In the Linux kernel, the following vulnerability has been resolved: s390: avoid using global register for currentstackpointer Commit 30de14b1884b "s390: currentstackpointer shouldn't be a function" made currentstackpointer a global register variable like on many other architectures. Unfortunately...
CVE-2022-49799
Summary of CVE-2022-49799 (Linux kernel): The vulnerability resides in the tracing subsys, specifically register_synth_event(), where if set_synth_event_print_fmt() fails, the code may call trace_remove_event_call() and unregister_trace_event() twice, causing the trace_event_call to invoke __unre...
CVE-2022-49799 tracing: Fix wild-memory-access in register_synth_event()
In the Linux kernel, the following vulnerability has been resolved: tracing: Fix wild-memory-access in registersynthevent In registersynthevent, if setsyntheventprintfmt failed, then both traceremoveeventcall and unregistertraceevent will be called, which means the traceeventcall will call...
DEBIAN-CVE-2025-37746
In the Linux kernel, the following vulnerability has been resolved: perf/dwcpcie: fix duplicate pcidev devices During platformdeviceregister, wrongly using struct device pcidev as platformdata caused a kmemdup copy of pcidev. Worse still, accessing the duplicated device leads to list corruption a...
DEBIAN-CVE-2025-23162
In the Linux kernel, the following vulnerability has been resolved: drm/xe/vf: Don't try to trigger a full GT reset if VF VFs don't have access to the GDRST0x941c register that driver uses to reset a GT. Attempt to trigger a reset using debugfs: $ cat...
UBUNTU-CVE-2025-23162
In the Linux kernel, the following vulnerability has been resolved: drm/xe/vf: Don't try to trigger a full GT reset if VF VFs don't have access to the GDRST0x941c register that driver uses to reset a GT. Attempt to trigger a reset using debugfs: $ cat...
CVE-2025-23162 drm/xe/vf: Don't try to trigger a full GT reset if VF
In the Linux kernel, the following vulnerability has been resolved: drm/xe/vf: Don't try to trigger a full GT reset if VF VFs don't have access to the GDRST0x941c register that driver uses to reset a GT. Attempt to trigger a reset using debugfs: $ cat...
Linux kernel 安全漏洞
Linux kernel is the kernel used by Linux, the open source operating system of the Linux Foundation in the United States. A security vulnerability exists in Linux kernel that stems from a device reference not being properly freed in mISDNdspelementregister, which could lead to a memory leak...
Linux kernel 安全漏洞
Linux kernel is the kernel used by Linux, the open source operating system of the Linux Foundation in the United States. A security vulnerability exists in the Linux kernel that stems from improper register settings and may result in warnings...
Linux kernel 安全漏洞
Linux kernel is the kernel used by Linux, the open source operating system of the Linux Foundation in the United States. A security vulnerability exists in the Linux kernel that stems from a register type conversion error problem in the releasereference function in the bpf driver...
PT-2025-18622 · Linux +1 · Linux Kernel +1
Name of the Vulnerable Software and Affected Versions: Linux kernel affected versions not specified Description: A possible leaked pernet namespace in smc init has been resolved. The issue occurs when register pernet subsys&smc net stat ops is called without error handling. If it fails, the...
Linux kernel 安全漏洞
Linux kernel is the kernel used by Linux, the open source operating system of the Linux Foundation in the United States. A security vulnerability exists in the Linux kernel that stems from a VF attempt to trigger a full GT reset, which could result in invalid register accesses...
PT-2025-18530 · Linux +1 · Linux Kernel +1
Name of the Vulnerable Software and Affected Versions: Linux kernel affected versions not specified Description: The issue concerns error handling in the ena init function. Specifically, when pci register driver fails, ena init does not destroy the workqueue created by create singlethread...
PT-2025-18632 · Linux +1 · Linux Kernel +1
Name of the Vulnerable Software and Affected Versions: Linux kernel affected versions not specified Description: A possible memory leak in the mISDN register device function has been fixed. The issue occurred after a commit where the device name is allocated dynamically. To resolve this, put devi...