Answer in brief
CVE-2025-23155 records a Unknown severity vulnerability in net: stmmac: Fix accessing freed irq affinity_hint. 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 | >=8deec94c6040bb4a767f6e9456a0a44c7f2e713e <2fbf67ddb8a0d0efc00d2df496a9843ec318d48b || >=8deec94c6040bb4a767f6e9456a0a44c7f2e713e <960dab23f6d405740c537d095f90a4ee9ddd9285 || >=8deec94c6040bb4a767f6e9456a0a44c7f2e713e <442312c2a90d60c7a5197246583fa91d9e579985 || >=8deec94c6040bb4a767f6e9456a0a44c7f2e713e <e148266e104fce396ad624079a6812ac3a9982ef || >=8deec94c6040bb4a767f6e9456a0a44c7f2e713e <9e51a6a44e2c4de780a26e8fe110d708e806a8cd || >=8deec94c6040bb4a767f6e9456a0a44c7f2e713e <c60d101a226f18e9a8f01bb4c6ca2b47dfcb15ef | 2fbf67ddb8a0d0efc00d2df496a9843ec318d48b, 960dab23f6d405740c537d095f90a4ee9ddd9285, 442312c2a90d60c7a5197246583fa91d9e579985, e148266e104fce396ad624079a6812ac3a9982ef, 9e51a6a44e2c4de780a26e8fe110d708e806a8cd, c60d101a226f18e9a8f01bb4c6ca2b47dfcb15ef |
| Linux/Linuxgeneric | 5.13 | Not reported |
Published upstream
May 1, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: net: stmmac: Fix accessing freed irq affinity_hint In stmmac_request_irq_multi_msi(), a pointer to the stack variable cpu_mask is passed to irq_set_affinity_hint(). This value is stored in irq_desc->affinity_hint, but once stmmac_request_irq_multi_msi() returns, the pointer becomes dangling. The affinity_hint is exposed via procfs with S_IRUGO permissions, allowing any unprivileged process to read it. Accessing this stale pointer can lead to: - a kernel oops or panic if the referenced memory has been released and unmapped, or - leakage of kernel data into userspace if the memory is re-used for other purposes. All platforms that use stmmac with PCI MSI (Intel, Loongson, etc) are affected.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2025-23155 records a Unknown severity vulnerability in net: stmmac: Fix accessing freed irq affinity_hint. 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 | >=8deec94c6040bb4a767f6e9456a0a44c7f2e713e <2fbf67ddb8a0d0efc00d2df496a9843ec318d48b || >=8deec94c6040bb4a767f6e9456a0a44c7f2e713e <960dab23f6d405740c537d095f90a4ee9ddd9285 || >=8deec94c6040bb4a767f6e9456a0a44c7f2e713e <442312c2a90d60c7a5197246583fa91d9e579985 || >=8deec94c6040bb4a767f6e9456a0a44c7f2e713e <e148266e104fce396ad624079a6812ac3a9982ef || >=8deec94c6040bb4a767f6e9456a0a44c7f2e713e <9e51a6a44e2c4de780a26e8fe110d708e806a8cd || >=8deec94c6040bb4a767f6e9456a0a44c7f2e713e <c60d101a226f18e9a8f01bb4c6ca2b47dfcb15ef | 2fbf67ddb8a0d0efc00d2df496a9843ec318d48b, 960dab23f6d405740c537d095f90a4ee9ddd9285, 442312c2a90d60c7a5197246583fa91d9e579985, e148266e104fce396ad624079a6812ac3a9982ef, 9e51a6a44e2c4de780a26e8fe110d708e806a8cd, c60d101a226f18e9a8f01bb4c6ca2b47dfcb15ef |
| Linux/Linuxgeneric | 5.13 | Not reported |
Published upstream
May 1, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: net: stmmac: Fix accessing freed irq affinity_hint In stmmac_request_irq_multi_msi(), a pointer to the stack variable cpu_mask is passed to irq_set_affinity_hint(). This value is stored in irq_desc->affinity_hint, but once stmmac_request_irq_multi_msi() returns, the pointer becomes dangling. The affinity_hint is exposed via procfs with S_IRUGO permissions, allowing any unprivileged process to read it. Accessing this stale pointer can lead to: - a kernel oops or panic if the referenced memory has been released and unmapped, or - leakage of kernel data into userspace if the memory is re-used for other purposes. All platforms that use stmmac with PCI MSI (Intel, Loongson, etc) are affected.
Quoted source text, attributed separately from HOL analysis.