Skip to content
Heist/ feed
Back to feed
UnratedFix available

power: supply: pm8916_lbc: Fix use-after-free for extcon in IRQ handler

Type: advisorySources: OSV

In the Linux kernel, the following vulnerability has been resolved: power: supply: pm8916_lbc: Fix use-after-free for extcon in IRQ handler Using the `devm_` variant for requesting IRQ _before_ the `devm_` variant for allocating/registering the `extcon` handle, means that the `extcon` handle will be deallocated/unregistered _before_ the interrupt handler (since `devm_` naturally deallocates in reverse allocation order). This means that during removal, there is a race condition where an interrupt can fire just _after_ the `extcon` handle has been freed, *but* just _before_ the corresponding unregistration of the IRQ handler has run. This will lead to the IRQ handler calling `extcon_set_state_sync()` with a freed `extcon` handle. Which usually crashes the system or otherwise silently corrupts the memory... Fix this racy use-after-free by making sure the IRQ is requested _after_ the registration of the `extcon` handle.

Products
Kernel
Affected versions
Not specified
Fixed versions
6.12.75, 6.18.14, 6.19.4
CVEs
CVE-2026-46246
Confirmed fixed CVEs
Not specified
Updated in this feed
2 Nov 2026, 19:51 UTC · Revision 1

Source evidence

power: supply: pm8916_lbc: Fix use-after-free for extcon in IRQ handler

core-osv · Original source

Published 3 Jun 2026, 15:49 UTC

In the Linux kernel, the following vulnerability has been resolved: power: supply: pm8916_lbc: Fix use-after-free for extcon in IRQ handler Using the `devm_` variant for requesting IRQ _before_ the `devm_` variant for allocating/registering the `extcon` handle, means that the `extcon` handle will be deallocated/unregistered _before_ the interrupt handler (since `devm_` naturally deallocates in reverse allocation order). This means that during removal, there is a race condition where an interrupt can fire just _after_ the `extcon` handle has been freed, *but* just _before_ the corresponding unregistration of the IRQ handler has run. This will lead to the IRQ handler calling `extcon_set_state_sync()` with a freed `extcon` handle. Which usually crashes the system or otherwise silently corrupts the memory... Fix this racy use-after-free by making sure the IRQ is requested _after_ the registration of the `extcon` handle.

osv:CVE-2026-46246

Kernel

Fixed versions: 6.12.75, 6.18.14, 6.19.4

Complete source record
{
  "id": "8f4b88146c63326edb744d651003379d348b391dd9b6c9fe61124f7d3b937122",
  "url": "https://osv.dev/vulnerability/CVE-2026-46246",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "power: supply: pm8916_lbc: Fix use-after-free for extcon in IRQ handler",
    "summary": "In the Linux kernel, the following vulnerability has been resolved: power: supply: pm8916_lbc: Fix use-after-free for extcon in IRQ handler Using the `devm_` variant for requesting IRQ _before_ the `devm_` variant for allocating/registering the `extcon` handle, means that the `extcon` handle will be deallocated/unregistered _before_ the interrupt handler (since `devm_` naturally deallocates in reverse allocation order). This means that during removal, there is a race condition where an interrupt can fire just _after_ the `extcon` handle has been freed, *but* just _before_ the corresponding unregistration of the IRQ handler has run. This will lead to the IRQ handler calling `extcon_set_state_sync()` with a freed `extcon` handle. Which usually crashes the system or otherwise silently corrupts the memory... Fix this racy use-after-free by making sure the IRQ is requested _after_ the registration of the `extcon` handle.",
    "evidence": "osv:CVE-2026-46246",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "6.12.75",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.18.14",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.19.4",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "unknown",
    "structured": {
      "id": "CVE-2026-46246",
      "aliases": [
        "CVE-2026-46246"
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "f8d7a3d21160a0cab4d15b81231f2a76b0fcee13"
                },
                {
                  "fixed": "9fab0120907e6965168e55b1e17cb9dfaf262b86"
                },
                {
                  "fixed": "47abfc207ab02cf1297257e282e8048da63f0d08"
                },
                {
                  "fixed": "48e0f68b50c344bb2d78d65dd98f93e41276ee00"
                },
                {
                  "fixed": "23067259919663580c6f81801847cfc7bd54fd1f"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-46246.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.7.0"
                },
                {
                  "fixed": "6.12.75"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.13.0"
                },
                {
                  "fixed": "6.18.14"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.19.0"
                },
                {
                  "fixed": "6.19.4"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-46246.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:23.255370808Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/23067259919663580c6f81801847cfc7bd54fd1f",
        "https://git.kernel.org/stable/c/47abfc207ab02cf1297257e282e8048da63f0d08",
        "https://git.kernel.org/stable/c/48e0f68b50c344bb2d78d65dd98f93e41276ee00",
        "https://git.kernel.org/stable/c/9fab0120907e6965168e55b1e17cb9dfaf262b86",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/46xxx/CVE-2026-46246.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-46246",
        "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
      ],
      "provider_metadata": {
        "cna_assigner": "Linux",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/46xxx/CVE-2026-46246.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-46246",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": null
  },
  "source_id": "core-osv",
  "document_id": 489419,
  "published_at": "2026-06-03T15:49:41.607+00:00"
}