BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2024
CVE-2021-47589High confidence

igbvf: fix double free in `igbvf_probe`

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 11 May 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.26% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

5 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 1 affected package state shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.15.15-1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.15.15-1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.15.15-1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.15.15-1Debian Security Tracker ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2021-47589 · CSAF 2.0 · revision 68 · interimSUSE Product Security TeamCVE-2021-47589
110 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
Summary
In the Linux kernel, the following vulnerability has been resolved: igbvf: fix double free in `igbvf_probe` In `igbvf_probe`, if register_netdev() fails, the program will go to label err_hw_init, and then to label err_ioremap. In free_netdev() which is just below label err_ioremap, there is `list_for_each_entry_safe` and `netif_napi_del` which aims to delete all entries in `dev->napi_list`. The program has added an entry `adapter->rx_ring->napi` which is added by `netif_napi_add` in igbvf_alloc_queues(). However, adapter->rx_ring has been freed below label err_hw_init. So this a UAF. In terms of how to patch the problem, we can refer to igbvf_remove() and delete the entry before `adapter->rx_ring`. The KASAN logs are as follows: [ 35.126075] BUG: KASAN: use-after-free in free_netdev+0x1fd/0x450 [ 35.127170] Read of size 8 at addr ffff88810126d990 by task modprobe/366 [ 35.128360] [ 35.128643] CPU: 1 PID: 366 Comm: modprobe Not tainted 5.15.0-rc2+ #14 [ 35.129789] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.12.0-59-gc9ba5276e321-prebuilt.qemu.org 04/01/2014 [ 35.131749] Call Trace: [ 35.132199] dump_stack_lvl+0x59/0x7b [ 35.132865] print_address_description+0x7c/0x3b0 [ 35.133707] ? free_netdev+0x1fd/0x450 [ 35.134378] __kasan_report+0x160/0x1c0 [ 35.135063] ? free_netdev+0x1fd/0x450 [ 35.135738] kasan_report+0x4b/0x70 [ 35.136367] free_netdev+0x1fd/0x450 [ 35.137006] igbvf_probe+0x121d/0x1a10 [igbvf] [ 35.137808] ? igbvf_vlan_rx_add_vid+0x100/0x100 [igbvf] [ 35.138751] local_pci_probe+0x13c/0x1f0 [ 35.139461] pci_device_probe+0x37e/0x6c0 [ 35.165526] [ 35.165806] Allocated by task 366: [ 35.166414] ____kasan_kmalloc+0xc4/0xf0 [ 35.167117] foo_kmem_cache_alloc_trace+0x3c/0x50 [igbvf] [ 35.168078] igbvf_probe+0x9c5/0x1a10 [igbvf] [ 35.168866] local_pci_probe+0x13c/0x1f0 [ 35.169565] pci_device_probe+0x37e/0x6c0 [ 35.179713] [ 35.179993] Freed by task 366: [ 35.180539] kasan_set_track+0x4c/0x80 [ 35.181211] kasan_set_free_info+0x1f/0x40 [ 35.181942] ____kasan_slab_free+0x103/0x140 [ 35.182703] kfree+0xe3/0x250 [ 35.183239] igbvf_probe+0x1173/0x1a10 [igbvf] [ 35.184040] local_pci_probe+0x13c/0x1f0
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2021-34591

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: igbvf: fix double free in `igbvf_probe` In `igbvf_probe`, if register_netdev() fails, the program will go to label err_hw_init, and then to label err_ioremap. In free_netdev() which is just below label err_ioremap, there is `list_for_each_entry_safe` and `netif_napi_del` which aims to delete all entries in `dev->napi_list`. The program has added an entry `adapter->rx_ring->napi` which is added by `netif_napi_add` in igbvf_alloc_queues(). However, adapter->rx_ring has been freed below label err_hw_init. So this a UAF. In terms of how to patch the problem, we can refer to igbvf_remove() and delete the entry before `adapter->rx_ring`. The KASAN logs are as follows: [ 35.126075] BUG: KASAN: use-after-free in free_netdev+0x1fd/0x450 [ 35.127170] Read of size 8 at addr ffff88810126d990 by task modprobe/366 [ 35.128360] [ 35.128643] CPU: 1 PID: 366 Comm: modprobe Not tainted 5.15.0-rc2+ #14 [ 35.129789] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.12.0-59-gc9ba5276e321-prebuilt.qemu.org 04/01/2014 [ 35.131749] Call Trace: [ 35.132199] dump_stack_lvl+0x59/0x7b [ 35.132865] print_address_description+0x7c/0x3b0 [ 35.133707] ? free_netdev+0x1fd/0x450 [ 35.134378] __kasan_report+0x160/0x1c0 [ 35.135063] ? free_netdev+0x1fd/0x450 [ 35.135738] kasan_report+0x4b/0x70 [ 35.136367] free_netdev+0x1fd/0x450 [ 35.137006] igbvf_probe+0x121d/0x1a10 [igbvf] [ 35.137808] ? igbvf_vlan_rx_add_vid+0x100/0x100 [igbvf] [ 35.138751] local_pci_probe+0x13c/0x1f0 [ 35.139461] pci_device_probe+0x37e/0x6c0 [ 35.165526] [ 35.165806] Allocated by task 366: [ 35.166414] ____kasan_kmalloc+0xc4/0xf0 [ 35.167117] foo_kmem_cache_alloc_trace+0x3c/0x50 [igbvf] [ 35.168078] igbvf_probe+0x9c5/0x1a10 [igbvf] [ 35.168866] local_pci_probe+0x13c/0x1f0 [ 35.169565] pci_device_probe+0x37e/0x6c0 [ 35.179713] [ 35.179993] Freed by task 366: [ 35.180539] kasan_set_track+0x4c/0x80 [ 35.181211] kasan_set_free_info+0x1f/0x40 [ 35.181942] ____kasan_slab_free+0x103/0x140 [ 35.182703] kfree+0xe3/0x250 [ 35.183239] igbvf_probe+0x1173/0x1a10 [igbvf] [ 35.184040] local_pci_probe+0x13c/0x1f0

