A vulnerability classified as problematic was found in OpenHarmony up to 5.0.3. Affected by this vulnerability is an unknown functionality. The manipulation leads to preservation of permissions.
This vulnerability is known as CVE-2025-27247. Local access is required to approach this attack. There is no exploit available.
A vulnerability classified as problematic has been found in OpenHarmony up to 5.0.3. Affected is an unknown function. The manipulation leads to denial of service.
This vulnerability is traded as CVE-2025-27242. An attack has to be approached locally. There is no exploit available.
A vulnerability was found in OpenHarmony up to 5.0.3. It has been rated as problematic. This issue affects some unknown processing. The manipulation leads to denial of service.
The identification of this vulnerability is CVE-2025-27131. The attack needs to be approached locally. There is no exploit available.
A vulnerability was found in OpenHarmony up to 5.0.3. It has been declared as problematic. This vulnerability affects unknown code. The manipulation leads to preservation of permissions.
This vulnerability was named CVE-2025-26693. It is possible to launch the attack on the local host. There is no exploit available.
A vulnerability was found in OpenHarmony up to 5.0.3. It has been classified as problematic. This affects an unknown part. The manipulation leads to preservation of permissions.
This vulnerability is uniquely identified as CVE-2025-26691. Attacking locally is a requirement. There is no exploit available.
A vulnerability was found in OpenHarmony up to 5.0.3 and classified as problematic. Affected by this issue is some unknown functionality. The manipulation leads to null pointer dereference.
This vulnerability is handled as CVE-2025-25217. Local access is required to approach this attack. There is no exploit available.
A vulnerability has been found in OpenHarmony up to 5.0.3 and classified as problematic. Affected by this vulnerability is an unknown functionality. The manipulation leads to race condition.
This vulnerability is known as CVE-2025-24493. An attack has to be approached locally. There is no exploit available.
A vulnerability, which was classified as problematic, was found in OpenHarmony up to 5.0.3. Affected is an unknown function. The manipulation leads to out-of-bounds read.
This vulnerability is traded as CVE-2025-23235. The attack needs to be approached locally. There is no exploit available.
A vulnerability, which was classified as problematic, has been found in OpenHarmony up to 5.0.3. This issue affects some unknown processing. The manipulation leads to type confusion.
The identification of this vulnerability is CVE-2025-21082. It is possible to launch the attack on the local host. There is no exploit available.
A vulnerability classified as problematic was found in OpenHarmony up to 5.0.3. This vulnerability affects unknown code. The manipulation leads to type confusion.
This vulnerability was named CVE-2025-20063. Attacking locally is a requirement. There is no exploit available.
A vulnerability classified as critical has been found in Linux Kernel up to 6.14.8. This affects the function rcu_read_lock of the component can. The manipulation leads to use after free.
This vulnerability is uniquely identified as CVE-2025-38003. The attack can only be initiated within the local network. There is no exploit available.
It is recommended to upgrade the affected component.
A vulnerability was found in Linux Kernel up to 6.14.8. It has been rated as problematic. Affected by this issue is the function bcm_can_tx of the component can. The manipulation of the argument Count leads to out-of-bounds read.
This vulnerability is handled as CVE-2025-38004. The attack can only be done within the local network. There is no exploit available.
It is recommended to upgrade the affected component.