CVE-2026-98666
Received Received - Intake

Unprotected Debugfs Reads in Linux Kernel IIO Gyro ADIS16136

Vulnerability report for CVE-2026-98666, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-10-18

Last updated on: 2026-10-18

Assigner: kernel.org

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-18
Last Modified
2026-10-18
Generated
2026-10-18
AI Q&A
2026-10-18
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 5 associated CPEs
Vendor Product Version / Range
Linux Linux 9aaea09b4cbdbe1a80ab3fa1a5d32c3ec61fa6e2
Linux Linux 9aaea09b4cbdbe1a80ab3fa1a5d32c3ec61fa6e2
Linux Linux 9aaea09b4cbdbe1a80ab3fa1a5d32c3ec61fa6e2
Linux Linux 9aaea09b4cbdbe1a80ab3fa1a5d32c3ec61fa6e2
Linux Linux 4.16

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in the Linux kernel involves a missing protection in the debugfs interface for the ADIS16136 gyroscope driver. The serial_number file was created using an unsafe debugfs function but did not implement the required debugfs_file_get() call. This oversight allows the debugfs_remove_recursive() function to remove the file while a read operation is still in progress, potentially leading to a use-after-free condition when the device is unbound.

Detection Guidance

This vulnerability is specific to the Linux kernel's IIO gyro driver for the ADIS16136 device. Detection requires checking the kernel version and the presence of the affected driver. Use commands like 'uname -a' to check the kernel version and 'lsmod | grep adis16136' to verify if the driver is loaded.

Impact Analysis

This vulnerability could allow an attacker with local access to cause a system crash or execute arbitrary code by triggering a race condition during a debugfs read operation. It may also lead to privilege escalation if combined with other kernel vulnerabilities.

Mitigation Strategies

Apply the kernel update that resolves this issue. If the driver is not in use, unload it with 'rmmod adis16136'. Ensure debugfs operations are properly protected by using debugfs_create_file() instead of debugfs_create_file_unsafe().

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-98666. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart