# CVE-2026-37530: Memory corruption in n/a

> Stack buffer overflow in AGL CAN service allows remote code execution on automotive ECUs via crafted diagnostic requests.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 May 2026
- **Updated:** 1 May 2026
- **Also known as:** GHSA-grgw-7h7j-hjqm

## What is CVE-2026-37530?

CVE-2026-37530 is a high-severity memory corruption vulnerability in n/a, published on 1 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2026-37530?

It affects 1 product.


Products: Linuxfoundation Automotive Grade Linux.

## How do I fix CVE-2026-37530?

No fix has been published for CVE-2026-37530 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-37530 being exploited?

There is no known exploitation of CVE-2026-37530 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2026-37531](https://insights.sbomify.com/CVE-2026-37531/): Path traversal in n/a (critical 9.8)
- [CVE-2026-37525](https://insights.sbomify.com/CVE-2026-37525/): Privilege escalation in n/a (high 7.8)
- [CVE-2026-37526](https://insights.sbomify.com/CVE-2026-37526/): Missing authorization in n/a (high 7.8)
- [CVE-2026-37532](https://insights.sbomify.com/CVE-2026-37532/): Memory corruption in n/a (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-37530 and fix it if it is affected.

What it is: CVE-2026-37530 is a high-severity memory corruption vulnerability in n/a, published on 1 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-37530 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-37530/ (Markdown: https://insights.sbomify.com/CVE-2026-37530/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-37530
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-37530
- OSV: https://osv.dev/vulnerability/CVE-2026-37530

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-37530/
Summaries are generated and may contain mistakes; the official description above is the record.