15745 matches found
CVE-2025-37782
In the Linux kernel, the following vulnerability has been resolved: hfs/hfsplus: fix slab-out-of-bounds in hfsbnodereadkey Syzbot reported an issue in hfs subsystem: BUG: KASAN: slab-out-of-bounds in memcpyfrompage include/linux/highmem.h:423 inline BUG: KASAN: slab-out-of-bounds in hfsbnoderead...
DEBIAN-CVE-2025-37772
In the Linux kernel, the following vulnerability has been resolved: RDMA/cma: Fix workqueue crash in cmaneteventworkhandler struct rdmacmid has member "struct workstruct network" that is reused for enqueuing cmaneteventworkhandlers onto cmawq. Below crash1 can occur if more than one call to...
UBUNTU-CVE-2025-37772
In the Linux kernel, the following vulnerability has been resolved: RDMA/cma: Fix workqueue crash in cmaneteventworkhandler struct rdmacmid has member "struct workstruct network" that is reused for enqueuing cmaneteventworkhandlers onto cmawq. Below crash1 can occur if more than one call to...
CVE-2022-49886
The CVE-2022-49886 issue affects the Linux kernel related to x86/tdx memory handling. The vulnerability stems from how private memory (TDX private memory, including kernel stacks/text) may trigger a virtualization exception (#VE) and the difficulty of handling such exceptions. The root cause desc...
CVE-2022-49886
In the Linux kernel, the following vulnerability has been resolved: x86/tdx: Panic on bad configs that VE on "private" memory access All normal kernel memory is "TDX private memory". This includes everything from kernel stacks to kernel text. Handling exceptions on arbitrary accesses to kernel...
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...
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...
CVE-2022-49799
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...
CVE-2022-49788 misc/vmw_vmci: fix an infoleak in vmci_host_do_receive_datagram()
In the Linux kernel, the following vulnerability has been resolved: misc/vmwvmci: fix an infoleak in vmcihostdoreceivedatagram struct vmcieventqp allocated by qpnotifypeer contains padding, which may carry uninitialized data to the userspace, as observed by KMSAN: BUG: KMSAN: kernel-infoleak in...
CVE-2025-23141
In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Acquire SRCU in KVMGETMPSTATE to protect guest memory accesses Acquire a lock on kvm-srcu when userspace is getting MP state to handle a rather extreme edge case where "accepting" APIC events, i.e. processing pending IN...
UBUNTU-CVE-2025-23141
In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Acquire SRCU in KVMGETMPSTATE to protect guest memory accesses Acquire a lock on kvm-srcu when userspace is getting MP state to handle a rather extreme edge case where "accepting" APIC events, i.e. processing pending IN...
CVE-2025-37782
CVE-2025-37782 affects the kernel package for versions earlier than 6.6.92.2-1. An upgraded kernel version (≥ 6.6.92.2-1) resolves the issue. No exploit details are provided in the connected documents. If using affected distributions, upgrade to the specified kernel version to mitigate.
CVE-2025-37778
CVE-2025-37778 is a Linux kernel vulnerability in ksmbd’s krb_authenticate path. The root cause is a use-after-free: krb_authenticate frees sess->user and may not NULL it; if ksmbd_krb5_authenticate does not reinitialize sess->user, smb2_sess_setup may later access freed memory. Several adv...
CVE-2025-37778 ksmbd: Fix dangling pointer in krb_authenticate
In the Linux kernel, the following vulnerability has been resolved: ksmbd: Fix dangling pointer in krbauthenticate krbauthenticate frees sess-user and does not set the pointer to NULL. It calls ksmbdkrb5authenticate to reinitialise sess-user but that function may return without doing so. If that...
CVE-2025-23158 media: venus: hfi: add check to handle incorrect queue size
In the Linux kernel, the following vulnerability has been resolved: media: venus: hfi: add check to handle incorrect queue size qsize represents size of shared queued between driver and video firmware. Firmware can modify this value to an invalid large value. In such situation, emptyspace will be...
CVE-2025-23141 KVM: x86: Acquire SRCU in KVM_GET_MP_STATE to protect guest memory accesses
In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Acquire SRCU in KVMGETMPSTATE to protect guest memory accesses Acquire a lock on kvm-srcu when userspace is getting MP state to handle a rather extreme edge case where "accepting" APIC events, i.e. processing pending IN...
CVE-2025-23141
CVE-2025-23141: In the Linux kernel KVM x86, acquiring the SRCU lock when retrieving MP state (KVM_GET_MP_STATE) can trigger a nested VM-Exit and potentially access guest memory in edge cases (e.g., L2 with INIT and pending TRIPLE_FAULT). The issue arises when the vCPU handling of MP state intera...
CVE-2025-23141 KVM: x86: Acquire SRCU in KVM_GET_MP_STATE to protect guest memory accesses
In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Acquire SRCU in KVMGETMPSTATE to protect guest memory accesses Acquire a lock on kvm-srcu when userspace is getting MP state to handle a rather extreme edge case where "accepting" APIC events, i.e. processing pending IN...