YoctoApplication · Linuxfoundation

CVE-2024-20147

MEDIUM · 5.3 CVSS v3.1 Published 2025-02-03

Fix available

A fix is available. Upgrade to after 3.5 or later.

See remediation →

62/100

Remediation priority · Elevated

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

In Bluetooth FW, there is a possible reachable assertion due to improper exception handling. This could lead to remote denial of service with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: WCNCR00389046 (Note: For MT79XX chipsets) / ALPS09136501 (Note: For MT2737, MT3603, MT6XXX, and MT8XXX chipsets); Issue ID: MSV-1797.

Technical summary

dbcve analysis · moderate confidence

This is a firmware vulnerability in MediaTek Bluetooth chipsets (MT79XX, MT2737, MT3603, MT6XXX, MT8XXX) where improper exception handling leads to a reachable assertion, causing the Bluetooth firmware to crash and result in denial of service. The vulnerability is exploitable remotely without user interaction or elevated privileges.

MitigationApply the vendor-provided firmware patches (WCNCR00389046 for MT79XX, ALPS09136501 for MT2737/MT3603/MT6XXX/MT8XXX) to resolve the improper exception handling that triggers the assertion. Verify Bluetooth functionality after patching.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

YoctoApplication

Affected:= 3.3= 4.0= 5.0

Software Development KitApplication

Affected:<= 3.5

AndroidOperating system

Affected:= 13.0= 14.0= 15.0

OpenwrtOperating system

Affected:= 23.05

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify MediaTek Bluetooth chipset in use

Check system hardware information or Bluetooth adapter details for MediaTek chipset identifiers MT79XX, MT2737, MT3603, MT6XXX, or MT8XXX. On Linux this may appear in 'hcitool -i hci0 info', 'hciconfig', '/sys/class/bluetooth/', or hardware logs. On Android check 'Settings > About Phone > Hardware' or use 'dumpsys bluetooth_manager'.

Affected if The system uses any of the listed MediaTek chipset models (MT79XX, MT2737, MT3603, MT6XXX, MT8XXX)
Check Bluetooth firmware version

Retrieve the Bluetooth firmware version from the MediaTek chipset. On Linux this may be available via 'hcitool -i hci0 version', 'btmgmt info', or by reading firmware files in /lib/firmware/mediatek/. Compare the firmware version against the patched versions provided in vendor advisories.

Affected if The Bluetooth firmware version is unpatched and corresponds to the vulnerable firmware builds preceding patches WCNCR00389046 (MT79XX) or ALPS09136501 (MT2737/MT3603/MT6XXX/MT8XXX)
Verify operating system or SDK version

Check the installed OS or SDK version against the affected versions listed: Linuxfoundation Yocto 3.3, 4.0, or 5.0; Mediatek SDK <= 3.5; Google Android 13.0, 14.0, or 15.0; OpenWrt 23.05. Use 'cat /etc/os-release' for Linux distros, 'getprop ro.build.version.release' for Android, or check SDK documentation.

Affected if The operating system or SDK version matches one of the affected version numbers exactly (3.3, 4.0, 5.0 for Yocto; <=3.5 for Mediatek SDK; 13.0, 14.0, 15.0 for Android; 23.05 for OpenWrt)
Confirm Bluetooth is enabled and operational

Verify that the Bluetooth subsystem is active. On Linux use 'systemctl status bluetooth' or 'rfkill list'. On Android check 'Settings > Bluetooth' is ON or use 'dumpsys bluetooth'. The vulnerability requires Bluetooth to be in a state where the firmware handles incoming connections.

Affected if Bluetooth is currently enabled and the MediaTek chipset is actively handling Bluetooth operations

The environment is affected if it uses any of the listed MediaTek Bluetooth chipsets (MT79XX, MT2737, MT3603, MT6XXX, MT8XXX) with unpatched firmware while running an affected OS/SDK version and with Bluetooth enabled.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to a release after 3.5

Interim mitigation

Apply the vendor-provided firmware patches (WCNCR00389046 for MT79XX, ALPS09136501 for MT2737/MT3603/MT6XXX/MT8XXX) to resolve the improper exception handling that triggers the assertion. Verify Bluetooth functionality after patching.

Recommended fix Moderate confidence

1. Identify the specific MediaTek chipset model in the affected device (MT79XX, MT2737, MT3603, MT6XXX, or MT8XXX)
2. Contact MediaTek or the device OEM to obtain the firmware patch corresponding to Patch ID WCNCR00389046 (for MT79XX) or ALPS09136501 (for MT2737, MT3603, MT6XXX, MT8XXX)
3. Apply the provided MediaTek Bluetooth firmware patch to update the Bluetooth firmware on the device
4. Verify the patch has been applied by checking the firmware version or confirming the MSV-1797 issue is resolved
5. Test Bluetooth functionality to ensure the denial of service vulnerability is mitigated

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Yocto Scoped from the published advisory

Consultation3.0 h
Implementation4.0 h
Testing8.0 h
Review / QA2.0 h

17.0 hours of engineering $2,880

Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,608.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2024-20147 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

corp.mediatek.comVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-20147 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2024-20147?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here

Verified mitigations, workarounds, and config changes
Version or environment caveats, and links to real fixes
No weaponised exploit code, or anything meant to cause harm
No spam, self-promotion, credentials, or personal data

At a glance

A fix existsUpgrade to after 3.5 or later

Severity 5.3 Medium

Exploit likelihood EPSS, next 30 days 0.2%

Affects: Yocto

Remediation

Need this fixed?

Fix this in Yocto 17 hrs · Moderate

Typical engagement from $2,880

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2024-20147 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

Check your environment

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References