---
id: "CVE-2026-98666"
kind: "vulnerability"
aliases: ["CVE-2026-98666"]
title: "Linux kernel: adis16136 gyro driver debugfs read can use freed memory"
severity: "unknown"
cvss: null
epss: null
exploited: false
status: "open"
category: "infrastructure"
products: []
ecosystems: []
tags: ["embedded", "iio-drivers", "infrastructure", "linux-kernel"]
not_affected_if: ["adis16136-not-loaded", "debugfs-not-mounted"]
published_at: "2026-10-18T16:17:19+00:00"
first_seen_at: "2026-10-23T21:57:16+00:00"
updated_at: "2026-10-25T05:19:26+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98666", "first_seen_at": "2026-10-23T21:57:16+00:00"}]
---

# Linux kernel: adis16136 gyro driver debugfs read can use freed memory

The adis16136 IIO gyroscope driver exposes a serial_number debugfs file whose read handlers skip the debugfs protection call, so a read in progress is not waited for when the driver unbinds. A read racing with unbind can then touch memory already freed, which can crash the kernel or lead to further memory corruption.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- unknown

## Fix

- Update the Linux kernel to a release containing the upstream fix that switches the adis16136 serial_number file to debugfs_create_file(); the fixed version is unknown from the sources.

## Timeline

- 2026-10-23T21:57:16+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-98666

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_