CVE-2019-20546
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 · uneditedAn issue was discovered on Samsung mobile devices with N(7.x), O(8.x), and P(9.0) (Broadcom Wi-Fi chipsets) software. A denial-of-service attack can leverage a shared interface between Broadcom Bluetooth and Broadcom Wi-Fi. The Samsung ID is SVE-2019-15350 (November 2019).
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 confidenceA denial-of-service vulnerability exists in Samsung mobile devices running Android N(7.x), O(8.x), and P(9.0) with Broadcom Wi-Fi chipsets. The issue stems from a shared interface between the Broadcom Bluetooth and Broadcom Wi-Fi components, allowing an attacker to trigger a DoS condition.
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= 7.0= 7.1.0= 7.1.1= 7.1.2= 8.0= 8.1= 9.0CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm device is a Samsung mobile deviceCheck the device manufacturer and model in Settings > About Phone > Device name or model numberAffected if The device is not manufactured by Samsung, then it is not affected by this specific vulnerability
-
Verify Android version is in affected rangeGo to Settings > About Phone > Android version. Confirm the version is 7.0, 7.1.0, 7.1.1, 7.1.2, 8.0, 8.1, or 9.0Affected if The Android version matches one of these listed versions, the device falls within the affected version range
-
Confirm the device has a Broadcom Wi-Fi chipsetCheck the Wi-Fi chipset information in Settings > About Phone > Hardware info, or use a system info app to view hardware specifications. Look for a Broadcom Wi-Fi adapterAffected if The Wi-Fi chipset is from Broadcom, the shared interface vulnerability applies to this hardware configuration
-
Verify Bluetooth and Wi-Fi features are presentConfirm Bluetooth and Wi-Fi are available on the device. Check Settings to see if both wireless options are listed and can be toggledAffected if Both Bluetooth and Wi-Fi interfaces exist on the device, the shared interface between them could be exploited
If the device is a Samsung mobile phone with a Broadcom Wi-Fi chipset running Android 7.x, 8.x, or 9.0 with Bluetooth and Wi-Fi hardware present, the environment is affected by this vulnerability.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply the Samsung security patch (SVE-2019-15350) released November 2019, which addresses the shared interface vulnerability between Broadcom Bluetooth and Wi-Fi components. Users of affected devices should ensure their devices are running the latest Samsung software updates.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2019-20546 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-20546 in production — separate from our analysis above.
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.
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.
- 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