Export limit exceeded: 419554 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.

Export limit exceeded: 419554 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.

Export limit exceeded: 419554 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.

Search

Search Results (419554 CVEs found)

CVE Vendors Products Updated CVSS v3.1
CVE-2026-48176 2026-11-05 N/A
A memory corruption vulnerability caused by improper validation of messages
CVE-2026-33969 2026-11-05 N/A
In the NAS Authentication Request message decoding procedure, a missing lower bound check causes an infinite loop, leading to Denial of Service.
CVE-2026-69006 2026-11-05 N/A
Insufficient validation of length fields in the GNSS firmware loader can result in kernel‑memory corruption.
CVE-2026-69005 2026-11-05 N/A
Integer overflow in NPU driver parameter processing due to insufficient bounds checking.
CVE-2025-66366 2026-11-05 N/A
Incorrect handling of unauthenticated downlink RRC Setup messages can cause the baseband to crash
CVE-2026-68991 2026-11-05 N/A
In the Samsung Exynos ENN NeuralNetworks HAL, improper input validation during request processing can cause memory corruption and lead to a denial of service condition.
CVE-2026-68990 2026-11-05 N/A
In the Samsung Exynos H-Arx DRM plugin, improper input validation during buffer operations can cause memory corruption, potentially leading to denial of service or privilege escalation.
CVE-2026-68993 2026-11-05 N/A
A double free vulnerability in NPU driver due to improper pointer management (940)
CVE-2026-48178 2026-11-05 N/A
Out of bound access in PPC due to race condition in global variable access
CVE-2026-48174 2026-11-05 N/A
In the NR RRC component, improper handling of messages before authentication triggers a data abort, which leads to a denial‑of‑service condition.
CVE-2026-48173 2026-11-05 N/A
In the NAS message handler, improper validation of the length field in NAS message causes memory corruption
CVE-2025-66365 2026-11-05 N/A
Incorrect handling of SIP packets leads to baseband crashes
CVE-2026-122992 2026-11-05 N/A
In G4KLX DStarGateway and F4FXL DStarGateway before 7b75de6, dstarCallsignToAPRS in APRSUtils.cpp has an integer underflow via an empty RS-MS1A sender field.
CVE-2026-35495 2026-11-05 N/A
In IMS stack, improper handling of SIP packets leads to Incorrect_Access_Control vulnerability
CVE-2025-66368 2026-11-05 N/A
Incorrect handling of SDP payload leads to a Denial of Service
CVE-2026-69025 2026-11-05 N/A
In the Exynos NPU driver, improper validation of user input in the ioctl handler can lead to an out-of-bounds write, which causes a denial of service
CVE-2026-122236 1 Openhands 1 Openhands 2026-11-05 6.3 Medium
A vulnerability has been found in OpenHands up to 1.24.0. This impacts an unknown function of the component Landing Page. Such manipulation leads to missing authentication. The attack must be carried out from within the local network. The exploit has been disclosed to the public and may be used. Upgrading to version 1.25.0 will fix this issue. The name of the patch is c5efa3ae415def0a903c82d2b17b748e663b1995. Upgrading the affected component is recommended.
CVE-2026-99232 1 Linux 2 Linux, Linux Kernel 2026-11-05 4.7 Medium
In the Linux kernel, the following vulnerability has been resolved: tracing/syscalls: Use copy_from_user for the faultable syscall buffer syscall_copy_user_array() copies the buffer argument of faultable syscalls (write, pwrite64, ...) with __copy_from_user(), which skips access_ok(). Use copy_from_user() instead so a non-user address is rejected and the entry is recorded as faulted. It could be a security concern for machines that trust perf a bit too much.
CVE-2026-99244 1 Linux 2 Linux, Linux Kernel 2026-11-05 3.3 Low
In the Linux kernel, the following vulnerability has been resolved: pid_namespace: prevent TIF_NOTIFY_SIGNAL from interrupting the reaper Since commit 7fea700e04bd ("zap_pid_ns_processes: clear TIF_NOTIFY_SIGNAL along with TIF_SIGPENDING") zap_pid_ns_processes() clears TIF_NOTIFY_SIGNAL before every kernel_wait4() call. Otherwise kernel_wait4() doesn't sleep and returns -ERESTARTSYS if signal_pending() is true and the reaper busy-waits. But clearing TIF_NOTIFY_SIGNAL doesn't fix it. It can get raised again. For example, klp_send_signals() sets it raw against any task that hasn't transitioned yet. And it keeps sending it until the livepatch finishes. The sleep loop waiting for pid_allocated to drop has the same problem and it doesn't even clear anything. So a schedule() in TASK_INTERRUPTIBLE returns immediately. Use a no_notify_signal guard. signal_pending() will ignore TIF_NOTIFY_SIGNAL and the pid namespace reaper sleeps until a child exits or free_pid() wakes it.
CVE-2026-48179 2026-11-05 N/A
In the Exynos modem's IMS stack, improper handling of SDP payload leads to a Denial of Service