CVE-2021-47424: i40e: Fix freeing of uninitialized misc IRQ vector
Telemetry drift only. No threshold crossed and no authority ruling changed.
CVE record, CISA KEV and EPSS as of 2026-10-18.
CVEs like this one computed, by meaning
What to do now held facts and links
- Upgrade to the fixed version for your release line, or later: kernel 4.19.211; kernel 5.10.73; kernel 5.14.12; kernel 5.4.153 upper bounds of the CVE record's affected ranges
- Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
- Check your version against the ranges this record publishes.
What it is stated by the CNA
In the Linux kernel, the following vulnerability has been resolved: i40e: Fix freeing of uninitialized misc IRQ vector When VSI set up failed in i40e_probe() as part of PF switch set up driver was trying to free misc IRQ vectors in i40e_clear_interrupt_scheme and produced a kernel Oops: Trying to free already-free IRQ 266 WARNING: CPU: 0 PID: 5 at kernel/irq/manage.c:1731 __free_irq+0x9a/0x300 Workqueue: events work_for_cpu_fn RIP: 0010:__free_irq+0x9a/0x300 Call Trace: ? synchronize_irq+0x3a/0xa0 free_irq+0x2e/0x60 i40e_clear_interrupt_scheme+0x53/0x190 [i40e] i40e_probe.part.108+0x134b/0x1a40 [i40e] ? kmem_cache_alloc+0x158/0x1c0 ? acpi_ut_update_ref_count.part.1+0x8e/0x345 ? acpi_ut_update_object_reference+0x15e/0x1e2 ? strstr+0x21/0x70 ? irq_get_irq_data+0xa/0x20 ? mp_check_pin_attr+0x13/0xc0 ? irq_get_irq_data+0xa/0x20 ? …
- weakness
- Not named by the CNA. NVD maps it to CWE-908.
- affected
- Linux
- published ranges
- linux kernel >= 4.15 < 4.19.211; linux kernel >= 4.20 < 5.4.153; linux kernel >= 5.5 < 5.10.73; linux kernel >= 5.11 < 5.14.12; and 4 more on the CVE page
- first unaffected version, by branch
- kernel 4.19.211; kernel 5.10.73; kernel 5.14.12; kernel 5.4.153
- assigned by
- Linux
- published
- 2024-05-21
check us git.kernel.org git.kernel.org git.kernel.org git.kernel.org
Exploit code held, dated
- exploit code
- None held in the PoC-in-GitHub feed. A public repository changes this brief.
What moved held, dated
| date | EPSS | event |
|---|---|---|
| 22 May 2024 | 0.00045 | |
| 17 Mar 2025 | 0.00078 | scoring model v2025.03.14 |
| 29 Mar 2025 | 0.00328 | |
| 30 Mar 2025 | 0.00078 | |
| 29 Jun 2025 | 0.00039 | |
| 20 Jul 2025 | 0.00035 | |
| 22 Jul 2025 | 0.00033 | |
| 25 Sep 2025 | 0.00017 | |
| 22 Oct 2025 | 0.00029 | |
| 18 Nov 2025 | 0.00068 | |
| 21 Nov 2025 | 0.00029 | |
| 15 Jun 2026 | 0.00222 | scoring model v2026.06.15 |
12 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.
Outside the record researched, cited
This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.
What would change this brief held, dated
- CISA KEV
- Not listed in the catalogue we hold. A listing changes this brief.
- exploit probability
- 0.00 on 2026-06-15 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
- fix
- Held: kernel 4.19.211; kernel 5.10.73; kernel 5.14.12; kernel 5.4.153. A newer fix from the CNA or OSV changes this brief.
How to check this
Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:
SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2021-47424', '2026-10-31T23:59:59.999999Z', now());