What

In the Linux kernel, the following vulnerability has been resolved: igbvf: fix double free in `igbvf_probe` In `igbvf_probe`, if register_netdev() fails, the program will go to label err_hw_init, and then to label err_ioremap. In free_netdev() which is just below label err_ioremap, there is `list_for_each_entry_safe` and `netif_napi_del` which aims to delete all entries in `dev->napi_list`. The program has added an entry `adapter->rx_ring->napi` which is added by `netif_napi_add` in igbvf_alloc_queues(). However, adapter->rx_ring has been freed below label err_hw_init. So this a UAF. In terms of how to patch the problem, we can refer to igbvf_remove() and delete the entry before `adapter->rx_ring`. The KASAN logs are as follows: [ 35.126075] BUG: KASAN: use-after-free in free_netdev+0x1fd/0x450 [ 35.127170] Read of size 8 at addr ffff88810126d990 by task modprobe/366 [ 35.128360] [ 35.128643] CPU: 1 PID: 366 Comm: modprobe Not tainted 5.15.0-rc2+ #14 [ 35.129789] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.12.0-59-gc9ba5276e321-prebuilt.qemu.org 04/01/2014 [ 35.131749] Call Trace: [ 35.132199] dump_stack_lvl+0x59/0x7b [ 35.132865] print_address_description+0x7c/0x3b0 [ 35.133707] ? free_netdev+0x1fd/0x450 [ 35.134378] __kasan_report+0x160/0x1c0 [ 35.135063] ? free_netdev+0x1fd/0x450 [ 35.135738] kasan_report+0x4b/0x70 [ 35.136367] free_netdev+0x1fd/0x450 [ 35.137006] igbvf_probe+0x121d/0x1a10 [igbvf] [ 35.137808] ? igbvf_vlan_rx_add_vid+0x100/0x100 [igbvf] [ 35.138751] local_pci_probe+0x13c/0x1f0 [ 35.139461] pci_device_probe+0x37e/0x6c0 [ 35.165526] [ 35.165806] Allocated by task 366: [ 35.166414] ____kasan_kmalloc+0xc4/0xf0 [ 35.167117] foo_kmem_cache_alloc_trace+0x3c/0x50 [igbvf] [ 35.168078] igbvf_probe+0x9c5/0x1a10 [igbvf] [ 35.168866] local_pci_probe+0x13c/0x1f0 [ 35.169565] pci_device_probe+0x37e/0x6c0 [ 35.179713] [ 35.179993] Freed by task 366: [ 35.180539] kasan_set_track+0x4c/0x80 [ 35.181211] kasan_set_free_info+0x1f/0x40 [ 35.181942] ____kasan_slab_free+0x103/0x140 [ 35.182703] kfree+0xe3/0x250 [ 35.183239] igbvf_probe+0x1173/0x1a10 [igbvf] [ 35.184040] local_pci_probe+0x13c/0x1f0

