Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-72153: irqchip/crossbar: Use correct index in crossbar_domain_free()

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
  • Fixed version: Linux Linux 043db005a8d6932dc7d217c86307e9af0bc10ddc, 13bdb5140405ff283f9052e65ee1d5c2303765c7, 1c48dc6a0c1ef47a9fa24611e60bc2f4ee4dd0df.

Low priority for now. Upgrade to Linux Linux 043db005a8d6932dc7d217c86307e9af0bc10ddc, 13bdb5140405ff283f9052e65ee1d5c2303765c7, 1c48dc6a0c1ef47a9fa24611e60bc2f4ee4dd0df or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Aug 15, 2026
Updated
Aug 17, 2026
EPSS
0.2% · 12th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-72153

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.1affected
    • 783d31863fb826f1a3754a2d5959a022a1b12d54 and later · before 13bdb5140405ff283f9052e65ee1d5c2303765c7affected · git
    • 783d31863fb826f1a3754a2d5959a022a1b12d54 and later · before 1c48dc6a0c1ef47a9fa24611e60bc2f4ee4dd0dfaffected · git
    • 783d31863fb826f1a3754a2d5959a022a1b12d54 and later · before ccc3664679763d2d6f067c28729bdff627bb72d0affected · git
    • 783d31863fb826f1a3754a2d5959a022a1b12d54 and later · before 424130169dc03b84ea604685409726d61bcec859affected · git
    • 783d31863fb826f1a3754a2d5959a022a1b12d54 and later · before cca649a23a5fc8aae536fc27a0546c67690a4078affected · git
    • 783d31863fb826f1a3754a2d5959a022a1b12d54 and later · before 36ca587f55a2c04468a89fd16174bb2f78dc04ecaffected · git
    • 783d31863fb826f1a3754a2d5959a022a1b12d54 and later · before e5be5d452d5f1efbb3342da2b00029be6c99034eaffected · git
    • 783d31863fb826f1a3754a2d5959a022a1b12d54 and later · before 043db005a8d6932dc7d217c86307e9af0bc10ddcaffected · git
    • before 4.1not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.180-16.1.180-1
Debian:13linuxbefore 6.12.100-16.12.100-1
Debian:14linuxbefore 7.1.5-17.1.5-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-72151Aug 15, 2026 · tpm: tpm2-sessions: wait for async KPP completion in tpm_buf_append_salt
    33Monitor
  • ← EarlierCVE-2026-72152Aug 15, 2026 · tpm: tpm_tis_spi: Use wait_woken() in wait_for_tmp_stat()
    0Monitor
  • Later →CVE-2026-72154Aug 15, 2026 · openrisc: Fix jump_label smp syncing
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux043db005a8d6932dc7d217c86307e9af0bc10ddcVendor (CNA)
Linux Linux13bdb5140405ff283f9052e65ee1d5c2303765c7Vendor (CNA)
Linux Linux1c48dc6a0c1ef47a9fa24611e60bc2f4ee4dd0dfVendor (CNA)
Linux Linux36ca587f55a2c04468a89fd16174bb2f78dc04ecVendor (CNA)
Linux Linux424130169dc03b84ea604685409726d61bcec859Vendor (CNA)
Linux Linuxcca649a23a5fc8aae536fc27a0546c67690a4078Vendor (CNA)
Linux Linuxccc3664679763d2d6f067c28729bdff627bb72d0Vendor (CNA)
Linux Linuxe5be5d452d5f1efbb3342da2b00029be6c99034eVendor (CNA)
debian:linux6.1.180-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records