{"api_version":"1","generated_at":"2026-06-04T00:10:07+00:00","cve":"CVE-2026-46246","urls":{"html":"https://cve.report/CVE-2026-46246","api":"https://cve.report/api/cve/CVE-2026-46246.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-46246","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-46246"},"summary":{"title":"power: supply: pm8916_lbc: Fix use-after-free for extcon in IRQ handler","description":"In the Linux kernel, the following vulnerability has been resolved:\n\npower: supply: pm8916_lbc: Fix use-after-free for extcon in IRQ handler\n\nUsing the `devm_` variant for requesting IRQ _before_ the `devm_`\nvariant for allocating/registering the `extcon` handle, means that the\n`extcon` handle will be deallocated/unregistered _before_ the interrupt\nhandler (since `devm_` naturally deallocates in reverse allocation\norder). This means that during removal, there is a race condition where\nan interrupt can fire just _after_ the `extcon` handle has been\nfreed, *but* just _before_ the corresponding unregistration of the IRQ\nhandler has run.\n\nThis will lead to the IRQ handler calling `extcon_set_state_sync()` with\na freed `extcon` handle. Which usually crashes the system or otherwise\nsilently corrupts the memory...\n\nFix this racy use-after-free by making sure the IRQ is requested _after_\nthe registration of the `extcon` handle.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-06-03 18:16:24","updated_at":"2026-06-03 18:16:24"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/23067259919663580c6f81801847cfc7bd54fd1f","name":"https://git.kernel.org/stable/c/23067259919663580c6f81801847cfc7bd54fd1f","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/48e0f68b50c344bb2d78d65dd98f93e41276ee00","name":"https://git.kernel.org/stable/c/48e0f68b50c344bb2d78d65dd98f93e41276ee00","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/47abfc207ab02cf1297257e282e8048da63f0d08","name":"https://git.kernel.org/stable/c/47abfc207ab02cf1297257e282e8048da63f0d08","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/9fab0120907e6965168e55b1e17cb9dfaf262b86","name":"https://git.kernel.org/stable/c/9fab0120907e6965168e55b1e17cb9dfaf262b86","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-46246","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46246","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected f8d7a3d21160a0cab4d15b81231f2a76b0fcee13 9fab0120907e6965168e55b1e17cb9dfaf262b86 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected f8d7a3d21160a0cab4d15b81231f2a76b0fcee13 47abfc207ab02cf1297257e282e8048da63f0d08 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected f8d7a3d21160a0cab4d15b81231f2a76b0fcee13 48e0f68b50c344bb2d78d65dd98f93e41276ee00 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected f8d7a3d21160a0cab4d15b81231f2a76b0fcee13 23067259919663580c6f81801847cfc7bd54fd1f git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.7","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.7 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.75 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.14 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.19.4 6.19.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.0 * 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/power/supply/pm8916_lbc.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"9fab0120907e6965168e55b1e17cb9dfaf262b86","status":"affected","version":"f8d7a3d21160a0cab4d15b81231f2a76b0fcee13","versionType":"git"},{"lessThan":"47abfc207ab02cf1297257e282e8048da63f0d08","status":"affected","version":"f8d7a3d21160a0cab4d15b81231f2a76b0fcee13","versionType":"git"},{"lessThan":"48e0f68b50c344bb2d78d65dd98f93e41276ee00","status":"affected","version":"f8d7a3d21160a0cab4d15b81231f2a76b0fcee13","versionType":"git"},{"lessThan":"23067259919663580c6f81801847cfc7bd54fd1f","status":"affected","version":"f8d7a3d21160a0cab4d15b81231f2a76b0fcee13","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/power/supply/pm8916_lbc.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.7"},{"lessThan":"6.7","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.75","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.14","versionType":"semver"},{"lessThanOrEqual":"6.19.*","status":"unaffected","version":"6.19.4","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.0","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.75","versionStartIncluding":"6.7","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.14","versionStartIncluding":"6.7","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.19.4","versionStartIncluding":"6.7","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.0","versionStartIncluding":"6.7","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\npower: supply: pm8916_lbc: Fix use-after-free for extcon in IRQ handler\n\nUsing the `devm_` variant for requesting IRQ _before_ the `devm_`\nvariant for allocating/registering the `extcon` handle, means that the\n`extcon` handle will be deallocated/unregistered _before_ the interrupt\nhandler (since `devm_` naturally deallocates in reverse allocation\norder). This means that during removal, there is a race condition where\nan interrupt can fire just _after_ the `extcon` handle has been\nfreed, *but* just _before_ the corresponding unregistration of the IRQ\nhandler has run.\n\nThis will lead to the IRQ handler calling `extcon_set_state_sync()` with\na freed `extcon` handle. Which usually crashes the system or otherwise\nsilently corrupts the memory...\n\nFix this racy use-after-free by making sure the IRQ is requested _after_\nthe registration of the `extcon` handle."}],"providerMetadata":{"dateUpdated":"2026-06-03T15:49:41.607Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/9fab0120907e6965168e55b1e17cb9dfaf262b86"},{"url":"https://git.kernel.org/stable/c/47abfc207ab02cf1297257e282e8048da63f0d08"},{"url":"https://git.kernel.org/stable/c/48e0f68b50c344bb2d78d65dd98f93e41276ee00"},{"url":"https://git.kernel.org/stable/c/23067259919663580c6f81801847cfc7bd54fd1f"}],"title":"power: supply: pm8916_lbc: Fix use-after-free for extcon in IRQ handler","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-46246","datePublished":"2026-06-03T15:49:41.607Z","dateReserved":"2026-05-13T15:03:33.107Z","dateUpdated":"2026-06-03T15:49:41.607Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-06-03 18:16:24","lastModifiedDate":"2026-06-03 18:16:24","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"46246","Ordinal":"1","Title":"power: supply: pm8916_lbc: Fix use-after-free for extcon in IRQ ","CVE":"CVE-2026-46246","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"46246","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\npower: supply: pm8916_lbc: Fix use-after-free for extcon in IRQ handler\n\nUsing the `devm_` variant for requesting IRQ _before_ the `devm_`\nvariant for allocating/registering the `extcon` handle, means that the\n`extcon` handle will be deallocated/unregistered _before_ the interrupt\nhandler (since `devm_` naturally deallocates in reverse allocation\norder). This means that during removal, there is a race condition where\nan interrupt can fire just _after_ the `extcon` handle has been\nfreed, *but* just _before_ the corresponding unregistration of the IRQ\nhandler has run.\n\nThis will lead to the IRQ handler calling `extcon_set_state_sync()` with\na freed `extcon` handle. Which usually crashes the system or otherwise\nsilently corrupts the memory...\n\nFix this racy use-after-free by making sure the IRQ is requested _after_\nthe registration of the `extcon` handle.","Type":"Description","Title":"power: supply: pm8916_lbc: Fix use-after-free for extcon in IRQ "}]}}}