Why

The product calls free() twice on the same memory address.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: igbvf: fix double free in `igbvf_probe` In `igbvf_probe`, if register_netdev() fails, the program will go to label err_hw_init, and then to label err_ioremap. In free_netdev() which is just below label err_ioremap, there is `list_for_each_entry_safe` and `netif_napi_del` which aims to delete all entries in `dev->napi_list`. The program has added an entry `adapter->rx_ring->napi` which is added by `netif_napi_add` in igbvf_alloc_queues(). However, adapter->rx_ring has been freed below label err_hw_init. So this a UAF. In terms of how to patch the problem, we can refer to igbvf_remove() and delete the entry before `adapter->rx_ring`. The KASAN logs are as follows: [ 35.126075] BUG: KASAN: use-after-free in free_netdev+0x1fd/0x450 [ 35.127170] Read of size 8 at addr ffff88810126d990 by task modprobe/366 [ 35.128360] [ 35.128643] CPU: 1 PID: 366 Comm: modprobe Not tainted 5.15.0-rc2+ #14 [ 35.129789] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.12.0-59-gc9ba5276e321-prebuilt.qemu.org 04/01/2014 [ 35.131749] Call Trace: [ 35.132199] dump_stack_lvl+0x59/0x7b [ 35.132865] print_address_description+0x7c/0x3b0 [ 35.133707] ? free_netdev+0x1fd/0x450 [ 35.134378] __kasan_report+0x160/0x1c0 [ 35.135063] ? free_netdev+0x1fd/0x450 [ 35.135738] kasan_report+0x4b/0x70 [ 35.136367] free_netdev+0x1fd/0x450 [ 35.137006] igbvf_probe+0x121d/0x1a10 [igbvf] [ 35.137808] ? igbvf_vlan_rx_add_vid+0x100/0x100 [igbvf] [ 35.138751] local_pci_probe+0x13c/0x1f0 [ 35.139461] pci_device_probe+0x37e/0x6c0 [ 35.165526] [ 35.165806] Allocated by task 366: [ 35.166414] ____kasan_kmalloc+0xc4/0xf0 [ 35.167117] foo_kmem_cache_alloc_trace+0x3c/0x50 [igbvf] [ 35.168078] igbvf_probe+0x9c5/0x1a10 [igbvf] [ 35.168866] local_pci_probe+0x13c/0x1f0 [ 35.169565] pci_device_probe+0x37e/0x6c0 [ 35.179713] [ 35.179993] Freed by task 366: [ 35.180539] kasan_set_track+0x4c/0x80 [ 35.181211] kasan_set_free_info+0x1f/0x40 [ 35.181942] ____kasan_slab_free+0x103/0x140 [ 35.182703] kfree+0xe3/0x250 [ 35.183239] igbvf_probe+0x1173/0x1a10 [igbvf] [ 35.184040] local_pci_probe+0x13c/0x1f0

Why

The product calls free() twice on the same memory address.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Double Free → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-415 ↗

CWE-415: Double Free. The product calls free() twice on the same memory address.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-415
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2024-1418Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20240626Security Bulletin 26 Jun 2024

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 26 Jun 2024, published on 26 June 2024. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1008Multiples vulnérabilités dans le noyau Linux d'Ubuntu

