dbcve.org
Stack-based Buffer OverflowWeakness · CWE-121

CVE-2023-50809

HIGH · 7.8 CVSS v3.1 Published 2024-08-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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 certain Sonos products before S1 Release 11.12 and S2 release 15.9, the mt_7615.ko wireless driver does not properly validate an information element during negotiation of a WPA2 four-way handshake. This lack of validation leads to a stack buffer overflow. This can result in remote code execution within the kernel. This affects Amp, Arc, Arc SL, Beam, Beam Gen 2, Beam SL, and Five.

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 · high confidence

The mt_7615.ko wireless driver in affected Sonos devices fails to validate an information element during the WPA2 four-way handshake negotiation. This validation failure allows a specially crafted malicious wireless frame to trigger a stack buffer overflow, enabling remote code execution within the kernel context.

MitigationApply the vendor-supplied firmware updates: S1 Release 11.12 or later for S1 devices, and S2 release 15.9 or later for S2 devices. Prioritize updating devices with direct wireless network exposure.

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

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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. Verify the mt_7615.ko driver is in use
    On the Sonos device or network, check loaded kernel modules or driver inventory for mt_7615.ko. This can be done via `lsmod` on the device shell, or by examining wireless adapter specifications if accessible.
    Affected if The mt_7615.ko driver is present and loaded on the device
  2. Confirm wireless (Wi-Fi) is enabled
    Verify that the wireless interface on the Sonos device is active and configured to connect to Wi-Fi networks. Check interface status via `iwconfig` or the device's network settings.
    Affected if Wireless functionality is enabled and the device uses Wi-Fi for network connectivity
  3. Identify the Sonos device model
    Determine the exact Sonos model number (e.g., One, Play:5, Arc, etc.) via the Sonos app, device labeling, or `sonosctl` / API query if available.
    Affected if The device is a Sonos product that utilizes the mt_7615.ko wireless driver
  4. Check the installed firmware version
    Retrieve the current firmware version from the Sonos app (under About This System) or via the Sonos API/CLI tools. Note whether the device runs S1 or S2 software.
    Affected if The firmware version is S1 earlier than 11.12, or S2 earlier than 15.9
  5. Compare version against fixed releases
    Compare the identified firmware version to the known fixed releases: S1 version 11.12 or later, S2 version 15.9 or later.
    Affected if The device firmware is below the S1 11.12 or S2 15.9 threshold, meaning the vulnerable driver code path during WPA2 handshake is present

A user is affected if their Sonos device uses the mt_7615.ko driver, has wireless enabled, and runs firmware older than S1 11.12 or S2 15.9.

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-supplied firmware updates: S1 Release 11.12 or later for S1 devices, and S2 release 15.9 or later for S2 devices. Prioritize updating devices with direct wireless network exposure.

Recommended fix High confidence

S1 Release 11.12 or S2 Release 15.9 (whichever corresponds to the device's software)

  1. 1. Identify the Sonos product model (Amp, Arc, Arc SL, Beam, Beam Gen 2, Beam SL, or Five)
  2. 2. Determine if the device runs S1 or S2 software by opening the Sonos app and checking Settings > About > My System > About My Sonos System
  3. 3. For S1 devices: Upgrade firmware to S1 Release 11.12 or later
  4. 4. For S2 devices: Upgrade firmware to S2 Release 15.9 or later
  5. 5. To perform the upgrade: Open the Sonos app, go to Settings > System > System Updates, and select 'Check for Updates' or ensure automatic updates are enabled
  6. 6. Verify the firmware version after upgrading by checking Settings > About > My System

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-50809 — 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-2023-50809 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