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

tipc: skb_linearize the head skb when reassembling msgs

Linux · Linux

9.8CriticalCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 67 structured product or package states 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 severityCriticalOperational priority:Critical, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.74% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • 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: Within 3 daysRemediation target: Within 90 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 67 structured product or package states 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.14.6-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.14.6-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.14.6-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.14.6-1Debian Security Tracker ↗Source updated 5 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 5 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-47162 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: tipc: skb_linearize the head skb when reassembling msgs
66 known affected

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

  • migration-toolkit-virtualization/mtv-deep-inspection-rhel9 as a component of Migration Toolkit for Virtualization
  • migration-toolkit-virtualization/mtv-virt-v2v-rhel9 as a component of Migration Toolkit for Virtualization
  • rhcertification/redhat-certification-baremetal as a component of Red Hat Certification Program for Red Hat Enterprise Linux 9
  • rhcertification/redhat-certification-system-ai-10 as a component of Red Hat Certification Program for Red Hat Enterprise Linux 9
  • rhcertification/redhat-certification-system-ai-9 as a component of Red Hat Certification Program for Red Hat Enterprise Linux 9
  • rhel10-eus/rhel-10.0-bootc as a component of Red Hat Enterprise Linux 10
  • rhel10-eus/rhel-10.2-bootc as a component of Red Hat Enterprise Linux 10
  • rhel10/rhel-bootc as a component of Red Hat Enterprise Linux 10
  • bpftool as a component of Red Hat Enterprise Linux 8
  • kernel as a component of Red Hat Enterprise Linux 8
  • kernel-abi-stablelists as a component of Red Hat Enterprise Linux 8
  • kernel-abi-whitelists as a component of Red Hat Enterprise Linux 8
