CVE-2022-41686: OpenHarmony-v3.1.2 and prior versions, 3.0.6 and prior versions have an Out-of-bound memory read and write vul

Q: How do I fix CVE-2022-41686?

openharmony: upgrade to newer than 3.0.6; openharmony: upgrade to newer than 3.1.2. Exact commands for each OS are on this page.

Q: Is CVE-2022-41686 being exploited?

CVE-2022-41686 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-41686 affect?

CVE-2022-41686 affects openharmony, openharmony. Severity is medium (CVSS 5.1). 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/mmz_userdev device driver. The impact depends on the privileges of the attacker. The unprivileged process run o

Q: How urgent is CVE-2022-41686?

Priority 24/100. No elevated risk signals yet.

Routine

MEDIUM 5.1UPGRADEUPGRADE

CVE-2022-41686 is a medium-severity flaw (CVSS 5.1) affecting openharmony, openharmony. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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/mmz_userdev 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 unspe

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	5.1 (Medium)
Attack vector	Local
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.3% (top 74%)
CISA exploited list	No
Weakness	CWE-787, CWE-125
Published	2022-10-14
Last modified	2026-06-17

Publisher (CNA): OpenHarmony · Vendor: openatom · openharmony

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-10-14 15:16 UTCPublished CVE record published
2026-06-17 05:03 UTCUpdated Record last modified

openharmony openharmony UPGRADE

Affected: >= 3.0 and <= 3.0.6

Fixed in: newer than 3.0.6

Safe to downgrade to: a release before 3.0

1. Check installed version

apt-cache policy openharmony || rpm -q openharmony || openharmony --version

2. UPGRADE to newer than 3.0.6 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade openharmony

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade openharmony

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 3.0 (Debian / Ubuntu)

apt-cache madison openharmony sudo apt install openharmony=<VERSION_BEFORE_3.0> sudo apt-mark hold openharmony

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list openharmony sudo dnf downgrade openharmony-<VERSION_BEFORE_3.0> sudo dnf versionlock add openharmony

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

openatom openharmony UPGRADE

Affected: >= 3.1 and <= 3.1.2

Fixed in: newer than 3.1.2

Safe to downgrade to: a release before 3.1

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-41686?

openharmony: upgrade to newer than 3.0.6; openharmony: upgrade to newer than 3.1.2. Exact commands for each OS are on this page.

Is CVE-2022-41686 being exploited?

CVE-2022-41686 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-41686 affect?

CVE-2022-41686 affects openharmony, openharmony. Severity is medium (CVSS 5.1). 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/mmz_userdev device driver. The impact depends on the privileges of the attacker. The unprivileged process run o

How urgent is CVE-2022-41686?

Priority 24/100. No elevated risk signals yet.

Related CVEs

CVE-2026-0639 LOW 3.3 UPGRADE in OpenHarmony v6.0 and prior versions allow a local attacker case DOS through missing release of memory.
CVE-2025-6969 MEDIUM 5.0 MITIGATE in OpenHarmony v5.1.0 and prior versions allow a local attacker cause DOS through improper input.
CVE-2025-52458 MEDIUM 5.5 MITIGATE in OpenHarmony v5.1.0 and prior versions allow a local attacker arbitrary code execution in pre-installed apps
CVE-2025-41432 MEDIUM 5.5 MITIGATE in OpenHarmony v5.1.0 and prior versions allow a local attacker arbitrary code execution in pre-installed apps
CVE-2025-27577 HIGH 8.4 UPGRADE in OpenHarmony v5.0.3 and prior versions allow a local attacker arbitrary code execution in tcb through race c

References

← Back to latest CVEs