# CVE-2026-72480: iio: adc: xilinx-ams: fix out-of-bounds channel lookup in event handling

> A missing bounds check in the Xilinx AMS ADC driver allows out-of-bounds memory access, potentially causing crashes or code execution.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-72480, DEBIAN-CVE-2026-72480, GHSA-c7xc-qxg6-9546, UBUNTU-CVE-2026-72480

## What is CVE-2026-72480?

CVE-2026-72480 is a high-severity memory corruption vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

iio: adc: xilinx-ams: fix out-of-bounds channel lookup in event handling

ams_event_to_channel() may return a pointer past the end of
dev->channels when no matching scan_index is found. This can lead
to invalid memory access in ams_handle_event().

Add a bounds check in ams_event_to_channel() and return NULL when
no channel is found. Also guard the caller to safely handle this
case.

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


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

Apply the vendor's patch.

## Is CVE-2026-72480 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72480 is a high-severity memory corruption vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-72480 in the wild and no public exploit code.

Affected product: Linux. 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-72480/ (Markdown: https://insights.sbomify.com/CVE-2026-72480/index.md)
```

## Sources

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

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