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

net/tls: Fix use-after-free after the TLS device goes down and up

Linux · Linux

8.1HighCVSS 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:High, 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.75% 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 30 daysRemediation target: Within 180 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.46-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.10.46-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.10.46-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.10.46-1Debian Security Tracker ↗Source updated 6 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-47131 · CSAF 2.0 · revision 57 · interimSUSE Product Security TeamCVE-2021-47131
64 known affected

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

  • kernel-source-azure as component of SUSE Enterprise Storage 7.1
  • kernel-source-azure as component of SUSE Enterprise Storage 7
  • 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
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-source-azure as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-source-azure as component of SUSE Linux Enterprise High Performance Computing 15 SP3
Summary
In the Linux kernel, the following vulnerability has been resolved: net/tls: Fix use-after-free after the TLS device goes down and up When a netdev with active TLS offload goes down, tls_device_down is called to stop the offload and tear down the TLS context. However, the socket stays alive, and it still points to the TLS context, which is now deallocated. If a netdev goes up, while the connection is still active, and the data flow resumes after a number of TCP retransmissions, it will lead to a use-after-free of the TLS context. This commit addresses this bug by keeping the context alive until its normal destruction, and implements the necessary fallbacks, so that the connection can resume in software (non-offloaded) kTLS mode. On the TX side tls_sw_fallback is used to encrypt all packets. The RX side already has all the necessary fallbacks, because receiving non-decrypted packets is supported. The thing needed on the RX side is to block resync requests, which are normally produced after receiving non-decrypted packets. The necessary synchronization is implemented for a graceful teardown: first the fallbacks are deployed, then the driver resources are released (it used to be possible to have a tls_dev_resync after tls_dev_del). A new flag called TLS_RX_DEV_DEGRADED is added to indicate the fallback mode. It's used to skip the RX resync logic completely, as it becomes useless, and some objects may be released (for example, resync_async, which is allocated and freed by the driver).
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-33779

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: net/tls: Fix use-after-free after the TLS device goes down and up When a netdev with active TLS offload goes down, tls_device_down is called to stop the offload and tear down the TLS context. However, the socket stays alive, and it still points to the TLS context, which is now deallocated. If a netdev goes up, while the connection is still active, and the data flow resumes after a number of TCP retransmissions, it will lead to a use-after-free of the TLS context. This commit addresses this bug by keeping the context alive until its normal destruction, and implements the necessary fallbacks, so that the connection can resume in software (non-offloaded) kTLS mode. On the TX side tls_sw_fallback is used to encrypt all packets. The RX side already has all the necessary fallbacks, because receiving non-decrypted packets is supported. The thing needed on the RX side is to block resync requests, which are normally produced after receiving non-decrypted packets. The necessary synchronization is implemented for a graceful teardown: first the fallbacks are deployed, then the driver resources are released (it used to be possible to have a tls_dev_resync after tls_dev_del). A new flag called TLS_RX_DEV_DEGRADED is added to indicate the fallback mode. It's used to skip the RX resync logic completely, as it becomes useless, and some objects may be released (for example, resync_async, which is allocated and freed by the driver).

What

