23747 matches found
CVE-2025-38381
In the Linux kernel, the following vulnerability has been resolved: Input: cs40l50-vibra - fix potential NULL dereference in cs40l50uploadowt The cs40l50uploadowt function allocates memory via kmalloc without checking for allocation failure, which could lead to a NULL pointer dereference. Return...
CVE-2025-38381 Input: cs40l50-vibra - fix potential NULL dereference in cs40l50_upload_owt()
In the Linux kernel, the following vulnerability has been resolved: Input: cs40l50-vibra - fix potential NULL dereference in cs40l50uploadowt The cs40l50uploadowt function allocates memory via kmalloc without checking for allocation failure, which could lead to a NULL pointer dereference. Return...
CVE-2025-38381
In the Linux kernel, the following vulnerability has been resolved: Input: cs40l50-vibra - fix potential NULL dereference in cs40l50uploadowt The cs40l50uploadowt function allocates memory via kmalloc without checking for allocation failure, which could lead to a NULL pointer dereference. Return...
CVE-2025-38381
The CVE-2025-38381 issue affects the Linux kernel codepath handling cs40l50 uploads. Specifically, in cs40l50_upload_owt(), memory allocated via kmalloc() is not checked for allocation failure, which can lead to a NULL pointer dereference. The fix adds a NULL check and returns -ENOMEM on allocati...
CVE-2025-38373 IB/mlx5: Fix potential deadlock in MR deregistration
In the Linux kernel, the following vulnerability has been resolved: IB/mlx5: Fix potential deadlock in MR deregistration The issue arises when kzalloc is invoked while holding umemmutex or any other lock acquired under umemmutex. This is problematic because kzalloc can trigger fsreclaimaqcuire,...
CVE-2025-38373
In the Linux kernel, the following vulnerability has been resolved: IB/mlx5: Fix potential deadlock in MR deregistration The issue arises when kzalloc is invoked while holding umemmutex or any other lock acquired under umemmutex. This is problematic because kzalloc can trigger fsreclaimaqcuire,...
CVE-2025-38369
In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: Check availability of workqueue allocated by idxd wq driver before using Running IDXD workloads in a container with the /dev directory mounted can trigger a call trace or even a kernel panic when the parent proce...
CVE-2025-38369 dmaengine: idxd: Check availability of workqueue allocated by idxd wq driver before using
In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: Check availability of workqueue allocated by idxd wq driver before using Running IDXD workloads in a container with the /dev directory mounted can trigger a call trace or even a kernel panic when the parent proce...
CVE-2025-38364
CVE-2025-38364 pertains to Linux kernel Maple_tree: MA_STATE_PREALLOC handling in mas_preallocate. The flaw prevented allocations when MA_STATE_PREALLOC was set; preallocation checks could undercount, leading to a WARN_ON() and a subsequent null pointer dereference on larger future requests (e.g....
CVE-2025-38364 maple_tree: fix MA_STATE_PREALLOC flag in mas_preallocate()
In the Linux kernel, the following vulnerability has been resolved: mapletree: fix MASTATEPREALLOC flag in maspreallocate Temporarily clear the preallocation flag when explicitly requesting allocations. Pre-existing allocations are already counted against the request through masnodecountgfp, but...
CVE-2025-38363 drm/tegra: Fix a possible null pointer dereference
In the Linux kernel, the following vulnerability has been resolved: drm/tegra: Fix a possible null pointer dereference In tegracrtcreset, new memory is allocated with kzalloc, but no check is performed. Before calling drmatomichelpercrtcreset, state should be checked to prevent possible null...
CVE-2025-38363
In the Linux kernel, the following vulnerability has been resolved: drm/tegra: Fix a possible null pointer dereference In tegracrtcreset, new memory is allocated with kzalloc, but no check is performed. Before calling drmatomichelpercrtcreset, state should be checked to prevent possible null...
CVE-2025-5253 DoS in Kron Technologies' Kron PAM
Allocation of Resources Without Limits or Throttling vulnerability in Kron Technologies Kron PAM allows HTTP DoS. This issue affects Kron PAM: before 3.7...
CVE-2025-5253
CVE-2025-5253 affects Kron Technologies’ Kron PAM prior to version 3.7. The issue is described as an HTTP DoS caused by unrestricted resource allocation (or throttling), enabling resource exhaustion under HTTP requests. Affected component is Kron PAM’s HTTP handling; product/version details indic...
CVE-2025-5253
Allocation of Resources Without Limits or Throttling vulnerability in Kron Technologies Kron PAM allows HTTP DoS. This issue affects Kron PAM: before 3.7...
CVE-2025-5253 DoS in Kron Technologies' Kron PAM
Allocation of Resources Without Limits or Throttling vulnerability in Kron Technologies Kron PAM allows HTTP DoS. This issue affects Kron PAM: before 3.7...
OESA-2025-1876 kernel security update
The Linux Kernel, the operating system core itself. Security Fixes: In the Linux kernel, the following vulnerability has been resolved: bpf: Do markchainprecision for ARGCONSTALLOCSIZEORZERO Precision markers need to be propagated whenever we have an ARGCONST style argument, as the verifier canno...
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 failure to check if the receive length exceeds the allocated size potentially resulting in an out-of-bound...
Kron PAM 安全漏洞
Kron PAM is a privileged access management platform from Kron Turkey. A security vulnerability exists in Kron PAM that stems from unrestricted resource allocation or throttling, which could lead to an HTTP denial of service...
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 call to kzalloc during umemmutex locking that could result in a deadlock...