# CVE-2026-98666: iio: gyro: adis16136: fix unprotected debugfs reads

> A use-after-free vulnerability in the Linux kernel adis16136 gyro driver allows local attackers to cause a denial of service or potentially execute code via debugfs reads.

- **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:** 18 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-108705, BELL-CVE-2026-98666, DEBIAN-CVE-2026-98666, GHSA-fw25-7hvg-9627, UBUNTU-CVE-2026-98666

## What is CVE-2026-98666?

CVE-2026-98666 is an use after free vulnerability in Linux, published on 18 Oct 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: gyro: adis16136: fix unprotected debugfs reads

The serial_number file operations are open coded and never call
debugfs_file_get(), which debugfs_create_file_unsafe() requires.
debugfs_remove_recursive() therefore does not wait for a read in
progress, and unbind frees the iio_dev underneath it.

Use debugfs_create_file() instead.

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


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

Apply the vendor's patch.

## Is CVE-2026-98666 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98666 is an use after free vulnerability in Linux, published on 18 Oct 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-98666 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-98666/ (Markdown: https://insights.sbomify.com/CVE-2026-98666/index.md)
```

## Sources

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

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