CVE-2025-23155
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 7.1 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Record status
- Modified
Affected
- Linux Kernel < 6.12.36
- Linux Kernel < 6.13.12
- Linux Kernel < 6.14.3
Attack profile CVSS 3.1 · 7.1
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2025-23155.md and follow it. Check whether this project is affected by CVE-2025-23155. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/2fbf67ddb8a0d0efc00d2df496a9843ec318d48b
- https://git.kernel.org/stable/c/442312c2a90d60c7a5197246583fa91d9e579985
- https://git.kernel.org/stable/c/960dab23f6d405740c537d095f90a4ee9ddd9285
- https://git.kernel.org/stable/c/9e51a6a44e2c4de780a26e8fe110d708e806a8cd
- https://git.kernel.org/stable/c/c60d101a226f18e9a8f01bb4c6ca2b47dfcb15ef
- https://git.kernel.org/stable/c/e148266e104fce396ad624079a6812ac3a9982ef
References
- https://git.kernel.org/stable/c/2fbf67ddb8a0d0efc00d2df496a9843ec318d48b
- https://git.kernel.org/stable/c/442312c2a90d60c7a5197246583fa91d9e579985
- https://git.kernel.org/stable/c/960dab23f6d405740c537d095f90a4ee9ddd9285
- https://git.kernel.org/stable/c/9e51a6a44e2c4de780a26e8fe110d708e806a8cd
- https://git.kernel.org/stable/c/c60d101a226f18e9a8f01bb4c6ca2b47dfcb15ef
- https://git.kernel.org/stable/c/e148266e104fce396ad624079a6812ac3a9982ef