Vuldb Updates

A vulnerability was found in Google Android kernel. It has been rated as problematic. Affected is the function __pkvm_guest_relinquish_to_host of the file mem_protect.c. The manipulation leads to information disclosure. This vulnerability is uniquely identified as CVE-2025-48610. Local access is required to approach this attack. No exploit exists.

A vulnerability classified as problematic was found in Google Android 13/14/15/16. The affected element is an unknown function. The manipulation results in information disclosure. This vulnerability is cataloged as CVE-2025-48604. The attack must be initiated from a local position. 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.

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 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 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 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 15/16 and classified as problematic. The impacted element is an unknown function. Performing manipulation results in denial of service. This vulnerability is cataloged as CVE-2025-48607. The attack must be initiated from a local position. There is no exploit available.

A vulnerability was found in Google Android 13/14/15/16 and classified as problematic. This affects the function findAvailRecognizer of the file VoiceInteractionManagerService.java. Executing manipulation can lead to insecure default initialization of resource. This vulnerability is registered as CVE-2025-48629. The attack needs to be launched locally. No exploit is available. It is best practice to apply a patch to resolve this issue.

A vulnerability was found in Huawei HarmonyOS and EMUI. It has been classified as critical. Impacted is an unknown function of the component Memory Management Module. Performing manipulation results in race condition. This vulnerability is cataloged as CVE-2025-54629. The attack must be initiated from a local position. There is no exploit available.

A vulnerability was found in Huawei HarmonyOS 5.1.0. It has been rated as problematic. Impacted is an unknown function of the component Card Management Module. The manipulation leads to improper control of resource through lifetime. This vulnerability is listed as CVE-2025-54612. The attack must be carried out locally. There is no available exploit.

A vulnerability categorized as problematic has been discovered in Huawei HarmonyOS 5.1.0. The affected element is an unknown function of the component Card Management Module. The manipulation results in improper control of resource through lifetime. This vulnerability is cataloged as CVE-2025-54613. 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 Huawei HarmonyOS 5.1.0. This affects an unknown part of the component WantAgent Module. This manipulation causes improper control of resource through lifetime. This vulnerability is handled as CVE-2025-54621. It is possible to launch the attack on the local host. There is not any exploit available.

A vulnerability classified as problematic was found in Huawei HarmonyOS 5.0.1/5.1.0/6.0.0. This affects an unknown function of the component Office Service. The manipulation results in download of code without integrity check. This vulnerability is reported as CVE-2025-66334. The attack requires a local approach. No exploit exists.

A vulnerability described as problematic has been identified in Google Android 15/16. Affected by this issue is the function initDecoder of the file C2SoftDav1dDec.cpp. Such manipulation leads to out-of-bounds read. This vulnerability is listed as CVE-2025-48592. The attack may be performed from remote. There is no available exploit.

A vulnerability marked as problematic has been reported in Google Android 13/14/15/16. This vulnerability affects the function appendFrom of the file Parcel.cpp. Performing manipulation results in out-of-bounds read. This vulnerability is identified as CVE-2025-48596. The attack is only possible with local access. There is not any exploit available.

A vulnerability, which was classified as problematic, was found in Google Android 13/14/15/16. This affects the function InputMethodInfo of the file InputMethodInfo.java. Such manipulation leads to resource consumption. This vulnerability is documented as CVE-2025-48603. The attack needs to be performed locally. There is not any exploit available.

A vulnerability has been found in Google Android 13/14 and classified as critical. This impacts an unknown function of the file WifiScanModeActivity.java. Performing manipulation results in permission issues. This vulnerability is reported as CVE-2025-48599. The attack requires a local approach. No exploit exists.

A vulnerability was found in Google Android 15/16. It has been declared as problematic. Affected by this issue is some unknown functionality. The manipulation results in information disclosure. This vulnerability is known as CVE-2025-48600. Attacking locally is a requirement. No exploit is available.

A vulnerability classified as critical was found in Google Android 16. This impacts an unknown function of the component Face Unlock. Such manipulation leads to improper authentication. This vulnerability is listed as CVE-2025-48598. The attack can be executed directly on the physical device. There is no available exploit.