{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-92481 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-92481 is an use after free vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-92481 and fix it if it is affected.\n\nWhat it is: CVE-2026-92481 is an use after free vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-92481 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-92481/ (Markdown: https://insights.sbomify.com/CVE-2026-92481/index.md)","id":"CVE-2026-92481","markdown":"https://insights.sbomify.com/CVE-2026-92481/index.md","name":"CVE-2026-92481","record":{"aliases":["BELL-CVE-2026-92481","DEBIAN-CVE-2026-92481","GHSA-fmh8-wm6j-9mrf","UBUNTU-CVE-2026-92481"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel driver","requires_auth":"high_privilege","summary":"A use-after-free vulnerability in the MediaTek pinctrl driver allows local attackers with module loading privileges to execute arbitrary code or cause a system crash.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\npinctrl: mediatek: free EINT resources on unbind\n\nmtk_eint_do_init() creates an IRQ domain, populates it with a mapping for\nevery EINT line and installs a chained handler on the parent interrupt,\nbut none of these are ever released. This was harmless while the drivers\nwere built-in, but now that they can be built as modules and\nunbound/rmmod'd it leaves behind a dangling IRQ domain, interrupt mappings\nwhose chip data points at freed memory, and a chained handler that keeps\nfiring into that freed data.\n\nThe plain allocations in mtk_eint_do_init() already use the device-managed\ndevm_*() helpers, so tear the remaining resources down the same way:\nregister a devm action that detaches the chained handler, waits for any\nin-flight handler to finish, disposes of the per-line mappings and removes\nthe IRQ domain. This mirrors the device-managed lifecycle adopted for the\nGPIO chip and keeps the whole EINT setup self-cleaning on unbind.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"pinctrl: mediatek: free EINT resources on unbind","id":"CVE-2026-92481","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"pinctrl: mediatek: use devm_gpiochip_add_data() for GPIO chip","id":"CVE-2026-92482"},"packages":[],"prev":{"headline":"scsi: ufs: core: Validate string descriptors","id":"CVE-2026-92480"},"products":["Linux"],"published":"2026-09-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A use-after-free vulnerability in the MediaTek pinctrl driver allows local attackers with module loading privileges to execute arbitrary code or cause a system crash.","url":"https://insights.sbomify.com/CVE-2026-92481/"}