Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2023-32828: In vpu, there is a possible out of bounds write due to an integer overflow

24
Routine
MEDIUM 6.7DOWNGRADEMITIGATE

CVE-2023-32828 is a medium-severity flaw (CVSS 6.7) affecting iot yocto, android. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

In vpu, there is a possible out of bounds write due to an integer overflow. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS07767817; Issue ID: ALPS07767817.

Why this priority

  • No elevated risk signals yet

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score6.7 (Medium)
Attack vectorLocal
Attack complexityLow
Privileges neededHigh
User interactionNone
EPSS exploit chance0.1% (top 99%)
CISA exploited listNo
WeaknessCWE-190
Published2023-10-02
Last modified2026-06-17
Publisher (CNA): MediaTek, Inc. · Vendor: google · mediatek

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

mediatek iot yocto DOWNGRADE
Affected: 23.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 23.0
1. Check installed version
apt-cache policy iot-yocto || rpm -q iot-yocto || iot-yocto --version
2. No fixed release: DOWNGRADE to a release before 23.0 (Debian / Ubuntu)
apt-cache madison iot-yocto sudo apt install iot-yocto=<VERSION_BEFORE_23.0> sudo apt-mark hold iot-yocto
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list iot-yocto sudo dnf downgrade iot-yocto-<VERSION_BEFORE_23.0> sudo dnf versionlock add iot-yocto
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.
google android MITIGATE
Affected: 12.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 12.0
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-2023-32828?

iot yocto: downgrade or apply the listed mitigation; android: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2023-32828 being exploited?

CVE-2023-32828 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-2023-32828 affect?

CVE-2023-32828 affects iot yocto, android. Severity is medium (CVSS 6.7). In vpu, there is a possible out of bounds write due to an integer overflow. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS07767817; I

How urgent is CVE-2023-32828?

Priority 24/100. No elevated risk signals yet.

Software pages

Android vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.