dbcve.org
YoctoApplication · Linuxfoundation

CVE-2024-20089

HIGH · 7.5 CVSS v3.1 Published 2024-09-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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.

NVD · unedited
In wlan, there is a possible denial of service due to incorrect error handling. This could lead to remote denial of service with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS08861558; Issue ID: MSV-1526.

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.

dbcve analysis · moderate confidence

A denial of service vulnerability exists in the WLAN (wireless LAN) component due to incorrect error handling. The flaw allows remote attackers to cause the WLAN service to become unavailable without requiring any authentication or user interaction. The vulnerability stems from improper handling of error conditions within the WLAN stack, which can lead to a crash or hang state.

MitigationApply the vendor patch ALPS08861558 to the affected WLAN component. Since this is a firmware-level fix, ensure the patch is integrated into the device firmware through the vendor's standard update mechanism.

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

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.

NVD · CPE data
YoctoApplication
Affected:= 2.6= 3.3= 4.0
Rdk BApplication
Affected:= 2022q3
AndroidOperating system
Affected:= 13.0= 14.0

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.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

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.

dbcve checks

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

  1. Identify your product and version
    Determine if your system runs Linuxfoundation Yocto (versions 2.6, 3.3, or 4.0), Rdkcentral Rdk B (2022q3), or Google Android (13.0 or 14.0). Check the OS/build information or system properties to confirm the exact version.
    Affected if The installed product version matches one of the affected versions listed (Yocto 2.6/3.3/4.0, RDK B 2022q3, or Android 13.0/14.0)
  2. Verify WLAN component is present
    Check if the WLAN (wireless LAN) feature is enabled on your device. On Android, inspect Wi-Fi settings or wireless interface status. On Yocto/RDK systems, check for wlan0 interface or WLAN service via 'ip link' or 'ifconfig' command.
    Affected if WLAN hardware or software component is present and accessible on the device
  3. Confirm WLAN service is active
    Check the status of the WLAN service. On Android, verify Wi-Fi is enabled in settings. On Linux-based systems, check if the WLAN daemon (such as wpa_supplicant, hostapd, or vendor-specific WLAN service) is running via 'ps' or 'systemctl status' commands.
    Affected if The WLAN service is running or Wi-Fi is enabled on the device
  4. Check WLAN firmware or driver version
    If accessible, query the WLAN firmware version or driver version. On Android, this may be available through 'getprop' or vendor-specific diagnostic tools. On Linux systems, check '/sys/class/net/wlan0/device/firmware_version' or use 'iw' or 'ethtool' commands. Compare this against any available vendor patch information (ALPS08861558).
    Affected if The WLAN firmware or driver version has not been patched to address the error handling vulnerability

Your environment is affected if you run one of the specified product versions (Yocto 2.6/3.3/4.0, RDK B 2022q3, or Android 13.0/14.0) and have the WLAN component enabled, and the device WLAN firmware has not been updated with the vendor patch.

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

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch ALPS08861558 to the affected WLAN component. Since this is a firmware-level fix, ensure the patch is integrated into the device firmware through the vendor's standard update mechanism.

Recommended fix Moderate confidence

Move to a Yocto release or MediaTek wlan driver version that incorporates the ALPS08861558 patch; for Android, apply a vendor security patch containing this fix

  1. Check MediaTek's official security advisory page at corp.mediatek.com for the ALPS08861558 patch details
  2. Contact MediaTek directly to obtain the patched wlan driver/firmware for your specific chipset
  3. For Yocto-based systems: Update the meta-mediatek layer or wlan driver recipes to include the patched MediaTek wlan components
  4. For RDK B (2022q3): Apply the MediaTek wlan patch through the RDK package management system
  5. For Android: Apply the vendor security patch that includes the MediaTek wlan fix (typically delivered through monthly security patches)
  6. Reboot the device after applying the patch to ensure the wlan driver is properly loaded
  7. Verify the fix by checking that the wlan interface remains stable and doesn't crash under load
Caveat No major breaking changes expected from this error handling fix, but test wlan functionality thoroughly after applying

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

Fix this in Yocto Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-20089 — 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 Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

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

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