{"api_version":"1","generated_at":"2026-10-01T05:18:51+00:00","cve":"CVE-2026-92482","urls":{"html":"https://cve.report/CVE-2026-92482","api":"https://cve.report/api/cve/CVE-2026-92482.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-92482","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-92482"},"summary":{"title":"pinctrl: mediatek: use devm_gpiochip_add_data() for GPIO chip","description":"In the Linux kernel, the following vulnerability has been resolved:\n\npinctrl: mediatek: use devm_gpiochip_add_data() for GPIO chip\n\nThe gpio_chip is allocated with device-managed memory but registered with\nthe non-managed gpiochip_add_data(). This was harmless while the drivers\nwere built-in, but once they can be built as modules and unbound/rmmod'd,\ndevm frees the gpio_chip's memory while it is still registered, causing a\nuse-after-free.\n\nRegister it with devm_gpiochip_add_data() so it shares the same\ndevice-managed lifecycle, which also lets the manual gpiochip_remove()\nerror paths go away.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-17 17:17:50","updated_at":"2026-09-17 17:17:50"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/b8fa1098ee9f627d38bdf7c0ef6c1a6058a4165b","name":"https://git.kernel.org/stable/c/b8fa1098ee9f627d38bdf7c0ef6c1a6058a4165b","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/9c650317ba553d297f3fc5f0ae40ec53d86f9dab","name":"https://git.kernel.org/stable/c/9c650317ba553d297f3fc5f0ae40ec53d86f9dab","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-92482","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-92482","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected a6df410d420aa4ff316797d352f69e7ebae5ff98 b8fa1098ee9f627d38bdf7c0ef6c1a6058a4165b git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected a6df410d420aa4ff316797d352f69e7ebae5ff98 9c650317ba553d297f3fc5f0ae40ec53d86f9dab git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 4.1","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 4.1 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.6 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-rc1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"92482","cve":"CVE-2026-92482","epss":"0.001890000","percentile":"0.088470000","score_date":"2026-09-18","updated_at":"2026-09-19 00:06:17"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/pinctrl/mediatek/pinctrl-moore.c","drivers/pinctrl/mediatek/pinctrl-mtk-common.c","drivers/pinctrl/mediatek/pinctrl-paris.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"b8fa1098ee9f627d38bdf7c0ef6c1a6058a4165b","status":"affected","version":"a6df410d420aa4ff316797d352f69e7ebae5ff98","versionType":"git"},{"lessThan":"9c650317ba553d297f3fc5f0ae40ec53d86f9dab","status":"affected","version":"a6df410d420aa4ff316797d352f69e7ebae5ff98","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/pinctrl/mediatek/pinctrl-moore.c","drivers/pinctrl/mediatek/pinctrl-mtk-common.c","drivers/pinctrl/mediatek/pinctrl-paris.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"4.1"},{"lessThan":"4.1","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.6","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.6","versionStartIncluding":"4.1","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc1","versionStartIncluding":"4.1","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\npinctrl: mediatek: use devm_gpiochip_add_data() for GPIO chip\n\nThe gpio_chip is allocated with device-managed memory but registered with\nthe non-managed gpiochip_add_data(). This was harmless while the drivers\nwere built-in, but once they can be built as modules and unbound/rmmod'd,\ndevm frees the gpio_chip's memory while it is still registered, causing a\nuse-after-free.\n\nRegister it with devm_gpiochip_add_data() so it shares the same\ndevice-managed lifecycle, which also lets the manual gpiochip_remove()\nerror paths go away."}],"providerMetadata":{"dateUpdated":"2026-09-17T16:09:59.019Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/b8fa1098ee9f627d38bdf7c0ef6c1a6058a4165b"},{"url":"https://git.kernel.org/stable/c/9c650317ba553d297f3fc5f0ae40ec53d86f9dab"}],"title":"pinctrl: mediatek: use devm_gpiochip_add_data() for GPIO chip","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-92482","datePublished":"2026-09-17T16:09:59.019Z","dateReserved":"2026-09-16T12:21:13.870Z","dateUpdated":"2026-09-17T16:09:59.019Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-17 17:17:50","lastModifiedDate":"2026-09-17 17:17:50","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"92482","Ordinal":"1","Title":"pinctrl: mediatek: use devm_gpiochip_add_data() for GPIO chip","CVE":"CVE-2026-92482","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"92482","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\npinctrl: mediatek: use devm_gpiochip_add_data() for GPIO chip\n\nThe gpio_chip is allocated with device-managed memory but registered with\nthe non-managed gpiochip_add_data(). This was harmless while the drivers\nwere built-in, but once they can be built as modules and unbound/rmmod'd,\ndevm frees the gpio_chip's memory while it is still registered, causing a\nuse-after-free.\n\nRegister it with devm_gpiochip_add_data() so it shares the same\ndevice-managed lifecycle, which also lets the manual gpiochip_remove()\nerror paths go away.","Type":"Description","Title":"pinctrl: mediatek: use devm_gpiochip_add_data() for GPIO chip"}]}}}