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

net:emac/emac-mac: Fix a use after free in emac_mac_tx_buf_send

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 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 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.79% 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 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.10.38-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.10.38-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.10.38-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.10.38-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-47013 · CSAF 2.0 · revision 60 · interimSUSE Product Security TeamCVE-2021-47013
122 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: net:emac/emac-mac: Fix a use after free in emac_mac_tx_buf_send In emac_mac_tx_buf_send, it calls emac_tx_fill_tpd(..,skb,..). If some error happens in emac_tx_fill_tpd(), the skb will be freed via dev_kfree_skb(skb) in error branch of emac_tx_fill_tpd(). But the freed skb is still used via skb->len by netdev_sent_queue(,skb->len). As i observed that emac_tx_fill_tpd() haven't modified the value of skb->len, thus my patch assigns skb->len to 'len' before the possible free and use 'len' instead of skb->len later.
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-33661

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 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: net:emac/emac-mac: Fix a use after free in emac_mac_tx_buf_send In emac_mac_tx_buf_send, it calls emac_tx_fill_tpd(..,skb,..). If some error happens in emac_tx_fill_tpd(), the skb will be freed via dev_kfree_skb(skb) in error branch of emac_tx_fill_tpd(). But the freed skb is still used via skb->len by netdev_sent_queue(,skb->len). As i observed that emac_tx_fill_tpd() haven't modified the value of skb->len, thus my patch assigns skb->len to 'len' before the possible free and use 'len' instead of skb->len later.

What

In the Linux kernel, the following vulnerability has been resolved: net:emac/emac-mac: Fix a use after free in emac_mac_tx_buf_send In emac_mac_tx_buf_send, it calls emac_tx_fill_tpd(..,skb,..). If some error happens in emac_tx_fill_tpd(), the skb will be freed via dev_kfree_skb(skb) in error branch of emac_tx_fill_tpd(). But the freed skb is still used via skb->len by netdev_sent_queue(,skb->len). As i observed that emac_tx_fill_tpd() haven't modified the value of skb->len, thus my patch assigns skb->len to 'len' before the possible free and use 'len' instead of skb->len later.

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 cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: net:emac/emac-mac: Fix a use after free in emac_mac_tx_buf_send In emac_mac_tx_buf_send, it calls emac_tx_fill_tpd(..,skb,..). If some error happens in emac_tx_fill_tpd(), the skb will be freed via dev_kfree_skb(skb) in error branch of emac_tx_fill_tpd(). But the freed skb is still used via skb->len by netdev_sent_queue(,skb->len). As i observed that emac_tx_fill_tpd() haven't modified the value of skb->len, thus my patch assigns skb->len to 'len' before the possible free and use 'len' instead of skb->len later.

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 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
a network path → Use After Free → cause the confidentiality, integrity or availability impact described by the vendor
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.
NetworkUnauthenticatedCWE-416
A

Official authority intelligence

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

BSI · German · WID-SEC-2024-0499Linux 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-20240306Security Bulletin 06 Mar 2024

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

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0741Multiples vulnérabilités dans Juniper Secure Analytics

d?id=CVE-2020-26555 Référence CVE CVE-2020-36777 https://www.cve.org/CVERecord?id=CVE-2020-36777 Référence CVE CVE-2021-33198 https://www.cve.org/CVERecord?id=CVE-2021-33198 Référence CVE CVE-2021-34558 https://www.cve.org/CVERecord?id=CVE-2021-34558 Référence CVE CVE-2021-40153 https://www.cve.org/CVERecord?id=CVE-2021-40153 Référence CVE CVE-2021-41072 https://www.cve.org/CVERecord?id=CVE-2021-41072 Référence CVE CVE-2021-46909 https://www.cve.org/CVERecord?id=CVE-2021-46909 Référence CVE CVE-2021-46934 https://www.cve.org/CVERecord?id=CVE-2021-46934 Référence CVE CVE-2021-46972 https://www.cve.org/CVERecord?id=CVE-2021-46972 Référence CVE CVE-2021-47013 https://www.cve.org/CVERecord?id=CVE-2021-47013 Référence CVE CVE-2021-47055 https://www.cve.org/CVERecord?id=CVE-2021-47055 Référence CVE CVE-2021-47069 https://www.cve.org/CVERecord?id=CVE-2021-47069 Référence CVE CVE-2021-47073 https://www.cve.org/CVERecord?id=CVE-2021-47073 Référence CVE CVE-2021-47118 https://www.cve.org/CVERecord?id=CVE-2021-47118 Référence CVE CVE-2021-47153 https://www.cve.org/CVERecord?id=CVE-2021-47153 Référence CVE CVE-2021-47171 https://www.cve.org/CVERecord?id=CVE-2021-47171 Référence CVE CVE-2021-47185 https://www.cve.org/CVERecord?id=CVE-2021-47185 Référence CVE CVE-2021-47236 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0646Multiples vulnérabilités dans les produits IBM

