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

GHSA-CJFC-RQM4-H9MG

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/crossbar: Use correct index in crossbar_domain_free()

crossbar_domain_free() resets the domain data and then uses the nulled out irq_data->hwirq member as index to reset the irq_map[] entry and to write the relevant crossbar register with a safe entry. That means it never frees the correct index and keeps the crossbar register connection to the source interrupt active.

If it would not reset the domain data, then this would be even worse as irq_data->hwirq holds the source interrupt number, but both the map and register index need the corresponding GIC SPI number and not the source interrupt number. This might even result in an out of bounds access as the source interrupt number can be higher than the maximal index space.

Fix this by using the GIC SPI index from the parent domain's irq_data.

Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2026-72153"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-08-15T06:21:33Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nirqchip/crossbar: Use correct index in crossbar_domain_free()\n\ncrossbar_domain_free() resets the domain data and then uses the nulled\nout irq_data-\u003ehwirq member as index to reset the irq_map[] entry and to\nwrite the relevant crossbar register with a safe entry. That means it\nnever frees the correct index and keeps the crossbar register connection\nto the source interrupt active.\n\nIf it would not reset the domain data, then this would be even worse as\nirq_data-\u003ehwirq holds the source interrupt number, but both the map and\nregister index need the corresponding GIC SPI number and not the source\ninterrupt number. This might even result in an out of bounds access as\nthe source interrupt number can be higher than the maximal index space.\n\nFix this by using the GIC SPI index from the parent domain\u0027s irq_data.",
  "id": "GHSA-cjfc-rqm4-h9mg",
  "modified": "2026-08-15T06:32:14Z",
  "published": "2026-08-15T06:32:14Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-72153"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/043db005a8d6932dc7d217c86307e9af0bc10ddc"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/13bdb5140405ff283f9052e65ee1d5c2303765c7"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/1c48dc6a0c1ef47a9fa24611e60bc2f4ee4dd0df"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/36ca587f55a2c04468a89fd16174bb2f78dc04ec"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/424130169dc03b84ea604685409726d61bcec859"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/cca649a23a5fc8aae536fc27a0546c67690a4078"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/ccc3664679763d2d6f067c28729bdff627bb72d0"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/e5be5d452d5f1efbb3342da2b00029be6c99034e"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





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.


Detection rules are retrieved from Rulezet.