In the Linux kernel, the following vulnerability has been resolved: net/tls: Fix use-after-free after the TLS device goes down and up When a netdev with active TLS offload goes down, tls_device_down is called to stop the offload and tear down the TLS context. However, the socket stays alive, and it still points to the TLS context, which is now deallocated. If a netdev goes up, while the connection is still active, and the data flow resumes after a number of TCP retransmissions, it will lead to a use-after-free of the TLS context. This commit addresses this bug by keeping the context alive until its normal destruction, and implements the necessary fallbacks, so that the connection can resume in software (non-offloaded) kTLS mode. On the TX side tls_sw_fallback is used to encrypt all packets. The RX side already has all the necessary fallbacks, because receiving non-decrypted packets is supported. The thing needed on the RX side is to block resync requests, which are normally produced after receiving non-decrypted packets. The necessary synchronization is implemented for a graceful teardown: first the fallbacks are deployed, then the driver resources are released (it used to be possible to have a tls_dev_resync after tls_dev_del). A new flag called TLS_RX_DEV_DEGRADED is added to indicate the fallback mode. It's used to skip the RX resync logic completely, as it becomes useless, and some objects may be released (for example, resync_async, which is allocated and freed by the driver).

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/tls: Fix use-after-free after the TLS device goes down and up When a netdev with active TLS offload goes down, tls_device_down is called to stop the offload and tear down the TLS context. However, the socket stays alive, and it still points to the TLS context, which is now deallocated. If a netdev goes up, while the connection is still active, and the data flow resumes after a number of TCP retransmissions, it will lead to a use-after-free of the TLS context. This commit addresses this bug by keeping the context alive until its normal destruction, and implements the necessary fallbacks, so that the connection can resume in software (non-offloaded) kTLS mode. On the TX side tls_sw_fallback is used to encrypt all packets. The RX side already has all the necessary fallbacks, because receiving non-decrypted packets is supported. The thing needed on the RX side is to block resync requests, which are normally produced after receiving non-decrypted packets. The necessary synchronization is implemented for a graceful teardown: first the fallbacks are deployed, then the driver resources are released (it used to be possible to have a tls_dev_resync after tls_dev_del). A new flag called TLS_RX_DEV_DEGRADED is added to indicate the fallback mode. It's used to skip the RX resync logic completely, as it becomes useless, and some objects may be released (for example, resync_async, which is allocated and freed by the driver).

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
High: exploitation depends on specific conditions
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:H/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.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.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-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-0652Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

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

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

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 20 Mar 2024, published on 20 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-0716Multiples vulnérabilités dans le noyau Linux d'Ubuntu

letin de sécurité Ubuntu USN-6974-1 du 21 août 2024 https://ubuntu.com/security/notices/USN-6974-1 Bulletin de sécurité Ubuntu USN-6975-1 du 21 août 2024 https://ubuntu.com/security/notices/USN-6975-1 Bulletin de sécurité Ubuntu USN-6972-2 du 22 août 2024 https://ubuntu.com/security/notices/USN-6972-2 Bulletin de sécurité Ubuntu USN-6979-1 du 22 août 2024 https://ubuntu.com/security/notices/USN-6979-1 Référence CVE CVE-2021-37159 https://www.cve.org/CVERecord?id=CVE-2021-37159 Référence CVE CVE-2021-46904 https://www.cve.org/CVERecord?id=CVE-2021-46904 Référence CVE CVE-2021-46926 https://www.cve.org/CVERecord?id=CVE-2021-46926 Référence CVE CVE-2021-47131 https://www.cve.org/CVERecord?id=CVE-2021-47131 Référence CVE CVE-2022-48655 https://www.cve.org/CVERecord?id=CVE-2022-48655 Référence CVE CVE-2022-48674 https://www.cve.org/CVERecord?id=CVE-2022-48674 Référence CVE CVE-2022-48772 https://www.cve.org/CVERecord?id=CVE-2022-48772 Référence CVE CVE-2023-52434 https://www.cve.org/CVERecord?id=CVE-2023-52434 Référence CVE CVE-2023-52470 https://www.cve.org/CVERecord?id=CVE-2023-52470 Référence CVE CVE-2023-52585 https://www.cve.org/CVERecord?id=CVE-2023-52585 Référence CVE CVE-2023-52629 https://www.cve.org/CVERecord?id=CVE-2023-52629 Référence CVE CVE-2023-52644 https://www.cve.org/CVERecord?id=

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

rity/notices/USN-6926-2 Bulletin de sécurité Ubuntu USN-6895-4 du 02 août 2024 https://ubuntu.com/security/notices/USN-6895-4 Bulletin de sécurité Ubuntu USN-6949-1 du 08 août 2024 https://ubuntu.com/security/notices/USN-6949-1 Bulletin de sécurité Ubuntu USN-6950-1 du 08 août 2024 https://ubuntu.com/security/notices/USN-6950-1 Bulletin de sécurité Ubuntu USN-6951-1 du 08 août 2024 https://ubuntu.com/security/notices/USN-6951-1 Bulletin de sécurité Ubuntu USN-6952-1 du 09 août 2024 https://ubuntu.com/security/notices/USN-6952-1 Bulletin de sécurité Ubuntu USN-6953-1 du 09 août 2024 https://ubuntu.com/security/notices/USN-6953-1 Référence CVE CVE-2021-47131 https://www.cve.org/CVERecord?id=CVE-2021-47131 Référence CVE CVE-2022-48655 https://www.cve.org/CVERecord?id=CVE-2022-48655 Référence CVE CVE-2022-48674 https://www.cve.org/CVERecord?id=CVE-2022-48674 Référence CVE CVE-2022-48772 https://www.cve.org/CVERecord?id=CVE-2022-48772 Référence CVE CVE-2023-46343 https://www.cve.org/CVERecord?id=CVE-2023-46343 Référence CVE CVE-2023-52434 https://www.cve.org/CVERecord?id=CVE-2023-52434 Référence CVE CVE-2023-52435 https://www.cve.org/CVERecord?id=CVE-2023-52435 Référence CVE CVE-2023-52436 https://www.cve.org/CVERecord?id=CVE-2023-52436 Référence CVE CVE-2023-52443 https://www.cve.org/CVERecord?id=

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