SN-7865-1 Bulletin de sécurité Ubuntu USN-7835-6 du 12 novembre 2025 https://ubuntu.com/security/notices/USN-7835-6 Bulletin de sécurité Ubuntu USN-7861-3 du 13 novembre 2025 https://ubuntu.com/security/notices/USN-7861-3 Bulletin de sécurité Ubuntu USN-7862-3 du 13 novembre 2025 https://ubuntu.com/security/notices/USN-7862-3 Référence CVE CVE-2021-47149 https://www.cve.org/CVERecord?id=CVE-2021-47149 Référence CVE CVE-2021-47294 https://www.cve.org/CVERecord?id=CVE-2021-47294 Référence CVE CVE-2021-47319 https://www.cve.org/CVERecord?id=CVE-2021-47319 Référence CVE CVE-2021-47330 https://www.cve.org/CVERecord?id=CVE-2021-47330 Référence CVE CVE-2021-47589 https://www.cve.org/CVERecord?id=CVE-2021-47589 Référence CVE CVE-2023-52574 https://www.cve.org/CVERecord?id=CVE-2023-52574 Référence CVE CVE-2023-52650 https://www.cve.org/CVERecord?id=CVE-2023-52650 Référence CVE CVE-2023-53034 https://www.cve.org/CVERecord?id=CVE-2023-53034 Référence CVE CVE-2024-27078 https://www.cve.org/CVERecord?id=CVE-2024-27078 Référence CVE CVE-2024-35849 https://www.cve.org/CVERecord?id=CVE-2024-35849 Référence CVE CVE-2024-41006 https://www.cve.org/CVERecord?id=CVE-2024-41006 Référence CVE CVE-2024-49924 https://www.cve.org/CVERecord?id=CVE-2024-49924 Référence CVE CVE-2024-50006 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0922Multiples vulnérabilités dans le noyau Linux d'Ubuntu

2 octobre 2025 https://ubuntu.com/security/notices/USN-7834-1 Bulletin de sécurité Ubuntu USN-7835-1 du 22 octobre 2025 https://ubuntu.com/security/notices/USN-7835-1 Bulletin de sécurité Ubuntu USN-7835-2 du 22 octobre 2025 https://ubuntu.com/security/notices/USN-7835-2 Bulletin de sécurité Ubuntu USN-7835-3 du 22 octobre 2025 https://ubuntu.com/security/notices/USN-7835-3 Bulletin de sécurité Ubuntu USN-7795-4 du 24 octobre 2025 https://ubuntu.com/security/notices/USN-7795-4 Référence CVE CVE-2021-47149 https://www.cve.org/CVERecord?id=CVE-2021-47149 Référence CVE CVE-2021-47319 https://www.cve.org/CVERecord?id=CVE-2021-47319 Référence CVE CVE-2021-47589 https://www.cve.org/CVERecord?id=CVE-2021-47589 Référence CVE CVE-2023-52593 https://www.cve.org/CVERecord?id=CVE-2023-52593 Référence CVE CVE-2023-52757 https://www.cve.org/CVERecord?id=CVE-2023-52757 Référence CVE CVE-2023-52975 https://www.cve.org/CVERecord?id=CVE-2023-52975 Référence CVE CVE-2023-53034 https://www.cve.org/CVERecord?id=CVE-2023-53034 Référence CVE CVE-2024-26700 https://www.cve.org/CVERecord?id=CVE-2024-26700 Référence CVE CVE-2024-26896 https://www.cve.org/CVERecord?id=CVE-2024-26896 Référence CVE CVE-2024-27078 https://www.cve.org/CVERecord?id=CVE-2024-27078 Référence CVE CVE-2024-35849 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0843Multiples vulnérabilités dans le noyau Linux d'Ubuntu

