GHSA-R949-42X5-FM64

Vulnerability from github – Published: 2026-06-03 18:33 – Updated: 2026-06-03 18:33
VLAI
Details

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.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-46246"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-06-03T18:16:24Z",
    "severity": null
  },
  "details": "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.",
  "id": "GHSA-r949-42x5-fm64",
  "modified": "2026-06-03T18:33:12Z",
  "published": "2026-06-03T18:33:12Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-46246"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/23067259919663580c6f81801847cfc7bd54fd1f"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/47abfc207ab02cf1297257e282e8048da63f0d08"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/48e0f68b50c344bb2d78d65dd98f93e41276ee00"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/9fab0120907e6965168e55b1e17cb9dfaf262b86"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…