Summary
This linux kernel vulnerability occurs in the TIPC (Transparent Inter-Process Communication) networking subsystem, specifically concerning how socket buffer (SKB) fragments are handled when reassembling messages. The issue arises when the network code attempts to append a new fragment to a head SKB's fragment list (frag_list). If this target list already contains socket buffers cloned from elsewhere—such as those created by pskb_copy() where reference counts are actively shared—appending new fragments directly to it can corrupt the list, leading to improper memory management and subsequent kernel crashes. Patched kernel versions resolve the vulnerability by explicitly linearizing the head socket buffer (skb_linearize) during message reassembly, ensuring that new fragments are processed safely without corrupting shared memory structures.
Remediation
Fix deferred
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-33810

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

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 67 structured product or package states 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: tipc: skb_linearize the head skb when reassembling msgs It's not a good idea to append the frag skb to a skb's frag_list if the frag_list already has skbs from elsewhere, such as this skb was created by pskb_copy() where the frag_list was cloned (all the skbs in it were skb_get'ed) and shared by multiple skbs. However, the new appended frag skb should have been only seen by the current skb. Otherwise, it will cause use after free crashes as this appended frag skb are seen by multiple skbs but it only got skb_get called once. The same thing happens with a skb updated by pskb_may_pull() with a skb_cloned skb. Li Shuang has reported quite a few crashes caused by this when doing testing over macvlan devices: [] kernel BUG at net/core/skbuff.c:1970! [] Call Trace: [] skb_clone+0x4d/0xb0 [] macvlan_broadcast+0xd8/0x160 [macvlan] [] macvlan_process_broadcast+0x148/0x150 [macvlan] [] process_one_work+0x1a7/0x360 [] worker_thread+0x30/0x390 [] kernel BUG at mm/usercopy.c:102! [] Call Trace: [] __check_heap_object+0xd3/0x100 [] __check_object_size+0xff/0x16b [] simple_copy_to_iter+0x1c/0x30 [] __skb_datagram_iter+0x7d/0x310 [] __skb_datagram_iter+0x2a5/0x310 [] skb_copy_datagram_iter+0x3b/0x90 [] tipc_recvmsg+0x14a/0x3a0 [tipc] [] ____sys_recvmsg+0x91/0x150 [] ___sys_recvmsg+0x7b/0xc0 [] kernel BUG at mm/slub.c:305! [] Call Trace: [] <IRQ> [] kmem_cache_free+0x3ff/0x400 [] __netif_receive_skb_core+0x12c/0xc40 [] ? kmem_cache_alloc+0x12e/0x270 [] netif_receive_skb_internal+0x3d/0xb0 [] ? get_rx_page_info+0x8e/0xa0 [be2net] [] be_poll+0x6ef/0xd00 [be2net] [] ? irq_exit+0x4f/0x100 [] net_rx_action+0x149/0x3b0 ... This patch is to fix it by linearizing the head skb if it has frag_list set in tipc_buf_append(). Note that we choose to do this before calling skb_unshare(), as __skb_linearize() will avoid skb_copy(). Also, we can not just drop the frag_list either as the early time.

What

In the Linux kernel, the following vulnerability has been resolved: tipc: skb_linearize the head skb when reassembling msgs It's not a good idea to append the frag skb to a skb's frag_list if the frag_list already has skbs from elsewhere, such as this skb was created by pskb_copy() where the frag_list was cloned (all the skbs in it were skb_get'ed) and shared by multiple skbs. However, the new appended frag skb should have been only seen by the current skb. Otherwise, it will cause use after free crashes as this appended frag skb are seen by multiple skbs but it only got skb_get called once. The same thing happens with a skb updated by pskb_may_pull() with a skb_cloned skb. Li Shuang has reported quite a few crashes caused by this when doing testing over macvlan devices: [] kernel BUG at net/core/skbuff.c:1970! [] Call Trace: [] skb_clone+0x4d/0xb0 [] macvlan_broadcast+0xd8/0x160 [macvlan] [] macvlan_process_broadcast+0x148/0x150 [macvlan] [] process_one_work+0x1a7/0x360 [] worker_thread+0x30/0x390 [] kernel BUG at mm/usercopy.c:102! [] Call Trace: [] __check_heap_object+0xd3/0x100 [] __check_object_size+0xff/0x16b [] simple_copy_to_iter+0x1c/0x30 [] __skb_datagram_iter+0x7d/0x310 [] __skb_datagram_iter+0x2a5/0x310 [] skb_copy_datagram_iter+0x3b/0x90 [] tipc_recvmsg+0x14a/0x3a0 [tipc] [] ____sys_recvmsg+0x91/0x150 [] ___sys_recvmsg+0x7b/0xc0 [] kernel BUG at mm/slub.c:305! [] Call Trace: [] <IRQ> [] kmem_cache_free+0x3ff/0x400 [] __netif_receive_skb_core+0x12c/0xc40 [] ? kmem_cache_alloc+0x12e/0x270 [] netif_receive_skb_internal+0x3d/0xb0 [] ? get_rx_page_info+0x8e/0xa0 [be2net] [] be_poll+0x6ef/0xd00 [be2net] [] ? irq_exit+0x4f/0x100 [] net_rx_action+0x149/0x3b0 ... This patch is to fix it by linearizing the head skb if it has frag_list set in tipc_buf_append(). Note that we choose to do this before calling skb_unshare(), as __skb_linearize() will avoid skb_copy(). Also, we can not just drop the frag_list either as the early time.

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

What

In the Linux kernel, the following vulnerability has been resolved: tipc: skb_linearize the head skb when reassembling msgs It's not a good idea to append the frag skb to a skb's frag_list if the frag_list already has skbs from elsewhere, such as this skb was created by pskb_copy() where the frag_list was cloned (all the skbs in it were skb_get'ed) and shared by multiple skbs. However, the new appended frag skb should have been only seen by the current skb. Otherwise, it will cause use after free crashes as this appended frag skb are seen by multiple skbs but it only got skb_get called once. The same thing happens with a skb updated by pskb_may_pull() with a skb_cloned skb. Li Shuang has reported quite a few crashes caused by this when doing testing over macvlan devices: [] kernel BUG at net/core/skbuff.c:1970! [] Call Trace: [] skb_clone+0x4d/0xb0 [] macvlan_broadcast+0xd8/0x160 [macvlan] [] macvlan_process_broadcast+0x148/0x150 [macvlan] [] process_one_work+0x1a7/0x360 [] worker_thread+0x30/0x390 [] kernel BUG at mm/usercopy.c:102! [] Call Trace: [] __check_heap_object+0xd3/0x100 [] __check_object_size+0xff/0x16b [] simple_copy_to_iter+0x1c/0x30 [] __skb_datagram_iter+0x7d/0x310 [] __skb_datagram_iter+0x2a5/0x310 [] skb_copy_datagram_iter+0x3b/0x90 [] tipc_recvmsg+0x14a/0x3a0 [tipc] [] ____sys_recvmsg+0x91/0x150 [] ___sys_recvmsg+0x7b/0xc0 [] kernel BUG at mm/slub.c:305! [] Call Trace: [] <IRQ> [] kmem_cache_free+0x3ff/0x400 [] __netif_receive_skb_core+0x12c/0xc40 [] ? kmem_cache_alloc+0x12e/0x270 [] netif_receive_skb_internal+0x3d/0xb0 [] ? get_rx_page_info+0x8e/0xa0 [be2net] [] be_poll+0x6ef/0xd00 [be2net] [] ? irq_exit+0x4f/0x100 [] net_rx_action+0x149/0x3b0 ... This patch is to fix it by linearizing the head skb if it has frag_list set in tipc_buf_append(). Note that we choose to do this before calling skb_unshare(), as __skb_linearize() will avoid skb_copy(). Also, we can not just drop the frag_list either as the early time.

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

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
a network path → Use After Free → disrupt the affected service
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
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-416 ↗

CWE-416: Use After Free. The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/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.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing 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
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedDenial of serviceCWE-416
A

Official authority intelligence

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

BSI · German · WID-SEC-2025-0225Dell PowerProtect Data Domain: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Dell PowerProtect Data Domain ausnutzen, um erhöhte Rechte zu erlangen, einen Denial-of-Service-Zustand herbeizuführen und einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2024-0699Linux-Kernel: Mehrere Schwachstellen ermöglichen Denial of Service und unspezifische Angriffe

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen und einen nicht spezifizierten Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20240327Security Bulletin 27 Mar 2024

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

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

mettent à un attaquant de provoquer une exécution de code arbitraire, un déni de service à distance et une atteinte à la confidentialité des données. Solutions Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation). Documentation Bulletin de sécurité SUSE SUSE-SU-2025:0034-1 du 08 janvier 2025 https://www.suse.com/support/update/announcement/2025/suse-su-20250034-1 Bulletin de sécurité SUSE SUSE-SU-2025:0035-1 du 08 janvier 2025 https://www.suse.com/support/update/announcement/2025/suse-su-20250035-1 Référence CVE CVE-2021-46936 https://www.cve.org/CVERecord?id=CVE-2021-46936 Référence CVE CVE-2021-47162 https://www.cve.org/CVERecord?id=CVE-2021-47162 Référence CVE CVE-2021-47163 https://www.cve.org/CVERecord?id=CVE-2021-47163 Référence CVE CVE-2021-47416 https://www.cve.org/CVERecord?id=CVE-2021-47416 Référence CVE CVE-2021-47612 https://www.cve.org/CVERecord?id=CVE-2021-47612 Référence CVE CVE-2022-48788 https://www.cve.org/CVERecord?id=CVE-2022-48788 Référence CVE CVE-2022-48789 https://www.cve.org/CVERecord?id=CVE-2022-48789 Référence CVE CVE-2022-48790 https://www.cve.org/CVERecord?id=CVE-2022-48790 Référence CVE CVE-2022-48809 https://www.cve.org/CVERecord?id=CVE-2022-48809 Référence CVE CVE-2022-48853 https://www.cve.org/CVERecord?id=

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

e 2024 https://www.suse.com/support/update/announcement/2024/suse-su-20244364-1 Bulletin de sécurité SUSE SUSE-SU-2024:4367-1 du 17 décembre 2024 https://www.suse.com/support/update/announcement/2024/suse-su-20244367-1 Bulletin de sécurité SUSE SUSE-SU-2024:4376-1 du 18 décembre 2024 https://www.suse.com/support/update/announcement/2024/suse-su-20244376-1 Bulletin de sécurité SUSE SUSE-SU-2024:4387-1 du 19 décembre 2024 https://www.suse.com/support/update/announcement/2024/suse-su-20244387-1 Bulletin de sécurité SUSE SUSE-SU-2024:4388-1 du 19 décembre 2024 https://www.suse.com/support/update/announcement/2024/suse-su-20244388-1 Référence CVE CVE-2021-47162 https://www.cve.org/CVERecord?id=CVE-2021-47162 Référence CVE CVE-2021-47416 https://www.cve.org/CVERecord?id=CVE-2021-47416 Référence CVE CVE-2021-47534 https://www.cve.org/CVERecord?id=CVE-2021-47534 Référence CVE CVE-2021-47594 https://www.cve.org/CVERecord?id=CVE-2021-47594 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-48664 https://www.cve.org/CVERecord?id=CVE-2022-48664 Référence CVE CVE-2022-48674 https://www.cve.org/CVERecord?id=CVE-2022-48674 Référence CVE CVE-2022-48853 https://www.cve.org/CVERecord?id=CV

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

ord?id=CVE-2021-39698 Référence CVE CVE-2021-4148 https://www.cve.org/CVERecord?id=CVE-2021-4148 Référence CVE CVE-2021-43056 https://www.cve.org/CVERecord?id=CVE-2021-43056 Référence CVE CVE-2021-46933 https://www.cve.org/CVERecord?id=CVE-2021-46933 Référence CVE CVE-2021-46955 https://www.cve.org/CVERecord?id=CVE-2021-46955 Référence CVE CVE-2021-47074 https://www.cve.org/CVERecord?id=CVE-2021-47074 Référence CVE CVE-2021-47104 https://www.cve.org/CVERecord?id=CVE-2021-47104 Référence CVE CVE-2021-47113 https://www.cve.org/CVERecord?id=CVE-2021-47113 Référence CVE CVE-2021-47131 https://www.cve.org/CVERecord?id=CVE-2021-47131 Référence CVE CVE-2021-47162 https://www.cve.org/CVERecord?id=CVE-2021-47162 Référence CVE CVE-2021-47171 https://www.cve.org/CVERecord?id=CVE-2021-47171 Référence CVE CVE-2021-47188 https://www.cve.org/CVERecord?id=CVE-2021-47188 Référence CVE CVE-2021-47192 https://www.cve.org/CVERecord?id=CVE-2021-47192 Référence CVE CVE-2021-47200 https://www.cve.org/CVERecord?id=CVE-2021-47200 Référence CVE CVE-2021-47206 https://www.cve.org/CVERecord?id=CVE-2021-47206 Référence CVE CVE-2021-47220 https://www.cve.org/CVERecord?id=CVE-2021-47220 Référence CVE CVE-2021-47227 https://www.cve.org/CVERecord?id=CVE-2021-47227 Référence CVE CVE-2021-47228 https://www.cve.org/CVERecord?id=

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

rd?id=CVE-2021-4148 Référence CVE CVE-2021-42327 https://www.cve.org/CVERecord?id=CVE-2021-42327 Référence CVE CVE-2021-43056 https://www.cve.org/CVERecord?id=CVE-2021-43056 Référence CVE CVE-2021-46933 https://www.cve.org/CVERecord?id=CVE-2021-46933 Référence CVE CVE-2021-46955 https://www.cve.org/CVERecord?id=CVE-2021-46955 Référence CVE CVE-2021-47074 https://www.cve.org/CVERecord?id=CVE-2021-47074 Référence CVE CVE-2021-47104 https://www.cve.org/CVERecord?id=CVE-2021-47104 Référence CVE CVE-2021-47113 https://www.cve.org/CVERecord?id=CVE-2021-47113 Référence CVE CVE-2021-47131 https://www.cve.org/CVERecord?id=CVE-2021-47131 Référence CVE CVE-2021-47162 https://www.cve.org/CVERecord?id=CVE-2021-47162 Référence CVE CVE-2021-47171 https://www.cve.org/CVERecord?id=CVE-2021-47171 Référence CVE CVE-2021-47188 https://www.cve.org/CVERecord?id=CVE-2021-47188 Référence CVE CVE-2021-47192 https://www.cve.org/CVERecord?id=CVE-2021-47192 Référence CVE CVE-2021-47200 https://www.cve.org/CVERecord?id=CVE-2021-47200 Référence CVE CVE-2021-47206 https://www.cve.org/CVERecord?id=CVE-2021-47206 Référence CVE CVE-2021-47220 https://www.cve.org/CVERecord?id=CVE-2021-47220 Référence CVE CVE-2021-47227 https://www.cve.org/CVERecord?id=CVE-2021-47227 Référence CVE CVE-2021-47228 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2021-47141 Référence CVE CVE-2021-47142 https://www.cve.org/CVERecord?id=CVE-2021-47142 Référence CVE CVE-2021-47143 https://www.cve.org/CVERecord?id=CVE-2021-47143 Référence CVE CVE-2021-47146 https://www.cve.org/CVERecord?id=CVE-2021-47146 Référence CVE CVE-2021-47149 https://www.cve.org/CVERecord?id=CVE-2021-47149 Référence CVE CVE-2021-47150 https://www.cve.org/CVERecord?id=CVE-2021-47150 Référence CVE CVE-2021-47153 https://www.cve.org/CVERecord?id=CVE-2021-47153 Référence CVE CVE-2021-47159 https://www.cve.org/CVERecord?id=CVE-2021-47159 Référence CVE CVE-2021-47161 https://www.cve.org/CVERecord?id=CVE-2021-47161 Référence CVE CVE-2021-47162 https://www.cve.org/CVERecord?id=CVE-2021-47162 Référence CVE CVE-2021-47165 https://www.cve.org/CVERecord?id=CVE-2021-47165 Référence CVE CVE-2021-47166 https://www.cve.org/CVERecord?id=CVE-2021-47166 Référence CVE CVE-2021-47167 https://www.cve.org/CVERecord?id=CVE-2021-47167 Référence CVE CVE-2021-47168 https://www.cve.org/CVERecord?id=CVE-2021-47168 Référence CVE CVE-2021-47169 https://www.cve.org/CVERecord?id=CVE-2021-47169 Référence CVE CVE-2021-47171 https://www.cve.org/CVERecord?id=CVE-2021-47171 Référence CVE CVE-2021-47173 https://www.cve.org/CVERecord?id=CVE-2021-47173 Référence CVE CVE-2021-47177 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2021-47141 Référence CVE CVE-2021-47142 https://www.cve.org/CVERecord?id=CVE-2021-47142 Référence CVE CVE-2021-47143 https://www.cve.org/CVERecord?id=CVE-2021-47143 Référence CVE CVE-2021-47146 https://www.cve.org/CVERecord?id=CVE-2021-47146 Référence CVE CVE-2021-47149 https://www.cve.org/CVERecord?id=CVE-2021-47149 Référence CVE CVE-2021-47150 https://www.cve.org/CVERecord?id=CVE-2021-47150 Référence CVE CVE-2021-47153 https://www.cve.org/CVERecord?id=CVE-2021-47153 Référence CVE CVE-2021-47159 https://www.cve.org/CVERecord?id=CVE-2021-47159 Référence CVE CVE-2021-47161 https://www.cve.org/CVERecord?id=CVE-2021-47161 Référence CVE CVE-2021-47162 https://www.cve.org/CVERecord?id=CVE-2021-47162 Référence CVE CVE-2021-47165 https://www.cve.org/CVERecord?id=CVE-2021-47165 Référence CVE CVE-2021-47166 https://www.cve.org/CVERecord?id=CVE-2021-47166 Référence CVE CVE-2021-47167 https://www.cve.org/CVERecord?id=CVE-2021-47167 Référence CVE CVE-2021-47168 https://www.cve.org/CVERecord?id=CVE-2021-47168 Référence CVE CVE-2021-47169 https://www.cve.org/CVERecord?id=CVE-2021-47169 Référence CVE CVE-2021-47171 https://www.cve.org/CVERecord?id=CVE-2021-47171 Référence CVE CVE-2021-47173 https://www.cve.org/CVERecord?id=CVE-2021-47173 Référence CVE CVE-2021-47177 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2021-47141 Référence CVE CVE-2021-47142 https://www.cve.org/CVERecord?id=CVE-2021-47142 Référence CVE CVE-2021-47143 https://www.cve.org/CVERecord?id=CVE-2021-47143 Référence CVE CVE-2021-47146 https://www.cve.org/CVERecord?id=CVE-2021-47146 Référence CVE CVE-2021-47149 https://www.cve.org/CVERecord?id=CVE-2021-47149 Référence CVE CVE-2021-47150 https://www.cve.org/CVERecord?id=CVE-2021-47150 Référence CVE CVE-2021-47153 https://www.cve.org/CVERecord?id=CVE-2021-47153 Référence CVE CVE-2021-47159 https://www.cve.org/CVERecord?id=CVE-2021-47159 Référence CVE CVE-2021-47161 https://www.cve.org/CVERecord?id=CVE-2021-47161 Référence CVE CVE-2021-47162 https://www.cve.org/CVERecord?id=CVE-2021-47162 Référence CVE CVE-2021-47165 https://www.cve.org/CVERecord?id=CVE-2021-47165 Référence CVE CVE-2021-47166 https://www.cve.org/CVERecord?id=CVE-2021-47166 Référence CVE CVE-2021-47167 https://www.cve.org/CVERecord?id=CVE-2021-47167 Référence CVE CVE-2021-47168 https://www.cve.org/CVERecord?id=CVE-2021-47168 Référence CVE CVE-2021-47169 https://www.cve.org/CVERecord?id=CVE-2021-47169 Référence CVE CVE-2021-47171 https://www.cve.org/CVERecord?id=CVE-2021-47171 Référence CVE CVE-2021-47173 https://www.cve.org/CVERecord?id=CVE-2021-47173 Référence CVE CVE-2021-47177 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2021-021669Linux の 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: < 4.3, 4.4.271 ≤ 4.4.*, 4.9.271 ≤ 4.9.*, 4.14.235 ≤ 4.14.*, 4.19.193 ≤ 4.19.*, 5.4.124 ≤ 5.4.*, 5.10.42 ≤ 5.10.*, 5.12.9 ≤ 5.12.*, 5.13 ≤ *
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. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 25 Mar 2024 · Last source change 5 Aug 2026, 08:46 UTC · CWE-416 · Use After Free

CVE recordCVE.org · 5.2
CVSS sourceCNA
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-33810
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
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 ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    bpftool as a component of Red Hat Enterprise Linux 8; kernel as a component of Red Hat Enterprise Linux 8; kernel-abi-stablelists as a component of Red Hat Enterprise Linux 8; kernel-abi-whitelists as a component of Red Hat Enterprise Linux 8; kernel-core as a component of Red Hat Enterprise Linux 8; kernel-cross-headers as a component of Red Hat Enterprise Linux 8; kernel-debug as a component of Red Hat Enterprise Linux 8; kernel-debug-core as a component of Red Hat Enterprise Linux 8; kernel-debug-devel as a component of Red Hat Enterprise Linux 8; kernel-debug-modules as a component of Red Hat Enterprise Linux 8; kernel-debug-modules-extra as a component of Red Hat Enterprise Linux 8; kernel-debug-modules-internal as a component of Red Hat Enterprise Linux 8; kernel-devel as a component of Red Hat Enterprise Linux 8; kernel-doc as a component of Red Hat Enterprise Linux 8; kernel-headers as a component of Red Hat Enterprise Linux 8; kernel-ipaclones-internal as a component of Red Hat Enterprise Linux 8; kernel-modules as a component of Red Hat Enterprise Linux 8; kernel-modules-extra as a component of Red Hat Enterprise Linux 8; kernel-modules-internal as a component of Red Hat Enterprise Linux 8; kernel-rt as a component of Red Hat Enterprise Linux 8; kernel-rt-core as a component of Red Hat Enterprise Linux 8; kernel-rt-debug as a component of Red Hat Enterprise Linux 8; kernel-rt-debug-core as a component of Red Hat Enterprise Linux 8; kernel-rt-debug-devel as a component of Red Hat Enterprise Linux 8; kernel-rt-debug-kvm as a component of Red Hat Enterprise Linux 8; kernel-rt-debug-modules as a component of Red Hat Enterprise Linux 8; kernel-rt-debug-modules-extra as a component of Red Hat Enterprise Linux 8; kernel-rt-debug-modules-internal as a component of Red Hat Enterprise Linux 8; kernel-rt-devel as a component of Red Hat Enterprise Linux 8; kernel-rt-kvm as a component of Red Hat Enterprise Linux 8; and 18 more
    After
    migration-toolkit-virtualization/mtv-deep-inspection-rhel9 as a component of Migration Toolkit for Virtualization; migration-toolkit-virtualization/mtv-virt-v2v-rhel9 as a component of Migration Toolkit for Virtualization; rhcertification/redhat-certification-baremetal as a component of Red Hat Certification Program for Red Hat Enterprise Linux 9; rhcertification/redhat-certification-system-ai-10 as a component of Red Hat Certification Program for Red Hat Enterprise Linux 9; rhcertification/redhat-certification-system-ai-9 as a component of Red Hat Certification Program for Red Hat Enterprise Linux 9; rhel10-eus/rhel-10.0-bootc as a component of Red Hat Enterprise Linux 10; rhel10-eus/rhel-10.2-bootc as a component of Red Hat Enterprise Linux 10; rhel10/rhel-bootc as a component of Red Hat Enterprise Linux 10; bpftool as a component of Red Hat Enterprise Linux 8; kernel as a component of Red Hat Enterprise Linux 8; kernel-abi-stablelists as a component of Red Hat Enterprise Linux 8; kernel-abi-whitelists as a component of Red Hat Enterprise Linux 8; kernel-core as a component of Red Hat Enterprise Linux 8; kernel-cross-headers as a component of Red Hat Enterprise Linux 8; kernel-debug as a component of Red Hat Enterprise Linux 8; kernel-debug-core as a component of Red Hat Enterprise Linux 8; kernel-debug-devel as a component of Red Hat Enterprise Linux 8; kernel-debug-modules as a component of Red Hat Enterprise Linux 8; kernel-debug-modules-extra as a component of Red Hat Enterprise Linux 8; kernel-debug-modules-internal as a component of Red Hat Enterprise Linux 8; kernel-devel as a component of Red Hat Enterprise Linux 8; kernel-doc as a component of Red Hat Enterprise Linux 8; kernel-headers as a component of Red Hat Enterprise Linux 8; kernel-ipaclones-internal as a component of Red Hat Enterprise Linux 8; kernel-modules as a component of Red Hat Enterprise Linux 8; kernel-modules-extra as a component of Red Hat Enterprise Linux 8; kernel-modules-internal as a component of Red Hat Enterprise Linux 8; kernel-rt as a component of Red Hat Enterprise Linux 8; kernel-rt-core as a component of Red Hat Enterprise Linux 8; kernel-rt-debug as a component of Red Hat Enterprise Linux 8; and 36 more
    Red Hat Product Security ↗
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-33810↗Vendor CSAF · Red Hat Product Security↗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-47162 · cve.blacktree.nl