{"api_version":"1","generated_at":"2026-11-19T23:50:34+00:00","cve":"CVE-2026-99189","urls":{"html":"https://cve.report/CVE-2026-99189","api":"https://cve.report/api/cve/CVE-2026-99189.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-99189","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-99189"},"summary":{"title":"gpio: mxc: fix race between chained IRQ handler install and probe completion","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ngpio: mxc: fix race between chained IRQ handler install and probe completion\n\nmxc_update_irq_chained_handler() is called before the IRQ domain, the\ngeneric IRQ chip, and the port list entry are set up. If an interrupt\narrives in that window:\n\n - mx3_gpio_irq_handler() calls generic_handle_domain_irq() with\n   port->domain still NULL.\n - mx2_gpio_irq_handler() walks mxc_gpio_ports, but the port has not\n   been added to the list yet.\n\nAdditionally, if any of the subsequent probe steps\n(gpio_generic_chip_init(), devm_gpiochip_add_data(),\nirq_domain_create_legacy(), or mxc_gpio_init_gc()) fail, the error\npaths never unregister the chained handler, leaving a dangling handler\nthat points at freed memory.\n\nMove the handler installation after all its dependencies are ready and\nafter list_add_tail(), so the handler is never live while the data\nstructures it touches are incomplete, and is never installed if probe\nfails.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-10-28 11:17:39","updated_at":"2026-10-28 11:17:39"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/6c1e035d881579a6e4ed1ce5feabb13d23e80a82","name":"https://git.kernel.org/stable/c/6c1e035d881579a6e4ed1ce5feabb13d23e80a82","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/38d44f78f041ffe60c8e2443b99434a199e7541d","name":"https://git.kernel.org/stable/c/38d44f78f041ffe60c8e2443b99434a199e7541d","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/261802c14e1a3281987ea8f106701e5ed9652f68","name":"https://git.kernel.org/stable/c/261802c14e1a3281987ea8f106701e5ed9652f68","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-99189","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99189","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 5f6d1998adeb5374ef248b5ba2e2a0c30ab0f60b 261802c14e1a3281987ea8f106701e5ed9652f68 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 5f6d1998adeb5374ef248b5ba2e2a0c30ab0f60b 6c1e035d881579a6e4ed1ce5feabb13d23e80a82 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 5f6d1998adeb5374ef248b5ba2e2a0c30ab0f60b 38d44f78f041ffe60c8e2443b99434a199e7541d git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.6","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.6 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.59 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.13 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/gpio/gpio-mxc.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"261802c14e1a3281987ea8f106701e5ed9652f68","status":"affected","version":"5f6d1998adeb5374ef248b5ba2e2a0c30ab0f60b","versionType":"git"},{"lessThan":"6c1e035d881579a6e4ed1ce5feabb13d23e80a82","status":"affected","version":"5f6d1998adeb5374ef248b5ba2e2a0c30ab0f60b","versionType":"git"},{"lessThan":"38d44f78f041ffe60c8e2443b99434a199e7541d","status":"affected","version":"5f6d1998adeb5374ef248b5ba2e2a0c30ab0f60b","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/gpio/gpio-mxc.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.6"},{"lessThan":"6.6","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.59","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.13","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.59","versionStartIncluding":"6.6","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.13","versionStartIncluding":"6.6","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3","versionStartIncluding":"6.6","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\ngpio: mxc: fix race between chained IRQ handler install and probe completion\n\nmxc_update_irq_chained_handler() is called before the IRQ domain, the\ngeneric IRQ chip, and the port list entry are set up. If an interrupt\narrives in that window:\n\n - mx3_gpio_irq_handler() calls generic_handle_domain_irq() with\n   port->domain still NULL.\n - mx2_gpio_irq_handler() walks mxc_gpio_ports, but the port has not\n   been added to the list yet.\n\nAdditionally, if any of the subsequent probe steps\n(gpio_generic_chip_init(), devm_gpiochip_add_data(),\nirq_domain_create_legacy(), or mxc_gpio_init_gc()) fail, the error\npaths never unregister the chained handler, leaving a dangling handler\nthat points at freed memory.\n\nMove the handler installation after all its dependencies are ready and\nafter list_add_tail(), so the handler is never live while the data\nstructures it touches are incomplete, and is never installed if probe\nfails."}],"providerMetadata":{"dateUpdated":"2026-10-28T10:35:46.366Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/261802c14e1a3281987ea8f106701e5ed9652f68"},{"url":"https://git.kernel.org/stable/c/6c1e035d881579a6e4ed1ce5feabb13d23e80a82"},{"url":"https://git.kernel.org/stable/c/38d44f78f041ffe60c8e2443b99434a199e7541d"}],"title":"gpio: mxc: fix race between chained IRQ handler install and probe completion","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-99189","datePublished":"2026-10-28T10:35:46.366Z","dateReserved":"2026-09-25T10:25:14.400Z","dateUpdated":"2026-10-28T10:35:46.366Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-10-28 11:17:39","lastModifiedDate":"2026-10-28 11:17:39","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"99189","Ordinal":"1","Title":"gpio: mxc: fix race between chained IRQ handler install and prob","CVE":"CVE-2026-99189","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"99189","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\ngpio: mxc: fix race between chained IRQ handler install and probe completion\n\nmxc_update_irq_chained_handler() is called before the IRQ domain, the\ngeneric IRQ chip, and the port list entry are set up. If an interrupt\narrives in that window:\n\n - mx3_gpio_irq_handler() calls generic_handle_domain_irq() with\n   port->domain still NULL.\n - mx2_gpio_irq_handler() walks mxc_gpio_ports, but the port has not\n   been added to the list yet.\n\nAdditionally, if any of the subsequent probe steps\n(gpio_generic_chip_init(), devm_gpiochip_add_data(),\nirq_domain_create_legacy(), or mxc_gpio_init_gc()) fail, the error\npaths never unregister the chained handler, leaving a dangling handler\nthat points at freed memory.\n\nMove the handler installation after all its dependencies are ready and\nafter list_add_tail(), so the handler is never live while the data\nstructures it touches are incomplete, and is never installed if probe\nfails.","Type":"Description","Title":"gpio: mxc: fix race between chained IRQ handler install and prob"}]}}}