Answer in brief
CVE-2026-89769 records a High severity (CVSS 7.4) vulnerability in clocksource/drivers/nxp-pit: Fix IRQ leak on cpuhp_setup_state error path. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.4. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=bee33f22d7c30626e711b4900e3f460b6e0e104f <d53c29a89a15e56a1797f3ef249955e544782e04 || >=bee33f22d7c30626e711b4900e3f460b6e0e104f <cdcd861123248e871c2ec2be968b0a1b2a5a34b0 || >=bee33f22d7c30626e711b4900e3f460b6e0e104f <05520e035f8332c8e33f3011b5ca016fde61793d | d53c29a89a15e56a1797f3ef249955e544782e04, cdcd861123248e871c2ec2be968b0a1b2a5a34b0, 05520e035f8332c8e33f3011b5ca016fde61793d |
| Linux/Linuxgeneric | 6.18 | Not reported |
Published upstream
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 11, 2026
In the Linux kernel, the following vulnerability has been resolved: clocksource/drivers/nxp-pit: Fix IRQ leak on cpuhp_setup_state error path When cpuhp_setup_state fails after pit_clockevent_per_cpu_init has successfully called request_irq, the error handling jumps directly to out_pit_clocksource_unregister without freeing the registered IRQ. This leaks the IRQ line and, since kfree(pit) follows, leaves a dangling pointer registered as the interrupt handler's dev_id, potentially leading to a use-after-free if the IRQ fires afterwards. Fix it by calling pit_clockevent_per_cpu_exit to properly release the IRQ before falling through to the existing cleanup chain.
Quoted source text, attributed separately from HOL analysis.