GCVE Workshop - 22 September 2026 (14:00-18:00), Luxembourg Before The Vulnopticon Conference - Registration

GHSA-XCPR-V9RP-M43F

Vulnerability from github – Published: 2026-08-15 06:32 – Updated: 2026-08-15 06:32
VLAI
Details

In the Linux kernel, the following vulnerability has been resolved:

irqchip/ts4800: Fix missing chained handler cleanup on remove

The driver installs a chained handler for the parent interrupt during probe using irq_set_chained_handler_and_data(), but the remove function does not clear this handler. This leaves a dangling handler that may be called when the parent interrupt fires after the driver has been removed, potentially accessing freed memory and causing a kernel crash.

Additionally, the parent_irq obtained via irq_of_parse_and_map() is not stored, making it inaccessible in the remove function. Moreover, interrupt mappings created during probe are not properly disposed.

Fix this by:

  • Saving parent_irq in probe
  • Clearing the chained handler with NULL in ts4800_ic_remove()
  • Disposing all IRQ mappings before domain removal to prevent resource leaks
Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-72384"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-08-15T06:22:11Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nirqchip/ts4800: Fix missing chained handler cleanup on remove\n\nThe driver installs a chained handler for the parent interrupt during probe\nusing irq_set_chained_handler_and_data(), but the remove function does not\nclear this handler. This leaves a dangling handler that may be called when\nthe parent interrupt fires after the driver has been removed, potentially\naccessing freed memory and causing a kernel crash.\n\nAdditionally, the parent_irq obtained via irq_of_parse_and_map() is not\nstored, making it inaccessible in the remove function. Moreover, interrupt\nmappings created during probe are not properly disposed.\n\nFix this by:\n\n   - Saving parent_irq in probe\n   - Clearing the chained handler with NULL in ts4800_ic_remove()\n   - Disposing all IRQ mappings before domain removal to prevent resource\n     leaks",
  "id": "GHSA-xcpr-v9rp-m43f",
  "modified": "2026-08-15T06:32:22Z",
  "published": "2026-08-15T06:32:22Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-72384"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/3f31f49afffa169cd01e6c37568c4df3eb1051af"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/4e8d498d32b6c67d73bb8b317ff316ff37897a3e"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/98bf7e54cec07d514b3575c11896a8b12d50ecc4"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/9ed0dca2aa05908b33ecf0bb15c7953947529542"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/b5b2b2cb6a91908e6c23958c9ce6d5ba2fdb686c"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/e6b674dc341c6add7d85bec2ec22caf1aad35795"
    }
  ],
  "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…

Loading…