CVE-2026-37532
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 · uneditedAGL agl-service-can-low-level thru 17.1.12 contains a heap buffer over-read in the isotp-c library. In isotp_continue_receive (receive.c:87-89), the payload_length for a Single Frame is extracted from a 4-bit nibble in the CAN frame data, yielding values 0-15. However, a standard CAN frame is only 8 bytes, with payload starting at data[1] (7 bytes available). When payload_length exceeds the available data (e.g., nibble=15 but only 7 payload bytes exist), memcpy(message.payload, &data[1], payload_length) reads up to 8 bytes past the end of the data buffer.
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 confidenceHeap buffer over-read vulnerability in the ISOTP-c library's isotp_continue_receive function. The code extracts a 4-bit payload_length (0-15) from Single Frame CAN data without validating it fits within the 7 available payload bytes starting at data[1]. When payload_length exceeds available data (e.g., nibble=15), memcpy reads past the 8-byte CAN frame buffer boundary.
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<= 17.1.12CVSS 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
- Low
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Check if running Automotive Grade LinuxRun 'cat /etc/os-release' or 'cat /etc/lsb-release' to identify the OS and versionAffected if The system is running Linuxfoundation Automotive Grade Linux version 17.1.12 or earlier
-
Identify ISOTP-c library installationSearch for the isotp library files: 'find / -name "*isotp*" -type f 2>/dev/null' or check package manager 'dpkg -l | grep isotp' or 'rpm -qa | grep isotp'Affected if The ISOTP-c library is installed on the system
-
Locate vulnerable receive.c source fileFind the isotp source code: 'find / -path "*/isotp/*" -name "receive.c" 2>/dev/null' and examine the isotp_continue_receive function for the memcpy operationAffected if The receive.c file exists and contains the isotp_continue_receive function with memcpy using payload_length from Single Frame CAN data without bounds checking
-
Verify CAN ISOTP usage in environmentCheck if any CAN bus application or service uses ISOTP protocol: 'ps aux | grep -i iso' or inspect running processes that communicate over CAN interfaces 'ip link show' and check related servicesAffected if Any application or service is actively using ISOTP protocol to receive CAN frames, as this triggers the vulnerable code path
-
Inspect CAN frame reception codeIf source code is available, search for 'isotp_continue_receive' calls and examine the memcpy that uses data[1] payload_length: look for pattern 'memcpy(dest, &data[1], payload_length)' without prior validation 'payload_length <= 7'Affected if Code calls isotp_continue_receive without bounds checking on payload_length before the memcpy operation
A system is affected if it runs Automotive Grade Linux <= 17.1.12 with the ISOTP-c library present and actively receiving CAN frames through the isotp_continue_receive function, where the vulnerable memcpy can read past the 8-byte buffer boundary when payload_length exceeds 7.
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.
dbcve · scopedAdd bounds checking to verify payload_length <= 7 before performing the memcpy operation in receive.c. Reject or truncate frames where payload_length exceeds available bytes.
AGL release > 17.1.12 (e.g., 17.2.x or later stable release containing the isotp-c patch)
- 1. Identify the current version of agl-service-can-low-level in your AGL system
- 2. Check the AGL release notes or gerrit.automotivelinux.org for commits addressing the isotp_continue_receive buffer over-read vulnerability (CVE-2026-37532)
- 3. Upgrade to the latest AGL release that includes a patched version of agl-service-can-low-level, which should be version > 17.1.12
- 4. After upgrading, verify the fix by reviewing the patched receive.c file in the isotp-c library to confirm payload_length is now properly validated against available data (7 bytes max starting at data[1])
- 5. Test the CAN communication functionality to ensure the patch does not break legitimate CAN frame processing
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.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,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-37532 — 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-37532 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