CVE-2022-26528
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 · uneditedRealtek Linux/Android Bluetooth Mesh SDK has a buffer overflow vulnerability due to insufficient validation for the length of segmented packets’ shift parameter. An unauthenticated attacker in the adjacent network can exploit this vulnerability to cause buffer overflow and disrupt service.
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 confidenceThe Realtek Linux/Android Bluetooth Mesh SDK contains a buffer overflow vulnerability in its segmented packet handling logic. The shift parameter within segmented packets lacks proper bounds checking, allowing an adjacent unauthenticated attacker to overflow buffers by sending maliciously crafted packets with excessive shift values, causing service disruption.
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<= 4.17-4.17-20220127CVSS 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.
-
Identify Realtek Bluetooth Mesh SDK usageDetermine if your system or application is using the Realtek Bluetooth Mesh SDK. This may be evident from product documentation, SDK installation directories, or running processes related to Bluetooth Mesh functionality.Affected if The system uses the Realtek Bluetooth Mesh SDK for Linux or Android
-
Check SDK version against affected rangeLocate the installed SDK version information. Compare your version to the affected range: versions <= 4.17-4.17-20220127. If your version is at or below this release, the vulnerability is present.Affected if Installed SDK version is 4.17-4.17-20220127 or earlier
-
Verify Bluetooth Mesh feature is enabledConfirm that Bluetooth Mesh functionality is active on the device. Check configuration files or runtime settings that enable Mesh protocol support in the Realtek Bluetooth stack.Affected if Bluetooth Mesh feature is enabled and processing incoming Bluetooth Mesh packets
-
Inspect segmented packet handling configurationReview the Bluetooth Mesh stack configuration for segmented packet processing settings. The vulnerability exists in the shift parameter handling logic within segmented packets.Affected if Segmented packet handling is operational and accepting external Bluetooth Mesh traffic
A system is affected if it uses the Realtek Bluetooth Mesh SDK version 4.17-4.17-20220127 or earlier with Bluetooth Mesh functionality enabled and exposed to adjacent attackers.
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 vendor-supplied patch from Realtek for the Bluetooth Mesh SDK to add proper validation of the segmented packet shift parameter length. Until patched, minimize Bluetooth exposure by limiting the device's discoverability and using network access controls to restrict adjacent network attackers.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26528 — 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-2022-26528 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