Integer Overflow or Wraparound vulnerability in openEuler kernel on Linux (filesystem modules) allows Forced Integer Overflow.This issue affects openEuler kernel: from 4.19.90 before 4.19.90-2401.3, from 5.10.0-60.18.0 before 5.10.0-183.0.0.

A flaw in the Linux Kernel console driver found. When setting font with malicious data by ioctl PIOFONT, kernel will write memory out of bounds. To trigger the vulnerability user need to have access to console driver like if text mode being used through a generic VGA standard display.

Reference: https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/releases/5.10.127/vt-drop-old-font-ioctls.patch

An attacker who submits a crafted tar file with size in header struct being 0 may be able to trigger an calling of malloc(0) for a variable gnulongname, causing an out-of-bounds read.

An attacker who submits a crafted tar file with size in header struct being 0 may be able to trigger an calling of malloc(0) for a variable gnulonglink, causing an out-of-bounds read.

in OpenHarmony v4.0.0 and prior versions allow a local attacker cause DOS through improper input.

in OpenHarmony v4.0.0 and prior versions

allow an adjacent attacker arbitrary code execution in any apps through use after free.

in OpenHarmony v4.0.0 and prior versions allow a local attacker cause heap overflow through integer overflow.

in OpenHarmony v4.0.0 and prior versions allow a local attacker cause heap overflow through integer overflow.

OpenHarmony-v3.1.2 and prior versions, 3.0.6 and prior versions have an Out-of-bound memory read and write vulnerability in /dev/mmzuserdev device driver. The impact depends on the privileges of the attacker. The unprivileged process run on the device could read out-of-bound memory leading sensitive to information disclosure. The processes with system user UID run on the device would be able to write out-of-bound memory which could lead to unspecified memory corruption.

Last updated 31 March 2025

Last updated 31 March 2025

After tarclose(), libtar.c releases the memory pointed to by pointer t. After tarclose() is called in the list() function, it continues to use pointer t: freelonglinklongname(t->thbuf) . As a result, the released memory is used (use-after-free).

in OpenHarmony v5.1.0 and prior versions allow a local attacker cause DOS through improper input.

in OpenHarmony v5.1.0 and prior versions allow a local attacker arbitrary code execution in pre-installed apps through out-of-bounds write. This vulnerability can be exploited only in restricted scenarios.

in OpenHarmony v5.1.0 and prior versions allow a local attacker arbitrary code execution in pre-installed apps through out-of-bounds write. This vulnerability can be exploited only in restricted scenarios.

in OpenHarmony v5.0.3 and prior versions allow a local attacker cause information improper input. This vulnerability can be exploited only in restricted scenarios.

in OpenHarmony v5.1.0 and prior versions allow a local attacker arbitrary code execution in pre-installed apps through using incompatible type. This vulnerability can be exploited only in restricted scenarios.

in OpenHarmony v6.0 and prior versions allow a local attacker case DOS through missing release of memory.

in OpenHarmony v5.0.3 and prior versions allow a local attacker case sensitive information leak through use of uninitialized resource.

in OpenHarmony v4.1.2 and prior versions allow a local attacker cause DOS through use after free.

in OpenHarmony v4.1.2 and prior versions allow a local attacker cause the device is unable to boot up through out-of-bounds write.

in OpenHarmony v4.1.2 and prior versions allow a local attacker cause information leak through out-of-bounds Read.

in OpenHarmony v5.0.2 and prior versions allow a local attacker cause DOS through out-of-bounds write.

in OpenHarmony v5.0.2 and prior versions allow a local attacker case DOS through missing release of memory.

in OpenHarmony v5.0.2 and prior versions allow a local attacker case DOS through missing release of memory.

in OpenHarmony v5.0.2 and prior versions allow a local attacker arbitrary code execution in pre-installed apps through integer overflow.

in OpenHarmony v5.0.2 and prior versions allow a local attacker cause DOS through out-of-bounds read.

in OpenHarmony v5.0.2 and prior versions allow a local attacker cause DOS through out-of-bounds read.

in OpenHarmony v5.0.2 and prior versions allow a local attacker cause DOS through out-of-bounds read.

in OpenHarmony v5.0.3 and prior versions allow a local attacker arbitrary code execution in tcb through use after free.