| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| A double free vulnerability in NPU driver due to improper pointer management (940) |
| Out of bound access in PPC due to race condition in global variable access |
| In the NR RRC component, improper handling of messages before authentication triggers a data abort, which leads to a denial‑of‑service condition. |
| In the NAS message handler, improper validation of the length field in NAS message causes memory corruption |
| Incorrect handling of SIP packets leads to baseband crashes |
| In G4KLX DStarGateway and F4FXL DStarGateway before 7b75de6, dstarCallsignToAPRS in APRSUtils.cpp has an integer underflow via an empty RS-MS1A sender field. |
| In IMS stack, improper handling of SIP packets leads to Incorrect_Access_Control vulnerability |
| Incorrect handling of SDP payload leads to a Denial of Service |
| 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 |
| 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. |
| 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. |
| 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. |
| In the Exynos modem's IMS stack, improper handling of SDP payload leads to a Denial of Service |
| Processing a malformed RRC Reconfiguration message leads to an out-of-bounds (OOB) access, resulting in a denial-of-service (DoS) condition. |
| An attacker may send a malicious IMS message to the target device, potentially leading to information exposure through the SIP message flow. |
| In the Samsung GPU driver, improper reference count handling during command submission can lead to memory corruption. |
| In the Samsung Exynos GPU driver, improper synchronization during buffer object creation and closing can lead to memory corruption |
| Out-of-bounds memory access in a device driver due to improper resource state tracking. |
| Memory corruption in GPU driver due to improper validation of VMID reservation. |
| Incorrect authorization in Samsung framework services due to missing permission checks |
