CVE-2026-31506
Double Free Vulnerability in Linux Kernel net:bcmasp WoL IRQ
Publication date: 2026-04-22
Last updated on: 2026-04-28
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.6 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | From 6.13 (inc) to 6.18.21 (exc) |
| linux | linux_kernel | From 6.19 (inc) to 6.19.11 (exc) |
| linux | linux_kernel | From 6.6.1 (inc) to 6.12.80 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-415 | The product calls free() twice on the same memory address. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a double free issue in the Linux kernel's bcmasp network driver related to the Wake-on-LAN (WoL) interrupt request (irq). Specifically, the code incorrectly frees the wol_irq resource twice. The problem arises because wol_irq was allocated using devm_request_irq(), which automatically manages the resource's lifecycle, so manually freeing it again causes a double free error.
How can this vulnerability impact me? :
A double free vulnerability can lead to undefined behavior such as memory corruption, system crashes, or potential exploitation by attackers to execute arbitrary code or cause denial of service. In this case, the double free of the WoL irq in the Linux kernel could destabilize the system or be leveraged by an attacker to compromise system integrity.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability in the Linux kernel related to a double free of WoL irq has been fixed by ensuring that wol_irq is not freed manually since it is managed by devm_request_irq().
To mitigate this vulnerability, you should update your Linux kernel to the version where this fix has been applied.