CVE-2024-20139: In Bluetooth firmware, there is a possible firmware asssert due to improper handling of exceptional conditions

Q: How do I fix CVE-2024-20139?

yocto: downgrade or apply the listed mitigation; software development kit: upgrade to newer than 3.3; android: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Q: Is CVE-2024-20139 being exploited?

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

CVE-2024-20139 affects yocto, software development kit, android. Severity is medium (CVSS 6.5). In Bluetooth firmware, there is a possible firmware asssert due to improper handling of exceptional conditions. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for ex

Q: How urgent is CVE-2024-20139?

Priority 28/100. On your watchlist

Routine

MEDIUM 6.5WATCHLISTDOWNGRADEUPGRADEMITIGATE

CVE-2024-20139 is a medium-severity flaw (CVSS 6.5) affecting yocto, software development kit, android. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

In Bluetooth firmware, there is a possible firmware asssert due to improper handling of exceptional conditions. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS09001270; Issue ID: MSV-1600.

Why this priority

On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	6.5 (Medium)
Attack vector	Adjacent network
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.1% (top 98%)
CISA exploited list	No
Weakness	CWE-617
Published	2024-12-02
Last modified	2026-06-17

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

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

Am I affected?

Timeline

2024-12-02 04:15 UTCPublished CVE record published
2026-06-17 07:06 UTCUpdated Record last modified

linuxfoundation yocto DOWNGRADE

Affected: 3.3 · 4.0 · 5.0

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.

mediatek software development kit UPGRADE

Affected: <= 3.3

Fixed in: newer than 3.3

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy software-development-kit || rpm -q software-development-kit || software-development-kit --version

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

sudo apt update && sudo apt install --only-upgrade software-development-kit

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade software-development-kit

Note

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

google android MITIGATE

Affected: 13.0 · 14.0 · 15.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 13.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: 23.05.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 23.05.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-20139?

yocto: downgrade or apply the listed mitigation; software development kit: upgrade to newer than 3.3; android: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2024-20139 being exploited?

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

CVE-2024-20139 affects yocto, software development kit, android. Severity is medium (CVSS 6.5). In Bluetooth firmware, there is a possible firmware asssert due to improper handling of exceptional conditions. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for ex

How urgent is CVE-2024-20139?

Priority 28/100. On your watchlist

Software pages

Android vulnerabilities · Bluetooth 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