CVE-2024-20053: In flashc, there is a possible out of bounds write due to an uncaught exception

Routine

HIGH 8.4WATCHLISTDOWNGRADEDOWNGRADEMITIGATE

CVE-2024-20053 is a high-severity flaw (CVSS 8.4) affecting yocto, rdk-b, android. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

In flashc, there is a possible out of bounds write due to an uncaught exception. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS08541757; Issue ID: ALPS08541764.

Why this priority

High severity
On your watchlist

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

Risk facts

CVSS score	8.4 (High)
Attack vector	Local
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.1% (top 100%)
CISA exploited list	No
Weakness	CWE-787
Published	2024-04-01
Last modified	2026-06-17

Publisher (CNA): MediaTek, Inc. · Vendor: google · linuxfoundation · openwrt · rdkcentral

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

Am I affected?

Timeline

2024-04-01 03:15 UTCPublished CVE record published
2026-06-17 07:05 UTCUpdated Record last modified

linuxfoundation yocto DOWNGRADE

Affected: 3.3

Fixed in: no fixed release known

Safe to downgrade to: a release before 3.3

1. Check installed version

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

2. No fixed release: DOWNGRADE to a release before 3.3 (Debian / Ubuntu)

apt-cache madison yocto sudo apt install yocto=<VERSION_BEFORE_3.3> sudo apt-mark hold yocto

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list yocto sudo dnf downgrade yocto-<VERSION_BEFORE_3.3> sudo dnf versionlock add 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.

rdkcentral rdk-b DOWNGRADE

Affected: 2022q3

Fixed in: no fixed release known

Safe to downgrade to: a release before 2022q3

1. Check installed version

apt-cache policy rdk-b || rpm -q rdk-b || rdk-b --version

2. No fixed release: DOWNGRADE to a release before 2022q3 (Debian / Ubuntu)

apt-cache madison rdk-b sudo apt install rdk-b=<VERSION_BEFORE_2022q3> sudo apt-mark hold rdk-b

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list rdk-b sudo dnf downgrade rdk-b-<VERSION_BEFORE_2022q3> sudo dnf versionlock add rdk-b

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 · 13.0 · 14.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.

openwrt openwrt MITIGATE

Affected: 19.07.0 · 21.02.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 19.07.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-2024-20053?

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

Is CVE-2024-20053 being exploited?

CVE-2024-20053 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-2024-20053 affect?

CVE-2024-20053 affects yocto, rdk-b, android. Severity is high (CVSS 8.4). In flashc, there is a possible out of bounds write due to an uncaught exception. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS085417

How urgent is CVE-2024-20053?

Priority 35/100. High severity; On your watchlist

Software pages

Android vulnerabilities · OpenWrt vulnerabilities

Related CVEs

CVE-2025-20746 MEDIUM 6.7 DOWNGRADE DOWNGRADE In gnss service, there is a possible out of bounds write due to an incorrect bounds check
CVE-2025-20747 MEDIUM 6.7 DOWNGRADE DOWNGRADE In gnss service, there is a possible out of bounds write due to an incorrect bounds check
CVE-2026-20435 MEDIUM 4.6 DOWNGRADE DOWNGRADE In preloader, there is a possible read of device unique identifiers due to a logic error
CVE-2025-61611 HIGH 7.5 MITIGATE In modem, there is a possible improper input validation
CVE-2025-20765 MEDIUM 4.7 DOWNGRADE MITIGATE In aee daemon, there is a possible system crash due to a race condition

References

← Back to latest CVEs