GHSA-W4FG-XQ8W-GQ57
Vulnerability from github – Published: 2026-10-18 18:31 – Updated: 2026-10-30 15:33In the Linux kernel, the following vulnerability has been resolved:
iio: imu: adis16400: fix unprotected debugfs reads
adis16400_serial_number_fops is open coded and never calls debugfs_file_get(), so debugfs_remove_recursive() does not wait for a read in progress and unbind frees the iio_dev underneath it.
Commit ae1d37a9bb4b ("iio: imu: adis16400: use DEFINE_DEBUGFS_ATTRIBUTE instead of DEFINE_SIMPLE_ATTRIBUTE") converted product_id and flash_count to DEFINE_DEBUGFS_ATTRIBUTE, which protects itself, but moved all three files to debugfs_create_file_unsafe().
serial_number prints three registers as "%.4x-%.4x-%.4x" and DEFINE_DEBUGFS_ATTRIBUTE() formats a single u64, so it cannot be converted without changing what the file returns. adis16475 and adis16550 already use debugfs_create_file() for their open coded files. Use it here too.
{
"affected": [],
"aliases": [
"CVE-2026-98664"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-18T16:17:19Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\niio: imu: adis16400: fix unprotected debugfs reads\n\nadis16400_serial_number_fops is open coded and never calls\ndebugfs_file_get(), so debugfs_remove_recursive() does not wait for a\nread in progress and unbind frees the iio_dev underneath it.\n\nCommit ae1d37a9bb4b (\"iio: imu: adis16400: use DEFINE_DEBUGFS_ATTRIBUTE\ninstead of DEFINE_SIMPLE_ATTRIBUTE\") converted product_id and\nflash_count to DEFINE_DEBUGFS_ATTRIBUTE, which protects itself, but\nmoved all three files to debugfs_create_file_unsafe().\n\nserial_number prints three registers as \"%.4x-%.4x-%.4x\" and\nDEFINE_DEBUGFS_ATTRIBUTE() formats a single u64, so it cannot be\nconverted without changing what the file returns. adis16475 and\nadis16550 already use debugfs_create_file() for their open coded\nfiles. Use it here too.",
"id": "GHSA-w4fg-xq8w-gq57",
"modified": "2026-10-30T15:33:54Z",
"published": "2026-10-18T18:31:58Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98664"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/48bb3c9b4a2fac64cb17c357418ebfbd4c9ac8ff"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/50e8d70ba0743f88afd7e49f9cebd1841ee677f5"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/69cc001761894c65a0eef1bb6df911b39d30d71e"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/d3078aaef8af4648f94eeafde4b7b36efd9838d1"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/d32eb2161b452a25b03f915f431bdcb9722cd92c"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/d94787287a113a1326211647d5e0deed1e9de105"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/e9b4c00f775a915b759b08bfe2c5e806a8301a59"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/f501302ebb9e1504162351b951fe3ae331c852ab"
}
],
"schema_version": "1.4.0",
"severity": []
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.