# CVE-2026-63935: iio: adc: nxp-sar-adc: fix division by zero in write_raw

> A local attacker can cause a kernel crash by writing invalid values to the NXP SAR ADC sampling frequency sysfs attribute.

- **Severity:** Not scored
- **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:** 19 Jul 2026
- **Updated:** 19 Jul 2026
- **Also known as:** DEBIAN-CVE-2026-63935, GHSA-ph67-42mq-jpw6, UBUNTU-CVE-2026-63935

## What is CVE-2026-63935?

CVE-2026-63935 is a denial of service vulnerability in Linux, published on 19 Jul 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: nxp-sar-adc: fix division by zero in write_raw

Add a validation check for the sampling frequency value before using it
as a divisor. A user writing zero or a negative value to the
sampling_frequency sysfs attribute triggers a division by zero in the
kernel.

Also prevent unsigned integer underflow when the computed cycle count is
smaller than NXP_SAR_ADC_CONV_TIME, which would wrap the u32 inpsamp to
a huge value.

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


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

Apply the vendor's patch.

## Is CVE-2026-63935 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-63935 is a denial of service vulnerability in Linux, published on 19 Jul 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-63935 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-63935/ (Markdown: https://insights.sbomify.com/CVE-2026-63935/index.md)
```

## Sources

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

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