urité Ubuntu USN-6923-2 du 30 juillet 2024 https://ubuntu.com/security/notices/USN-6923-2 Bulletin de sécurité Ubuntu USN-6924-2 du 30 juillet 2024 https://ubuntu.com/security/notices/USN-6924-2 Bulletin de sécurité Ubuntu USN-6927-1 du 30 juillet 2024 https://ubuntu.com/security/notices/USN-6927-1 Bulletin de sécurité Ubuntu USN-6938-1 du 31 juillet 2024 https://ubuntu.com/security/notices/USN-6938-1 Référence CVE CVE-2021-46932 https://www.cve.org/CVERecord?id=CVE-2021-46932 Référence CVE CVE-2021-46933 https://www.cve.org/CVERecord?id=CVE-2021-46933 Référence CVE CVE-2021-46960 https://www.cve.org/CVERecord?id=CVE-2021-46960 Référence CVE CVE-2021-47131 https://www.cve.org/CVERecord?id=CVE-2021-47131 Référence CVE CVE-2021-47194 https://www.cve.org/CVERecord?id=CVE-2021-47194 Référence CVE CVE-2022-38096 https://www.cve.org/CVERecord?id=CVE-2022-38096 Référence CVE CVE-2022-48619 https://www.cve.org/CVERecord?id=CVE-2022-48619 Référence CVE CVE-2022-48655 https://www.cve.org/CVERecord?id=CVE-2022-48655 Référence CVE CVE-2022-48808 https://www.cve.org/CVERecord?id=CVE-2022-48808 Référence CVE CVE-2023-46343 https://www.cve.org/CVERecord?id=CVE-2023-46343 Référence CVE CVE-2023-52434 https://www.cve.org/CVERecord?id=CVE-2023-52434 Référence CVE CVE-2023-52435 https://www.cve.org/CVERecord?id=

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

cord?id=CVE-2021-3743 Référence CVE CVE-2021-39698 https://www.cve.org/CVERecord?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=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0496Multiples 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-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=

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

d?id=CVE-2021-47101 Référence CVE CVE-2021-47104 https://www.cve.org/CVERecord?id=CVE-2021-47104 Référence CVE CVE-2021-47110 https://www.cve.org/CVERecord?id=CVE-2021-47110 Référence CVE CVE-2021-47112 https://www.cve.org/CVERecord?id=CVE-2021-47112 Référence CVE CVE-2021-47113 https://www.cve.org/CVERecord?id=CVE-2021-47113 Référence CVE CVE-2021-47114 https://www.cve.org/CVERecord?id=CVE-2021-47114 Référence CVE CVE-2021-47117 https://www.cve.org/CVERecord?id=CVE-2021-47117 Référence CVE CVE-2021-47118 https://www.cve.org/CVERecord?id=CVE-2021-47118 Référence CVE CVE-2021-47119 https://www.cve.org/CVERecord?id=CVE-2021-47119 Référence CVE CVE-2021-47131 https://www.cve.org/CVERecord?id=CVE-2021-47131 Référence CVE CVE-2021-47138 https://www.cve.org/CVERecord?id=CVE-2021-47138 Référence CVE CVE-2021-47141 https://www.cve.org/CVERecord?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=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2021-021631Linux の 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.18, 5.10.43 ≤ 5.10.*, 5.12.10 ≤ 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 15 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-33779
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-33779↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor 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-47131 · cve.blacktree.nl