dbcve.org
Automotive Grade LinuxOperating system · Linuxfoundation

CVE-2026-37530

HIGH · 7.5 CVSS v3.1 Published 2026-05-01
Fix available
A fix is available. Upgrade to after 17.1.12 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
AGL agl-service-can-low-level thru 17.1.12 contains a stack buffer overflow in the uds-c library. The send_diagnostic_request function in uds.c allocates a 6-byte stack buffer (MAX_DIAGNOSTIC_PAYLOAD_SIZE=6) but copies up to 7 bytes (MAX_UDS_REQUEST_PAYLOAD_LENGTH=7) via memcpy at an offset of 1+pid_length (2-3 bytes), resulting in 1-4 bytes of controlled stack overflow. The payload_length field (uint8_t) has no bounds check against the destination buffer. On 32-bit ARM automotive ECUs without stack canaries, this can lead to return address overwrite and RCE.

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 confidence

Stack buffer overflow in AGL agl-service-can-low-level thru 17.1.12 where send_diagnostic_request in uds.c uses a 6-byte stack buffer (MAX_DIAGNOSTIC_PAYLOAD_SIZE=6) but memcpy can copy up to 7 bytes (MAX_UDS_REQUEST_PAYLOAD_LENGTH=7) at an offset of 1+pid_length, allowing 1-4 bytes of controlled overflow. On 32-bit ARM automotive ECUs without stack canaries, this enables return address overwrite and potential RCE.

MitigationAdd bounds checking to validate payload_length against MAX_DIAGNOSTIC_PAYLOAD_SIZE before memcpy, or increase the destination buffer to MAX_UDS_REQUEST_PAYLOAD_LENGTH. For automotive ECUs, ensure patch deployment accounts for the embedded system's update constraints.

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
Automotive Grade LinuxOperating system
Affected:<= 17.1.12

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if agl-service-can-low-level package is installed
    Run 'dpkg -l agl-service-can-low-level' or 'rpm -qa | grep -i agl-service-can-low-level' or check package management system for this specific package
    Affected if Package is installed with version <= 17.1.12 (or if version cannot be determined but package exists on AGL <= 17.1.12 systems)
  2. Locate the vulnerable uds.c source file
    Search for uds.c in the agl-service-can-low-level package files: 'find /usr -name uds.c 2>/dev/null' or 'dpkg -L agl-service-can-low-level | grep uds.c'
    Affected if The uds.c file exists and is from the affected package version
  3. Verify the vulnerable memcpy pattern exists
    Examine uds.c and look for memcpy calls using MAX_DIAGNOSTIC_PAYLOAD_SIZE (6-byte buffer) copying from a source that can be up to MAX_UDS_REQUEST_PAYLOAD_LENGTH (7 bytes) at offset 1+pid_length
    Affected if The code contains the unbounded memcpy pattern: memcpy to a 6-byte buffer from a 7-byte max source at offset 1+pid_length
  4. Confirm the diagnostic request feature is enabled
    Check if the CAN low-level service is running or configured to start: 'systemctl status agl-service-can-low-level' or check service configuration files in /etc or /var
    Affected if The agl-service-can-low-level service is active or enabled, enabling the vulnerable code path

The system is affected if agl-service-can-low-level version <= 17.1.12 is installed AND the service is running, which exposes the stack buffer overflow in uds.c send_diagnostic_request function.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 17.1.12
Interim mitigation

Add bounds checking to validate payload_length against MAX_DIAGNOSTIC_PAYLOAD_SIZE before memcpy, or increase the destination buffer to MAX_UDS_REQUEST_PAYLOAD_LENGTH. For automotive ECUs, ensure patch deployment accounts for the embedded system's update constraints.

Fix this in Automotive Grade Linux Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,872.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-37530 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-37530 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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