lletin de sécurité IBM 7162077 du 31 juillet 2024 https://www.ibm.com/support/pages/node/7162077 Référence CVE CVE-2018-25091 https://www.cve.org/CVERecord?id=CVE-2018-25091 Référence CVE CVE-2019-20372 https://www.cve.org/CVERecord?id=CVE-2019-20372 Référence CVE CVE-2019-25162 https://www.cve.org/CVERecord?id=CVE-2019-25162 Référence CVE CVE-2020-36777 https://www.cve.org/CVERecord?id=CVE-2020-36777 Référence CVE CVE-2021-33198 https://www.cve.org/CVERecord?id=CVE-2021-33198 Référence CVE CVE-2021-34558 https://www.cve.org/CVERecord?id=CVE-2021-34558 Référence CVE CVE-2021-46934 https://www.cve.org/CVERecord?id=CVE-2021-46934 Référence CVE CVE-2021-47013 https://www.cve.org/CVERecord?id=CVE-2021-47013 Référence CVE CVE-2021-47055 https://www.cve.org/CVERecord?id=CVE-2021-47055 Référence CVE CVE-2021-47118 https://www.cve.org/CVERecord?id=CVE-2021-47118 Référence CVE CVE-2021-47153 https://www.cve.org/CVERecord?id=CVE-2021-47153 Référence CVE CVE-2021-47171 https://www.cve.org/CVERecord?id=CVE-2021-47171 Référence CVE CVE-2021-47185 https://www.cve.org/CVERecord?id=CVE-2021-47185 Référence CVE CVE-2022-2879 https://www.cve.org/CVERecord?id=CVE-2022-2879 Référence CVE CVE-2022-2880 https://www.cve.org/CVERecord?id=CVE-2022-2880 Référence CVE CVE-2022-38096 https://www.cve.org/CVERecord?id=CVE-

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

écurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation). Documentation Bulletin de sécurité Red Hat RHSA-2024:3810 du 11 juin 2024 https://access.redhat.com/errata/RHSA-2024:3810 Bulletin de sécurité Red Hat RHSA-2024:3854 du 12 juin 2024 https://access.redhat.com/errata/RHSA-2024:3854 Bulletin de sécurité Red Hat RHSA-2024:3855 du 12 juin 2024 https://access.redhat.com/errata/RHSA-2024:3855 Bulletin de sécurité Red Hat RHSA-2024:3859 du 12 juin 2024 https://access.redhat.com/errata/RHSA-2024:3859 Bulletin de sécurité Red Hat RHSA-2024:3925 du 13 juin 2024 https://access.redhat.com/errata/RHSA-2024:3925 Référence CVE CVE-2021-47013 https://www.cve.org/CVERecord?id=CVE-2021-47013 Référence CVE CVE-2023-1118 https://www.cve.org/CVERecord?id=CVE-2023-1118 Référence CVE CVE-2023-1998 https://www.cve.org/CVERecord?id=CVE-2023-1998 Référence CVE CVE-2023-3128 https://www.cve.org/CVERecord?id=CVE-2023-3128 Référence CVE CVE-2023-4155 https://www.cve.org/CVERecord?id=CVE-2023-4155 Référence CVE CVE-2023-4822 https://www.cve.org/CVERecord?id=CVE-2023-4822 Référence CVE CVE-2023-49568 https://www.cve.org/CVERecord?id=CVE-2023-49568 Référence CVE CVE-2023-49569 https://www.cve.org/CVERecord?id=CVE-2023-49569 Référence CVE CVE-2023-5090 https://www.cve.org/CVERecord?id=CVE-2023-50

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

