Filtered by NVD-CWE-noinfo
Total 34060 CVE
CVE Vendors Products Updated CVSS v3.1
CVE-2024-27837 1 Apple 1 Macos 2025-12-16 7.7 High
A downgrade issue was addressed with additional code-signing restrictions. This issue is fixed in macOS Sonoma 14.5. A local attacker may gain access to Keychain items.
CVE-2024-27825 1 Apple 1 Macos 2025-12-16 7.8 High
A downgrade issue affecting Intel-based Mac computers was addressed with additional code-signing restrictions. This issue is fixed in macOS Sonoma 14.5. An app may be able to bypass certain Privacy preferences.
CVE-2024-27796 1 Apple 4 Ipad Os, Ipados, Iphone Os and 1 more 2025-12-16 8.1 High
The issue was addressed with improved checks. This issue is fixed in iOS 17.5 and iPadOS 17.5, macOS Sonoma 14.5. An attacker may be able to elevate privileges.
CVE-2024-23708 1 Google 1 Android 2025-12-16 9.8 Critical
In multiple functions of NotificationManagerService.java, there is a possible way to not show a toast message when a clipboard message has been accessed. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
CVE-2024-23706 1 Google 1 Android 2025-12-16 7.4 High
In multiple locations, there is a possible bypass of health data permissions due to an improper input validation. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
CVE-2024-23705 1 Google 1 Android 2025-12-16 9.8 Critical
In multiple locations, there is a possible failure to persist or enforce user restrictions due to improper input validation. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation.
CVE-2024-20015 2 Google, Mediatek 40 Android, Mt6739, Mt6753 and 37 more 2025-12-16 7.4 High
In telephony, there is a possible escalation of privilege due to a permissions bypass. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS08441419; Issue ID: ALPS08441419.
CVE-2024-21888 1 Ivanti 2 Connect Secure, Policy Secure 2025-12-16 8.8 High
A privilege escalation vulnerability in web component of Ivanti Connect Secure (9.x, 22.x) and Ivanti Policy Secure (9.x, 22.x) allows a user to elevate privileges to that of an administrator.
CVE-2021-3453 1 Lenovo 42 730s-13iml, 730s-13iml Firmware, Ideacentre Aio 5-24imb05 and 39 more 2025-12-16 6.8 Medium
Some Lenovo Notebook, ThinkPad, and Lenovo Desktop systems have BIOS modules unprotected by Intel Boot Guard that could allow an attacker with physical access the ability to write to the SPI flash storage.
CVE-2022-29126 1 Microsoft 19 Windows 10, Windows 10 1507, Windows 10 1607 and 16 more 2025-12-16 7 High
Tablet Windows User Interface Application Core Elevation of Privilege Vulnerability
CVE-2022-29106 1 Microsoft 5 Windows 10, Windows Server 2016, Windows Server 2019 and 2 more 2025-12-16 7 High
Windows Hyper-V Shared Virtual Disk Elevation of Privilege Vulnerability
CVE-2022-26917 1 Microsoft 22 Windows 10, Windows 10 1507, Windows 10 1607 and 19 more 2025-12-16 7.8 High
Windows Fax Compose Form Remote Code Execution Vulnerability
CVE-2025-38336 2 Debian, Linux 2 Debian Linux, Linux Kernel 2025-12-16 5.5 Medium
In the Linux kernel, the following vulnerability has been resolved: ata: pata_via: Force PIO for ATAPI devices on VT6415/VT6330 The controller has a hardware bug that can hard hang the system when doing ATAPI DMAs without any trace of what happened. Depending on the device attached, it can also prevent the system from booting. In this case, the system hangs when reading the ATIP from optical media with cdrecord -vvv -atip on an _NEC DVD_RW ND-4571A 1-01 and an Optiarc DVD RW AD-7200A 1.06 attached to an ASRock 990FX Extreme 4, running at UDMA/33. The issue can be reproduced by running the same command with a cygwin build of cdrecord on WinXP, although it requires more attempts to cause it. The hang in that case is also resolved by forcing PIO. It doesn't appear that VIA has produced any drivers for that OS, thus no known workaround exists. HDDs attached to the controller do not suffer from any DMA issues.
CVE-2022-26916 1 Microsoft 22 Windows 10, Windows 10 1507, Windows 10 1607 and 19 more 2025-12-16 7.8 High
Windows Fax Compose Form Remote Code Execution Vulnerability
CVE-2022-24494 1 Microsoft 22 Windows 10, Windows 10 1507, Windows 10 1607 and 19 more 2025-12-16 7.8 High
Windows Ancillary Function Driver for WinSock Elevation of Privilege Vulnerability
CVE-2022-24489 1 Microsoft 4 Windows Server 2016, Windows Server 2019, Windows Server 2022 and 1 more 2025-12-16 7.8 High
Cluster Client Failover (CCF) Elevation of Privilege Vulnerability
CVE-2022-30165 1 Microsoft 12 Windows 10, Windows 10 1607, Windows 10 1809 and 9 more 2025-12-16 8.8 High
Windows Kerberos Elevation of Privilege Vulnerability
CVE-2022-24549 1 Microsoft 14 Windows 10, Windows 10 1507, Windows 10 1607 and 11 more 2025-12-16 7.8 High
Windows AppX Package Manager Elevation of Privilege Vulnerability
CVE-2015-10139 1 Vibethemes 1 Wordpress Learning Management System 2025-12-16 8.8 High
The WPLMS theme for WordPress is vulnerable to Privilege Escalation in versions 1.5.2 to 1.8.4.1 via the 'wp_ajax_import_data' AJAX action. This makes it possible for authenticated attackers to change otherwise restricted settings and potentially create a new accessible admin account.
CVE-2025-38354 2 Debian, Linux 2 Debian Linux, Linux Kernel 2025-12-16 5.5 Medium
In the Linux kernel, the following vulnerability has been resolved: drm/msm/gpu: Fix crash when throttling GPU immediately during boot There is a small chance that the GPU is already hot during boot. In that case, the call to of_devfreq_cooling_register() will immediately try to apply devfreq cooling, as seen in the following crash: Unable to handle kernel paging request at virtual address 0000000000014110 pc : a6xx_gpu_busy+0x1c/0x58 [msm] lr : msm_devfreq_get_dev_status+0xbc/0x140 [msm] Call trace: a6xx_gpu_busy+0x1c/0x58 [msm] (P) devfreq_simple_ondemand_func+0x3c/0x150 devfreq_update_target+0x44/0xd8 qos_max_notifier_call+0x30/0x84 blocking_notifier_call_chain+0x6c/0xa0 pm_qos_update_target+0xd0/0x110 freq_qos_apply+0x3c/0x74 apply_constraint+0x88/0x148 __dev_pm_qos_update_request+0x7c/0xcc dev_pm_qos_update_request+0x38/0x5c devfreq_cooling_set_cur_state+0x98/0xf0 __thermal_cdev_update+0x64/0xb4 thermal_cdev_update+0x4c/0x58 step_wise_manage+0x1f0/0x318 __thermal_zone_device_update+0x278/0x424 __thermal_cooling_device_register+0x2bc/0x308 thermal_of_cooling_device_register+0x10/0x1c of_devfreq_cooling_register_power+0x240/0x2bc of_devfreq_cooling_register+0x14/0x20 msm_devfreq_init+0xc4/0x1a0 [msm] msm_gpu_init+0x304/0x574 [msm] adreno_gpu_init+0x1c4/0x2e0 [msm] a6xx_gpu_init+0x5c8/0x9c8 [msm] adreno_bind+0x2a8/0x33c [msm] ... At this point we haven't initialized the GMU at all yet, so we cannot read the GMU registers inside a6xx_gpu_busy(). A similar issue was fixed before in commit 6694482a70e9 ("drm/msm: Avoid unclocked GMU register access in 6xx gpu_busy"): msm_devfreq_init() does call devfreq_suspend_device(), but unlike msm_devfreq_suspend(), it doesn't set the df->suspended flag accordingly. This means the df->suspended flag does not match the actual devfreq state after initialization and msm_devfreq_get_dev_status() will end up accessing GMU registers, causing the crash. Fix this by setting df->suspended correctly during initialization. Patchwork: https://patchwork.freedesktop.org/patch/650772/