Answer in brief
CVE-2026-72424 records a Unknown severity vulnerability in rtc: msc313: fix NULL deref in shared IRQ handler at probe. 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.
A CVSS score is not reported in the current record. 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 | >=be7d9c9161b9c76edeff15e79edc2f256568fe05 <ece7b9ffde23e2ccd7567761ac27463ded43932c || >=be7d9c9161b9c76edeff15e79edc2f256568fe05 <52c73b6992b46ed476590ed526faa033d4fbfc5d || >=be7d9c9161b9c76edeff15e79edc2f256568fe05 <bc1f61a9b97d65de21c2681bcf0b5b1392c58486 || >=be7d9c9161b9c76edeff15e79edc2f256568fe05 <1f6a4aec0d36647eb2f67cd69db22bd28cabe2cb || >=be7d9c9161b9c76edeff15e79edc2f256568fe05 <bb3e624808c981fe881cb79037be63e680ed7d38 || >=be7d9c9161b9c76edeff15e79edc2f256568fe05 <a369f48be8de426a7d2bca18dbd46c2ad1138803 | ece7b9ffde23e2ccd7567761ac27463ded43932c, 52c73b6992b46ed476590ed526faa033d4fbfc5d, bc1f61a9b97d65de21c2681bcf0b5b1392c58486, 1f6a4aec0d36647eb2f67cd69db22bd28cabe2cb, bb3e624808c981fe881cb79037be63e680ed7d38, a369f48be8de426a7d2bca18dbd46c2ad1138803 |
| Linux/Linuxgeneric | 5.16 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
In the Linux kernel, the following vulnerability has been resolved: rtc: msc313: fix NULL deref in shared IRQ handler at probe msc313_rtc_probe() calls devm_request_irq() with IRQF_SHARED and &pdev->dev as the cookie, but platform_set_drvdata() is only called later after the clock setup. With a shared IRQ line, another device on the same line can trigger the handler in that window. The handler does dev_get_drvdata() on the cookie, gets NULL, and dereferences priv->rtc_base in interrupt context. Pass priv as the cookie directly so the handler reads it from dev_id without the lookup, removing the dependency on probe order.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-72424 records a Unknown severity vulnerability in rtc: msc313: fix NULL deref in shared IRQ handler at probe. 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.
A CVSS score is not reported in the current record. 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 | >=be7d9c9161b9c76edeff15e79edc2f256568fe05 <ece7b9ffde23e2ccd7567761ac27463ded43932c || >=be7d9c9161b9c76edeff15e79edc2f256568fe05 <52c73b6992b46ed476590ed526faa033d4fbfc5d || >=be7d9c9161b9c76edeff15e79edc2f256568fe05 <bc1f61a9b97d65de21c2681bcf0b5b1392c58486 || >=be7d9c9161b9c76edeff15e79edc2f256568fe05 <1f6a4aec0d36647eb2f67cd69db22bd28cabe2cb || >=be7d9c9161b9c76edeff15e79edc2f256568fe05 <bb3e624808c981fe881cb79037be63e680ed7d38 || >=be7d9c9161b9c76edeff15e79edc2f256568fe05 <a369f48be8de426a7d2bca18dbd46c2ad1138803 | ece7b9ffde23e2ccd7567761ac27463ded43932c, 52c73b6992b46ed476590ed526faa033d4fbfc5d, bc1f61a9b97d65de21c2681bcf0b5b1392c58486, 1f6a4aec0d36647eb2f67cd69db22bd28cabe2cb, bb3e624808c981fe881cb79037be63e680ed7d38, a369f48be8de426a7d2bca18dbd46c2ad1138803 |
| Linux/Linuxgeneric | 5.16 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
In the Linux kernel, the following vulnerability has been resolved: rtc: msc313: fix NULL deref in shared IRQ handler at probe msc313_rtc_probe() calls devm_request_irq() with IRQF_SHARED and &pdev->dev as the cookie, but platform_set_drvdata() is only called later after the clock setup. With a shared IRQ line, another device on the same line can trigger the handler in that window. The handler does dev_get_drvdata() on the cookie, gets NULL, and dereferences priv->rtc_base in interrupt context. Pass priv as the cookie directly so the handler reads it from dev_id without the lookup, removing the dependency on probe order.
Quoted source text, attributed separately from HOL analysis.