Answer in brief
CVE-2026-92482 records a Unknown severity vulnerability in pinctrl: mediatek: use devm_gpiochip_add_data() for GPIO chip. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=a6df410d420aa4ff316797d352f69e7ebae5ff98 <b8fa1098ee9f627d38bdf7c0ef6c1a6058a4165b || >=a6df410d420aa4ff316797d352f69e7ebae5ff98 <9c650317ba553d297f3fc5f0ae40ec53d86f9dab | b8fa1098ee9f627d38bdf7c0ef6c1a6058a4165b, 9c650317ba553d297f3fc5f0ae40ec53d86f9dab |
| Linux/Linuxgeneric | 4.1 | Not reported |
| Linux/Linuxgeneric | >=a6df410d420aa4ff316797d352f69e7ebae5ff98 <01b5fcdc30c0ab35af960b60508eae1f7f7d32fd || >=a6df410d420aa4ff316797d352f69e7ebae5ff98 <b8fa1098ee9f627d38bdf7c0ef6c1a6058a4165b || >=a6df410d420aa4ff316797d352f69e7ebae5ff98 <9c650317ba553d297f3fc5f0ae40ec53d86f9dab | 01b5fcdc30c0ab35af960b60508eae1f7f7d32fd, b8fa1098ee9f627d38bdf7c0ef6c1a6058a4165b, 9c650317ba553d297f3fc5f0ae40ec53d86f9dab |
| Linux/Linuxgeneric | >=a6df410d420aa4ff316797d352f69e7ebae5ff98 <dc6e5d802c88468290fee8826dd3a54cf58da25a || >=a6df410d420aa4ff316797d352f69e7ebae5ff98 <2490528a90a26f408ec3e95f865bad35454f9ff3 || >=a6df410d420aa4ff316797d352f69e7ebae5ff98 <01b5fcdc30c0ab35af960b60508eae1f7f7d32fd || >=a6df410d420aa4ff316797d352f69e7ebae5ff98 <b8fa1098ee9f627d38bdf7c0ef6c1a6058a4165b || >=a6df410d420aa4ff316797d352f69e7ebae5ff98 <9c650317ba553d297f3fc5f0ae40ec53d86f9dab | dc6e5d802c88468290fee8826dd3a54cf58da25a, 2490528a90a26f408ec3e95f865bad35454f9ff3, 01b5fcdc30c0ab35af960b60508eae1f7f7d32fd, b8fa1098ee9f627d38bdf7c0ef6c1a6058a4165b, 9c650317ba553d297f3fc5f0ae40ec53d86f9dab |
| Linux/Linuxgeneric | >=a6df410d420aa4ff316797d352f69e7ebae5ff98 <13a25cb4f0f0863afded5e915cb3bceede221426 || >=a6df410d420aa4ff316797d352f69e7ebae5ff98 <dc6e5d802c88468290fee8826dd3a54cf58da25a || >=a6df410d420aa4ff316797d352f69e7ebae5ff98 <2490528a90a26f408ec3e95f865bad35454f9ff3 || >=a6df410d420aa4ff316797d352f69e7ebae5ff98 <01b5fcdc30c0ab35af960b60508eae1f7f7d32fd || >=a6df410d420aa4ff316797d352f69e7ebae5ff98 <b8fa1098ee9f627d38bdf7c0ef6c1a6058a4165b || >=a6df410d420aa4ff316797d352f69e7ebae5ff98 <9c650317ba553d297f3fc5f0ae40ec53d86f9dab | 13a25cb4f0f0863afded5e915cb3bceede221426, dc6e5d802c88468290fee8826dd3a54cf58da25a, 2490528a90a26f408ec3e95f865bad35454f9ff3, 01b5fcdc30c0ab35af960b60508eae1f7f7d32fd, b8fa1098ee9f627d38bdf7c0ef6c1a6058a4165b, 9c650317ba553d297f3fc5f0ae40ec53d86f9dab |
Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 30, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 17, 2026
In the Linux kernel, the following vulnerability has been resolved: pinctrl: mediatek: use devm_gpiochip_add_data() for GPIO chip The gpio_chip is allocated with device-managed memory but registered with the non-managed gpiochip_add_data(). This was harmless while the drivers were built-in, but once they can be built as modules and unbound/rmmod'd, devm frees the gpio_chip's memory while it is still registered, causing a use-after-free. Register it with devm_gpiochip_add_data() so it shares the same device-managed lifecycle, which also lets the manual gpiochip_remove() error paths go away.
Quoted source text, attributed separately from HOL analysis.