at RHSA-2024:3530 du 31 mai 2024 https://access.redhat.com/errata/RHSA-2024:3530 Bulletin de sécurité Red Hat RHSA-2024:3618 du 05 juin 2024 https://access.redhat.com/errata/RHSA-2024:3618 Bulletin de sécurité Red Hat RHSA-2024:3619 du 05 juin 2024 https://access.redhat.com/errata/RHSA-2024:3619 Bulletin de sécurité Red Hat RHSA-2024:3627 du 05 juin 2024 https://access.redhat.com/errata/RHSA-2024:3627 Référence CVE CVE-2019-25162 https://www.cve.org/CVERecord?id=CVE-2019-25162 Référence CVE CVE-2020-36777 https://www.cve.org/CVERecord?id=CVE-2020-36777 Référence CVE CVE-2021-46934 https://www.cve.org/CVERecord?id=CVE-2021-46934 Référence CVE CVE-2021-47013 https://www.cve.org/CVERecord?id=CVE-2021-47013 Référence CVE CVE-2021-47055 https://www.cve.org/CVERecord?id=CVE-2021-47055 Référence CVE CVE-2021-47118 https://www.cve.org/CVERecord?id=CVE-2021-47118 Référence CVE CVE-2021-47153 https://www.cve.org/CVERecord?id=CVE-2021-47153 Référence CVE CVE-2021-47171 https://www.cve.org/CVERecord?id=CVE-2021-47171 Référence CVE CVE-2021-47185 https://www.cve.org/CVERecord?id=CVE-2021-47185 Référence CVE CVE-2022-48627 https://www.cve.org/CVERecord?id=CVE-2022-48627 Référence CVE CVE-2022-48669 https://www.cve.org/CVERecord?id=CVE-2022-48669 Référence CVE CVE-2023-2166 https://www.cve.org/CVERecord?id=C

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

De multiples vulnérabilités ont été découvertes dans le noyau Linux de Red Hat. Elles permettent à un attaquant de provoquer une élévation de privilèges, une atteinte à la confidentialité des données, un déni de service.

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

