CVE-2026-35553
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 · uneditedBluetooth ACPI Drivers provided by Dynabook Inc. contain a stack-based buffer overflow vulnerability. An attacker may execute arbitrary code by modifying certain registry values.
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 confidenceDynabook Bluetooth ACPI drivers contain a stack-based buffer overflow vulnerability where an attacker with the ability to modify certain registry values can trigger the overflow and execute arbitrary code. The vulnerability exists in the driver's handling of registry configuration data, which is copied into a fixed-size stack buffer without proper bounds checking.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Dynabook Bluetooth ACPI driver is installedOpen Device Manager, expand 'Bluetooth' section, and look for Dynabook Bluetooth driver entries. Alternatively, run 'driverquery /v | findstr -i bluetooth' to list installed Bluetooth drivers.Affected if Dynabook Bluetooth ACPI driver is present in the system
-
Locate the driver file and versionRight-click the driver in Device Manager, select Properties, then the Driver tab to view the driver version and file path. The driver file is typically in C:\Windows\System32\drivers\ with 'bt' or 'acpi' in the filename.Affected if Driver version cannot be determined or falls within an unpatched version range
-
Identify vulnerable registry keysCheck registry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BtwUSBHci or HKEY_LOCAL_MACHINE\SOFTWARE\Dynabook for Bluetooth ACPI configuration entries. Look for any registry values that control driver behavior or parameters.Affected if Registry keys related to Dynabook Bluetooth ACPI driver configuration exist on the system
-
Check registry key permissionsRight-click the identified registry key in regedit, select Permissions, and review which users or groups have Write or Full Control access. Use 'reg query' command with access control output to programmatically check permissions.Affected if Users other than Administrators or System have write access to the Bluetooth ACPI registry configuration keys
Affected if Dynabook Bluetooth ACPI driver is installed and the relevant registry configuration keys are present and writable by non-admin users.
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 vendor-provided patches for Dynabook Bluetooth ACPI drivers when available. Restrict write access to the relevant registry keys to minimize attack surface.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35553 — 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-2026-35553 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