2 octobre 2025 https://ubuntu.com/security/notices/USN-7797-2 Bulletin de sécurité Ubuntu USN-7798-1 du 02 octobre 2025 https://ubuntu.com/security/notices/USN-7798-1 Bulletin de sécurité Ubuntu USN-7800-1 du 02 octobre 2025 https://ubuntu.com/security/notices/USN-7800-1 Bulletin de sécurité Ubuntu USN-7801-1 du 02 octobre 2025 https://ubuntu.com/security/notices/USN-7801-1 Bulletin de sécurité Ubuntu USN-7802-1 du 02 octobre 2025 https://ubuntu.com/security/notices/USN-7802-1 Référence CVE CVE-2021-47149 https://www.cve.org/CVERecord?id=CVE-2021-47149 Référence CVE CVE-2021-47319 https://www.cve.org/CVERecord?id=CVE-2021-47319 Référence CVE CVE-2021-47589 https://www.cve.org/CVERecord?id=CVE-2021-47589 Référence CVE CVE-2022-48703 https://www.cve.org/CVERecord?id=CVE-2022-48703 Référence CVE CVE-2024-26726 https://www.cve.org/CVERecord?id=CVE-2024-26726 Référence CVE CVE-2024-26775 https://www.cve.org/CVERecord?id=CVE-2024-26775 Référence CVE CVE-2024-27078 https://www.cve.org/CVERecord?id=CVE-2024-27078 Référence CVE CVE-2024-35849 https://www.cve.org/CVERecord?id=CVE-2024-35849 Référence CVE CVE-2024-44939 https://www.cve.org/CVERecord?id=CVE-2024-44939 Référence CVE CVE-2024-49924 https://www.cve.org/CVERecord?id=CVE-2024-49924 Référence CVE CVE-2024-57883 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-1048Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2021-46936 Référence CVE CVE-2021-47163 https://www.cve.org/CVERecord?id=CVE-2021-47163 Référence CVE CVE-2021-47291 https://www.cve.org/CVERecord?id=CVE-2021-47291 Référence CVE CVE-2021-47378 https://www.cve.org/CVERecord?id=CVE-2021-47378 Référence CVE CVE-2021-47383 https://www.cve.org/CVERecord?id=CVE-2021-47383 Référence CVE CVE-2021-47402 https://www.cve.org/CVERecord?id=CVE-2021-47402 Référence CVE CVE-2021-47416 https://www.cve.org/CVERecord?id=CVE-2021-47416 Référence CVE CVE-2021-47517 https://www.cve.org/CVERecord?id=CVE-2021-47517 Référence CVE CVE-2021-47534 https://www.cve.org/CVERecord?id=CVE-2021-47534 Référence CVE CVE-2021-47589 https://www.cve.org/CVERecord?id=CVE-2021-47589 Référence CVE CVE-2021-47598 https://www.cve.org/CVERecord?id=CVE-2021-47598 Référence CVE CVE-2021-47612 https://www.cve.org/CVERecord?id=CVE-2021-47612 Référence CVE CVE-2022-3435 https://www.cve.org/CVERecord?id=CVE-2022-3435 Référence CVE CVE-2022-45934 https://www.cve.org/CVERecord?id=CVE-2022-45934 Référence CVE CVE-2022-48651 https://www.cve.org/CVERecord?id=CVE-2022-48651 Référence CVE CVE-2022-48662 https://www.cve.org/CVERecord?id=CVE-2022-48662 Référence CVE CVE-2022-48664 https://www.cve.org/CVERecord?id=CVE-2022-48664 Référence CVE CVE-2022-48788 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-1012Multiples vulnérabilités dans le noyau Linux de SUSE

