VulDB Recent Entries

A vulnerability labeled as problematic has been found in Google Android 16-qpr2. Affected by this vulnerability is the function preparePackage of the file InstallPackageHelper.java. Such manipulation leads to Local Privilege Escalation. This vulnerability is uniquely identified as CVE-2025-48606. Local access is required to approach this attack. No exploit exists. It is best practice to apply a patch to resolve this issue.

A vulnerability identified as problematic has been detected in Google Android 13/14/15/16. Affected is the function disassociate of the file DisassociationProcessor.java. This manipulation causes improper input validation. This vulnerability is handled as CVE-2025-48525. It is possible to launch the attack on the local host. There is not any exploit available.

A vulnerability categorized as critical has been discovered in Google Android 13/14/15/16. This impacts the function grantAllowlistedPackagePermissions of the file SettingsSliceProvider.java. The manipulation results in permission issues. This vulnerability is known as CVE-2025-48536. Attacking locally is a requirement. No exploit is available.

A vulnerability was found in HummerRisk up to 1.5.0. It has been rated as critical. This affects an unknown function of the component Snakeyaml. The manipulation leads to privilege escalation. This vulnerability is traded as CVE-2025-63721. It is possible to initiate the attack remotely. There is no exploit available.

A vulnerability was found in Google Android kernel. It has been declared as critical. The impacted element is an unknown function of the file mem_protect.c. Executing manipulation can lead to out-of-bounds write. This vulnerability appears as CVE-2025-48637. The attack requires local access. There is no available exploit.

A vulnerability was found in Google Android kernel. It has been classified as critical. The affected element is the function __pkvm_load_tracing of the file trace.c. Performing manipulation results in out-of-bounds write. This vulnerability is reported as CVE-2025-48638. The attack requires a local approach. No exploit exists.

A vulnerability was found in Google Android kernel and classified as critical. Impacted is an unknown function of the file arm-smmu-v3.c. Such manipulation leads to out-of-bounds write. This vulnerability is documented as CVE-2025-48624. The attack needs to be performed locally. There is not any exploit available.

A vulnerability has been found in Google Android 16 and classified as critical. This issue affects the function ensureBound of the file RemotePrintService.java. This manipulation causes permission issues. This vulnerability is registered as CVE-2025-32319. Remote exploitation of the attack is possible. No exploit is available.

A vulnerability, which was classified as problematic, was found in Google Android 13/14. This vulnerability affects the function startNextMatchingActivity of the file ActivityTaskManagerService.java. The manipulation results in Local Privilege Escalation. This vulnerability is cataloged as CVE-2025-48627. The attack must be initiated from a local position. There is no exploit available.

A vulnerability, which was classified as problematic, has been found in Google Android 13/14/15/16. This affects the function hasAccountsOnAnyUser of the file DevicePolicyManagerService.java. The manipulation leads to Local Privilege Escalation. This vulnerability is listed as CVE-2025-48633. The attack must be carried out locally. In addition, an exploit is available.

A vulnerability classified as problematic was found in Google Android 13/14/15/16. Affected by this issue is the function verifyAndGetBypass of the file AppOpsService.java. Executing manipulation can lead to resource consumption. This vulnerability is tracked as CVE-2025-48590. The attack is restricted to local execution. No exploit exists.

A vulnerability classified as problematic has been found in Google Android 13/14/15/16. Affected by this vulnerability is the function validateIconUserBoundary of the file PrintManagerService.java. Performing manipulation results in Local Privilege Escalation. This vulnerability is identified as CVE-2025-48628. The attack is only possible with local access. There is not any exploit available.

A vulnerability described as problematic has been identified in Google Android 14/15/16. Affected is the function setDisplayName of the file AssociationRequest.java. Such manipulation leads to improper input validation. This vulnerability is referenced as CVE-2025-48632. The attack can only be performed from a local environment. No exploit is available.

A vulnerability marked as problematic has been reported in Google Android 13/14/15/16. This impacts the function onSomePackagesChanged of the file VoiceInteractionManagerService.java. This manipulation causes Local Privilege Escalation. The identification of this vulnerability is CVE-2025-48620. The attack can only be executed locally. There is no exploit available.

A vulnerability labeled as critical has been found in Google Android kernel. This affects the function init_pkvm_hyp_vcpu of the file pkvm.c. The manipulation results in out-of-bounds write. This vulnerability was named CVE-2025-48623. The attack needs to be approached locally. There is no available exploit.

A vulnerability identified as problematic has been detected in Google Android 13/14/15/16. The impacted element is an unknown function of the file DefaultTransitionHandler.java. The manipulation leads to improper restriction of rendered ui layers. This vulnerability is uniquely identified as CVE-2025-48621. The attack is possible to be carried out remotely. No exploit exists.

A vulnerability categorized as problematic has been discovered in Google Android 13/14/15. The affected element is the function startAlwaysOnVpn of the file Vpn.java. Executing manipulation can lead to Local Privilege Escalation. This vulnerability is handled as CVE-2025-48588. It is possible to launch the attack on the local host. There is not any exploit available.

A vulnerability was found in Google Android 13/14/15/16. It has been rated as problematic. Impacted is the function processLaunchBrowser of the file CommandParamsFactory.java of the component Lockscreen. Performing manipulation results in improper locking. This vulnerability is known as CVE-2025-48618. The attack may be carried out on the physical device. No exploit is available.

A vulnerability was found in Google Android 13/14/15/16. It has been declared as problematic. This issue affects the function rebootWipeUserData of the file RecoverySystem.java of the component Factory Reset Handler. Such manipulation leads to denial of service. This vulnerability is traded as CVE-2025-48614. The attack can be executed directly on the physical device. There is no exploit available.

A vulnerability was found in Google Android 13/14/15/16. It has been classified as problematic. This vulnerability affects unknown code of the component NFC Payment. This manipulation causes improper input validation. This vulnerability appears as CVE-2025-48612. The attack requires local access. There is no available exploit.