280 matches found
CVE-2022-49101
CVE-2022-49101 entry is rejected by the CVE Numbering Authority and does not represent an active vulnerability.
PT-2025-14358
Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description A hang issue in the kdump kernel has been resolved when running on Hyper-V Gen 2 VMs. The problem occurs when the hyperv fb driver moves the framebuffer to a different MMIO address due t...
AZL-56800 CVE-2025-21694 affecting package kernel for versions less than 5.15.180.1-1
In the Linux kernel, the following vulnerability has been resolved: fs/proc: fix softlockup in readvmcore part 2 Since commit 5cbcb62dddf5 "fs/proc: fix softlockup in readvmcore" the number of softlockups in readvmcore at kdump time have gone down, but they still happen sometimes. In a memory...
CVE-2025-21694
In the Linux kernel, the following vulnerability has been resolved: fs/proc: fix softlockup in readvmcore part 2 Since commit 5cbcb62dddf5 "fs/proc: fix softlockup in readvmcore" the number of softlockups in readvmcore at kdump time have gone down, but they still happen sometimes. In a memory...
DEBIAN-CVE-2025-21694
In the Linux kernel, the following vulnerability has been resolved: fs/proc: fix softlockup in readvmcore part 2 Since commit 5cbcb62dddf5 "fs/proc: fix softlockup in readvmcore" the number of softlockups in readvmcore at kdump time have gone down, but they still happen sometimes. In a memory...
UBUNTU-CVE-2025-21694
In the Linux kernel, the following vulnerability has been resolved: fs/proc: fix softlockup in readvmcore part 2 Since commit 5cbcb62dddf5 "fs/proc: fix softlockup in readvmcore" the number of softlockups in readvmcore at kdump time have gone down, but they still happen sometimes. In a memory...
CVE-2025-21694 fs/proc: fix softlockup in __read_vmcore (part 2)
In the Linux kernel, the following vulnerability has been resolved: fs/proc: fix softlockup in readvmcore part 2 Since commit 5cbcb62dddf5 "fs/proc: fix softlockup in readvmcore" the number of softlockups in readvmcore at kdump time have gone down, but they still happen sometimes. In a memory...
CVE-2025-21694
In the Linux kernel, the following vulnerability has been resolved: fs/proc: fix softlockup in readvmcore part 2 Since commit 5cbcb62dddf5 "fs/proc: fix softlockup in readvmcore" the number of softlockups in readvmcore at kdump time have gone down, but they still happen sometimes. In a memory...
CVE-2025-21694
CVE-2025-21694 : Linux kernel vulnerability in fs/proc/__read_vmcore (kdump path). Root cause: second loop in __read_vmcore could still hit softlockups; fix adds cond_resched() to yield in that loop. Impact: softlockups may interfere with RCU memory freeing and cause crashdump stalls in memory-co...
CVE-2025-21694 fs/proc: fix softlockup in __read_vmcore (part 2)
In the Linux kernel, the following vulnerability has been resolved: fs/proc: fix softlockup in readvmcore part 2 Since commit 5cbcb62dddf5 "fs/proc: fix softlockup in readvmcore" the number of softlockups in readvmcore at kdump time have gone down, but they still happen sometimes. In a memory...
CVE-2025-21664
CVE-2025-21664 affects the Linux kernel dm-thin component. Root cause: get_first_thin did a non-RCU-safe sequence (list_empty -> list_first) that could race with concurrent updates, risking dereferencing a stale/altered list head during process_deferred_bios flow and leading to a crash. Connec...
CVE-2022-49003 nvme: fix SRCU protection of nvme_ns_head list
In the Linux kernel, the following vulnerability has been resolved: nvme: fix SRCU protection of nvmenshead list Walking the nvmenshead siblings list is protected by the head's srcu in nvmensheadsubmitbio but not nvmempathrevalidatepaths. Removing namespaces from the list also fails to synchroniz...
CVE-2022-49003 nvme: fix SRCU protection of nvme_ns_head list
In the Linux kernel, the following vulnerability has been resolved: nvme: fix SRCU protection of nvmenshead list Walking the nvmenshead siblings list is protected by the head's srcu in nvmensheadsubmitbio but not nvmempathrevalidatepaths. Removing namespaces from the list also fails to synchroniz...
CBL Mariner 2.0 Security Update: kernel (CVE-2024-26929)
The version of kernel installed on the remote CBL Mariner 2.0 host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the CVE-2024-26929 advisory. - NIST NVD Details CVE-2024-26929 Note that Nessus has not tested for this issue but has instead relied only o...
kexec-tools bug fix update
An update is available for kexec-tools. This update affects Rocky Linux 9. A Common Vulnerability Scoring System CVSS base score, which gives a detailed severity rating, is available for each vulnerability from the CVE list The kexec-tools packages contain the /sbin/kexec binary and utilities tha...
kernel: efi: fix panic in kdump kernel
In the Linux kernel, the following vulnerability has been resolved: efi: fix panic in kdump kernel The Linux kernel CVE team has assigned CVE-2024-35800 to this issue. Upstream advisory: https://lore.kernel.org/linux-cve-announce/2024051738-CVE-2024-35800-219a@gregkh/T...
kernel: mlxbf_gige: call request_irq() after NAPI initialized
CVE-2024-35907 is a vulnerability in the Linux kernel's mlxbfgige driver, which supports Mellanox BlueField devices. The issue occurs during kdump operations when a receive RX interrupt is triggered before the driver fully initializes. This leads to a race condition that can result in a NULL...
kernel: mlxbf_gige: call request_irq() after NAPI initialized
CVE-2024-35907 is a vulnerability in the Linux kernel's mlxbfgige driver, which supports Mellanox BlueField devices. The issue occurs during kdump operations when a receive RX interrupt is triggered before the driver fully initializes. This leads to a race condition that can result in a NULL...
kernel: mlxbf_gige: call request_irq() after NAPI initialized
CVE-2024-35907 is a vulnerability in the Linux kernel's mlxbfgige driver, which supports Mellanox BlueField devices. The issue occurs during kdump operations when a receive RX interrupt is triggered before the driver fully initializes. This leads to a race condition that can result in a NULL...