De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire, un déni de service à distance et une atteinte à la confidentialité des données.

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0693Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2021-47578 Référence CVE CVE-2021-47580 https://www.cve.org/CVERecord?id=CVE-2021-47580 Référence CVE CVE-2021-47582 https://www.cve.org/CVERecord?id=CVE-2021-47582 Référence CVE CVE-2021-47583 https://www.cve.org/CVERecord?id=CVE-2021-47583 Référence CVE CVE-2021-47584 https://www.cve.org/CVERecord?id=CVE-2021-47584 Référence CVE CVE-2021-47585 https://www.cve.org/CVERecord?id=CVE-2021-47585 Référence CVE CVE-2021-47586 https://www.cve.org/CVERecord?id=CVE-2021-47586 Référence CVE CVE-2021-47587 https://www.cve.org/CVERecord?id=CVE-2021-47587 Référence CVE CVE-2021-47588 https://www.cve.org/CVERecord?id=CVE-2021-47588 Référence CVE CVE-2021-47589 https://www.cve.org/CVERecord?id=CVE-2021-47589 Référence CVE CVE-2021-47590 https://www.cve.org/CVERecord?id=CVE-2021-47590 Référence CVE CVE-2021-47591 https://www.cve.org/CVERecord?id=CVE-2021-47591 Référence CVE CVE-2021-47592 https://www.cve.org/CVERecord?id=CVE-2021-47592 Référence CVE CVE-2021-47593 https://www.cve.org/CVERecord?id=CVE-2021-47593 Référence CVE CVE-2021-47595 https://www.cve.org/CVERecord?id=CVE-2021-47595 Référence CVE CVE-2021-47596 https://www.cve.org/CVERecord?id=CVE-2021-47596 Référence CVE CVE-2021-47597 https://www.cve.org/CVERecord?id=CVE-2021-47597 Référence CVE CVE-2021-47598 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0610Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2021-47518 Référence CVE CVE-2021-47520 https://www.cve.org/CVERecord?id=CVE-2021-47520 Référence CVE CVE-2021-47544 https://www.cve.org/CVERecord?id=CVE-2021-47544 Référence CVE CVE-2021-47547 https://www.cve.org/CVERecord?id=CVE-2021-47547 Référence CVE CVE-2021-47555 https://www.cve.org/CVERecord?id=CVE-2021-47555 Référence CVE CVE-2021-47566 https://www.cve.org/CVERecord?id=CVE-2021-47566 Référence CVE CVE-2021-47571 https://www.cve.org/CVERecord?id=CVE-2021-47571 Référence CVE CVE-2021-47576 https://www.cve.org/CVERecord?id=CVE-2021-47576 Référence CVE CVE-2021-47587 https://www.cve.org/CVERecord?id=CVE-2021-47587 Référence CVE CVE-2021-47589 https://www.cve.org/CVERecord?id=CVE-2021-47589 Référence CVE CVE-2021-47600 https://www.cve.org/CVERecord?id=CVE-2021-47600 Référence CVE CVE-2021-47602 https://www.cve.org/CVERecord?id=CVE-2021-47602 Référence CVE CVE-2021-47603 https://www.cve.org/CVERecord?id=CVE-2021-47603 Référence CVE CVE-2021-47609 https://www.cve.org/CVERecord?id=CVE-2021-47609 Référence CVE CVE-2021-47617 https://www.cve.org/CVERecord?id=CVE-2021-47617 Référence CVE CVE-2022-0435 https://www.cve.org/CVERecord?id=CVE-2022-0435 Référence CVE CVE-2022-22942 https://www.cve.org/CVERecord?id=CVE-2022-22942 Référence CVE CVE-2022-48651 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0578Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2021-47577 Référence CVE CVE-2021-47578 https://www.cve.org/CVERecord?id=CVE-2021-47578 Référence CVE CVE-2021-47580 https://www.cve.org/CVERecord?id=CVE-2021-47580 Référence CVE CVE-2021-47582 https://www.cve.org/CVERecord?id=CVE-2021-47582 Référence CVE CVE-2021-47583 https://www.cve.org/CVERecord?id=CVE-2021-47583 Référence CVE CVE-2021-47584 https://www.cve.org/CVERecord?id=CVE-2021-47584 Référence CVE CVE-2021-47585 https://www.cve.org/CVERecord?id=CVE-2021-47585 Référence CVE CVE-2021-47586 https://www.cve.org/CVERecord?id=CVE-2021-47586 Référence CVE CVE-2021-47587 https://www.cve.org/CVERecord?id=CVE-2021-47587 Référence CVE CVE-2021-47589 https://www.cve.org/CVERecord?id=CVE-2021-47589 Référence CVE CVE-2021-47592 https://www.cve.org/CVERecord?id=CVE-2021-47592 Référence CVE CVE-2021-47595 https://www.cve.org/CVERecord?id=CVE-2021-47595 Référence CVE CVE-2021-47596 https://www.cve.org/CVERecord?id=CVE-2021-47596 Référence CVE CVE-2021-47597 https://www.cve.org/CVERecord?id=CVE-2021-47597 Référence CVE CVE-2021-47600 https://www.cve.org/CVERecord?id=CVE-2021-47600 Référence CVE CVE-2021-47601 https://www.cve.org/CVERecord?id=CVE-2021-47601 Référence CVE CVE-2021-47602 https://www.cve.org/CVERecord?id=CVE-2021-47602 Référence CVE CVE-2021-47603 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2021-021275Linux の Linux Kernel における二重解放に関する脆弱性

Linux の Linux Kernel には、二重解放に関する脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 2.6.30, 4.4.296 ≤ 4.4.*, 4.9.294 ≤ 4.9.*, 4.14.259 ≤ 4.14.*, 4.19.222 ≤ 4.19.*, 5.4.168 ≤ 5.4.*, 5.10.88 ≤ 5.10.*, 5.15.11 ≤ 5.15.*, 5.16 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 19 Jun 2024 · Last source change 11 May 2026, 13:57 UTC · CWE-415 · Double Free

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2021-34591
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2021-34591↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2021-47589 · cve.blacktree.nl