d?id=CVE-2021-46990 Référence CVE CVE-2021-46991 https://www.cve.org/CVERecord?id=CVE-2021-46991 Référence CVE CVE-2021-46992 https://www.cve.org/CVERecord?id=CVE-2021-46992 Référence CVE CVE-2021-46998 https://www.cve.org/CVERecord?id=CVE-2021-46998 Référence CVE CVE-2021-47000 https://www.cve.org/CVERecord?id=CVE-2021-47000 Référence CVE CVE-2021-47001 https://www.cve.org/CVERecord?id=CVE-2021-47001 Référence CVE CVE-2021-47003 https://www.cve.org/CVERecord?id=CVE-2021-47003 Référence CVE CVE-2021-47006 https://www.cve.org/CVERecord?id=CVE-2021-47006 Référence CVE CVE-2021-47009 https://www.cve.org/CVERecord?id=CVE-2021-47009 Référence CVE CVE-2021-47013 https://www.cve.org/CVERecord?id=CVE-2021-47013 Référence CVE CVE-2021-47014 https://www.cve.org/CVERecord?id=CVE-2021-47014 Référence CVE CVE-2021-47015 https://www.cve.org/CVERecord?id=CVE-2021-47015 Référence CVE CVE-2021-47017 https://www.cve.org/CVERecord?id=CVE-2021-47017 Référence CVE CVE-2021-47020 https://www.cve.org/CVERecord?id=CVE-2021-47020 Référence CVE CVE-2021-47026 https://www.cve.org/CVERecord?id=CVE-2021-47026 Référence CVE CVE-2021-47034 https://www.cve.org/CVERecord?id=CVE-2021-47034 Référence CVE CVE-2021-47035 https://www.cve.org/CVERecord?id=CVE-2021-47035 Référence CVE CVE-2021-47038 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2021-46953 Référence CVE CVE-2021-46964 https://www.cve.org/CVERecord?id=CVE-2021-46964 Référence CVE CVE-2021-46966 https://www.cve.org/CVERecord?id=CVE-2021-46966 Référence CVE CVE-2021-46974 https://www.cve.org/CVERecord?id=CVE-2021-46974 Référence CVE CVE-2021-46989 https://www.cve.org/CVERecord?id=CVE-2021-46989 Référence CVE CVE-2021-46991 https://www.cve.org/CVERecord?id=CVE-2021-46991 Référence CVE CVE-2021-46992 https://www.cve.org/CVERecord?id=CVE-2021-46992 Référence CVE CVE-2021-47005 https://www.cve.org/CVERecord?id=CVE-2021-47005 Référence CVE CVE-2021-47012 https://www.cve.org/CVERecord?id=CVE-2021-47012 Référence CVE CVE-2021-47013 https://www.cve.org/CVERecord?id=CVE-2021-47013 Référence CVE CVE-2021-47054 https://www.cve.org/CVERecord?id=CVE-2021-47054 Référence CVE CVE-2021-47060 https://www.cve.org/CVERecord?id=CVE-2021-47060 Référence CVE CVE-2021-47061 https://www.cve.org/CVERecord?id=CVE-2021-47061 Référence CVE CVE-2021-47069 https://www.cve.org/CVERecord?id=CVE-2021-47069 Référence CVE CVE-2021-47076 https://www.cve.org/CVERecord?id=CVE-2021-47076 Référence CVE CVE-2021-47077 https://www.cve.org/CVERecord?id=CVE-2021-47077 Référence CVE CVE-2021-47078 https://www.cve.org/CVERecord?id=CVE-2021-47078 Référence CVE CVE-2021-47083 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2021-46934 Référence CVE CVE-2021-46953 https://www.cve.org/CVERecord?id=CVE-2021-46953 Référence CVE CVE-2021-46964 https://www.cve.org/CVERecord?id=CVE-2021-46964 Référence CVE CVE-2021-46966 https://www.cve.org/CVERecord?id=CVE-2021-46966 Référence CVE CVE-2021-46968 https://www.cve.org/CVERecord?id=CVE-2021-46968 Référence CVE CVE-2021-46974 https://www.cve.org/CVERecord?id=CVE-2021-46974 Référence CVE CVE-2021-46989 https://www.cve.org/CVERecord?id=CVE-2021-46989 Référence CVE CVE-2021-47005 https://www.cve.org/CVERecord?id=CVE-2021-47005 Référence CVE CVE-2021-47012 https://www.cve.org/CVERecord?id=CVE-2021-47012 Référence CVE CVE-2021-47013 https://www.cve.org/CVERecord?id=CVE-2021-47013 Référence CVE CVE-2021-47054 https://www.cve.org/CVERecord?id=CVE-2021-47054 Référence CVE CVE-2021-47060 https://www.cve.org/CVERecord?id=CVE-2021-47060 Référence CVE CVE-2021-47061 https://www.cve.org/CVERecord?id=CVE-2021-47061 Référence CVE CVE-2021-47069 https://www.cve.org/CVERecord?id=CVE-2021-47069 Référence CVE CVE-2021-47076 https://www.cve.org/CVERecord?id=CVE-2021-47076 Référence CVE CVE-2021-47078 https://www.cve.org/CVERecord?id=CVE-2021-47078 Référence CVE CVE-2021-47083 https://www.cve.org/CVERecord?id=CVE-2021-47083 Référence CVE CVE-2022-20154 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2021-021345Linux の 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.9, 4.9.269 ≤ 4.9.*, 4.14.233 ≤ 4.14.*, 4.19.191 ≤ 4.19.*, 5.4.119 ≤ 5.4.*, 5.10.37 ≤ 5.10.*, 5.11.21 ≤ 5.11.*, 5.12.4 ≤ 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 28 Feb 2024 · Last source change 5 Aug 2026, 08:45 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-33661
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-33661↗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-47013 · cve.blacktree.nl