CVE-2026-37536
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 · uneditedmiaofng/uds-c commit e506334e270d77b20c0bc259ac6c7d8c9b702b7a (2016-10-05) contains a stack buffer overflow in send_diagnostic_request. A 6-byte stack buffer (MAX_DIAGNOSTIC_PAYLOAD_SIZE=6) receives memcpy at offset 1+pid_length with payload_length bytes. MAX_UDS_REQUEST_PAYLOAD_LENGTH=7, so 1+2+7=10 exceeds buffer by 4 bytes. No bounds check on payload_length before memcpy.
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 confidenceStack buffer overflow in send_diagnostic_request where a 6-byte stack buffer (MAX_DIAGNOSTIC_PAYLOAD_SIZE=6) receives memcpy with payload_length bytes at offset 1+pid_length. With MAX_UDS_REQUEST_PAYLOAD_LENGTH=7, the copy attempts to write 10 bytes (1+2+7) into a 6-byte buffer, overflowing by 4 bytes. No bounds check validates payload_length before the memcpy operation.
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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/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.
-
Locate the send_diagnostic_request function source codeSearch the codebase for the function 'send_diagnostic_request' and review its implementation to identify the memcpy operationAffected if The function exists and performs a memcpy into a fixed-size buffer without bounds checking on payload_length
-
Verify MAX_DIAGNOSTIC_PAYLOAD_SIZE buffer sizeFind the definition of MAX_DIAGNOSTIC_PAYLOAD_SIZE in the codebase - it should be defined as 6 bytesAffected if MAX_DIAGNOSTIC_PAYLOAD_SIZE is defined as 6 and is used as the destination buffer size for the memcpy
-
Confirm MAX_UDS_REQUEST_PAYLOAD_LENGTH valueFind the definition of MAX_UDS_REQUEST_PAYLOAD_LENGTH - it should be 7 bytesAffected if MAX_UDS_REQUEST_PAYLOAD_LENGTH is 7, allowing payload_length up to 7 bytes which exceeds the 6-byte buffer when combined with offset bytes
-
Inspect the memcpy call for missing bounds checkReview the memcpy call in send_diagnostic_request: it copies payload_length bytes at offset (1+pid_length) into the buffer; verify there is no validation that payload_length + 1 + pid_length <= buffer size before the copyAffected if The memcpy operates without validating that the total bytes to write (1 + pid_length + payload_length) does not exceed the buffer size (6 bytes)
-
Calculate overflow conditionWhen pid_length is 2 and payload_length is at maximum (7), the copy attempts to write 1+2+7=10 bytes into a 6-byte buffer, overflowing by 4 bytesAffected if The code allows payload_length up to 7 with pid_length of 2, resulting in a 4-byte overflow
The environment is affected if it contains the send_diagnostic_request function with a 6-byte MAX_DIAGNOSTIC_PAYLOAD_SIZE buffer and a memcpy that lacks bounds validation, allowing payload_length + 1 + pid_length to exceed 6 bytes.
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 dataAdd bounds checking to ensure payload_length + 1 + pid_length does not exceed MAX_DIAGNOSTIC_PAYLOAD_SIZE before memcpy, or increase buffer size to accommodate maximum possible payload.
- 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-2026-37536 — 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-37536 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