BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2020
CVE-2020-10690High confidence

There is a use-after-free in kernel versions before 5.5 due to a race condition between the release of ptp_clock and cdev while resource deallocation

Red Hat · kernel

6.5MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. 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 severityMediumOperational priority:Low, lowered one band.downgradedsince 4 Aug 2024

Evidence used

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

Compensating controls

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

Verification

  1. Confirm that the asset runs Red Hat kernel 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: No default targetRemediation target: Normal maintenance

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.4.8-1Debian Security Tracker ↗Source updated 23 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.4.8-1Debian Security Tracker ↗Source updated 23 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.4.8-1Debian Security Tracker ↗Source updated 23 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.4.8-1Debian Security Tracker ↗Source updated 23 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 23 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-2020-10690 · CSAF 2.0 · revision 39 · interimSUSE Product Security TeamCVE-2020-10690
27 known affected

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

  • kernel-source-azure as component of HPE Helion OpenStack 8
  • kernel-source-azure as component of SUSE Enterprise Storage 7
  • 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
  • kernel-source-azure as component of SUSE Linux Enterprise Module for Public Cloud 15 SP2
  • kernel-source-azure as component of SUSE Linux Enterprise Module for Public Cloud 15
  • kernel-source-azure as component of SUSE Linux Enterprise Server 15 SP2
  • kernel-source-azure as component of SUSE Linux Enterprise Server 15
  • kernel-source-azure as component of SUSE Linux Enterprise Server for SAP Applications 15 SP2
  • kernel-source-azure as component of SUSE Linux Enterprise Server for SAP Applications 15
  • kernel-source-azure as component of SUSE Manager Proxy 4.1
  • kernel-source-azure as component of SUSE Manager Retail Branch Server 4.1
Summary
There is a use-after-free in kernel versions before 5.5 due to a race condition between the release of ptp_clock and cdev while resource deallocation. When a (high privileged) process allocates a ptp device file (like /dev/ptpX) and voluntarily goes to sleep. During this time if the underlying device is removed, it can cause an exploitable condition as the process wakes up to terminate and clean all attached files. The system crashes due to the cdev structure being invalid (as already freed) which is pointed to by the inode.
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-2020-3124

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

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. 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

There is a use-after-free in kernel versions before 5.5 due to a race condition between the release of ptp_clock and cdev while resource deallocation. When a (high privileged) process allocates a ptp device file (like /dev/ptpX) and voluntarily goes to sleep. During this time if the underlying device is removed, it can cause an exploitable condition as the process wakes up to terminate and clean all attached files. The system crashes due to the cdev structure being invalid (as already freed) which is pointed to by the inode.

What

There is a use-after-free in kernel versions before 5.5 due to a race condition between the release of ptp_clock and cdev while resource deallocation. When a (high privileged) process allocates a ptp device file (like /dev/ptpX) and voluntarily goes to sleep. During this time if the underlying device is removed, it can cause an exploitable condition as the process wakes up to terminate and clean all attached files. The system crashes due to the cdev structure being invalid (as already freed) which is pointed to by the inode.

Why

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

How

An attacker operating through local access may attempt exploitation with elevated privileges. If successful, the issue may disrupt the affected service.

What

There is a use-after-free in kernel versions before 5.5 due to a race condition between the release of ptp_clock and cdev while resource deallocation. When a (high privileged) process allocates a ptp device file (like /dev/ptpX) and voluntarily goes to sleep. During this time if the underlying device is removed, it can cause an exploitable condition as the process wakes up to terminate and clean all attached files. The system crashes due to the cdev structure being invalid (as already freed) which is pointed to by the inode.

Why

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

How

An attacker operating through local access may attempt exploitation with elevated privileges. 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
local access → Use After Free → disrupt the affected service
Attack surface
Local
Privileges required
High: elevated access is required
User interaction
Required interaction required
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:L/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H

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

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRHighPrivileges required: The attacker needs elevated or administrative privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
Denial 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-2022-1925Linux Kernel: Schwachstelle ermöglicht Denial of Service

Ein lokaler Angreifer kann eine Schwachstelle im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20200513Security Bulletin 13 May 2020

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

Official advisory ↗
CERT-FR · French · CERTFR-2022-AVI-267Multiples vulnérabilités dans Juniper Networks Junos Space

ve.org/CVERecord?id=CVE-2019-9458 Référence CVE CVE-2019-9503 https://www.cve.org/CVERecord?id=CVE-2019-9503 Référence CVE CVE-2019-9636 https://www.cve.org/CVERecord?id=CVE-2019-9636 Référence CVE CVE-2019-9740 https://www.cve.org/CVERecord?id=CVE-2019-9740 Référence CVE CVE-2019-9824 https://www.cve.org/CVERecord?id=CVE-2019-9824 Référence CVE CVE-2019-9924 https://www.cve.org/CVERecord?id=CVE-2019-9924 Référence CVE CVE-2019-9947 https://www.cve.org/CVERecord?id=CVE-2019-9947 Référence CVE CVE-2019-9948 https://www.cve.org/CVERecord?id=CVE-2019-9948 Référence CVE CVE-2020-10531 https://www.cve.org/CVERecord?id=CVE-2020-10531 Référence CVE CVE-2020-10690 https://www.cve.org/CVERecord?id=CVE-2020-10690 Référence CVE CVE-2020-10703 https://www.cve.org/CVERecord?id=CVE-2020-10703 Référence CVE CVE-2020-10713 https://www.cve.org/CVERecord?id=CVE-2020-10713 Référence CVE CVE-2020-10732 https://www.cve.org/CVERecord?id=CVE-2020-10732 Référence CVE CVE-2020-10742 https://www.cve.org/CVERecord?id=CVE-2020-10742 Référence CVE CVE-2020-10751 https://www.cve.org/CVERecord?id=CVE-2020-10751 Référence CVE CVE-2020-10754 https://www.cve.org/CVERecord?id=CVE-2020-10754 Référence CVE CVE-2020-10757 https://www.cve.org/CVERecord?id=CVE-2020-10757 Référence CVE CVE-2020-10769 https://www.cve.org/CVERecord?id=

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

ecord?id=CVE-2019-19534 Référence CVE CVE-2019-19537 https://www.cve.org/CVERecord?id=CVE-2019-19537 Référence CVE CVE-2019-19767 https://www.cve.org/CVERecord?id=CVE-2019-19767 Référence CVE CVE-2019-19807 https://www.cve.org/CVERecord?id=CVE-2019-19807 Référence CVE CVE-2019-20054 https://www.cve.org/CVERecord?id=CVE-2019-20054 Référence CVE CVE-2019-20095 https://www.cve.org/CVERecord?id=CVE-2019-20095 Référence CVE CVE-2019-20636 https://www.cve.org/CVERecord?id=CVE-2019-20636 Référence CVE CVE-2019-9454 https://www.cve.org/CVERecord?id=CVE-2019-9454 Référence CVE CVE-2019-9458 https://www.cve.org/CVERecord?id=CVE-2019-9458 Référence CVE CVE-2020-10690 https://www.cve.org/CVERecord?id=CVE-2020-10690 Référence CVE CVE-2020-10732 https://www.cve.org/CVERecord?id=CVE-2020-10732 Référence CVE CVE-2020-10742 https://www.cve.org/CVERecord?id=CVE-2020-10742 Référence CVE CVE-2020-10751 https://www.cve.org/CVERecord?id=CVE-2020-10751 Référence CVE CVE-2020-10942 https://www.cve.org/CVERecord?id=CVE-2020-10942 Référence CVE CVE-2020-11565 https://www.cve.org/CVERecord?id=CVE-2020-11565 Référence CVE CVE-2020-12770 https://www.cve.org/CVERecord?id=CVE-2020-12770 Référence CVE CVE-2020-12826 https://www.cve.org/CVERecord?id=CVE-2020-12826 Référence CVE CVE-2020-14305 https://www.cve.org/CVERecord?id=

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

ERecord?id=CVE-2019-19462 Référence CVE CVE-2019-20806 https://www.cve.org/CVERecord?id=CVE-2019-20806 Référence CVE CVE-2019-20810 https://www.cve.org/CVERecord?id=CVE-2019-20810 Référence CVE CVE-2019-20812 https://www.cve.org/CVERecord?id=CVE-2019-20812 Référence CVE CVE-2019-20908 https://www.cve.org/CVERecord?id=CVE-2019-20908 Référence CVE CVE-2019-9455 https://www.cve.org/CVERecord?id=CVE-2019-9455 Référence CVE CVE-2020-0305 https://www.cve.org/CVERecord?id=CVE-2020-0305 Référence CVE CVE-2020-0543 https://www.cve.org/CVERecord?id=CVE-2020-0543 Référence CVE CVE-2020-10135 https://www.cve.org/CVERecord?id=CVE-2020-10135 Référence CVE CVE-2020-10690 https://www.cve.org/CVERecord?id=CVE-2020-10690 Référence CVE CVE-2020-10711 https://www.cve.org/CVERecord?id=CVE-2020-10711 Référence CVE CVE-2020-10720 https://www.cve.org/CVERecord?id=CVE-2020-10720 Référence CVE CVE-2020-10732 https://www.cve.org/CVERecord?id=CVE-2020-10732 Référence CVE CVE-2020-10751 https://www.cve.org/CVERecord?id=CVE-2020-10751 Référence CVE CVE-2020-10757 https://www.cve.org/CVERecord?id=CVE-2020-10757 Référence CVE CVE-2020-10766 https://www.cve.org/CVERecord?id=CVE-2020-10766 Référence CVE CVE-2020-10767 https://www.cve.org/CVERecord?id=CVE-2020-10767 Référence CVE CVE-2020-10768 https://www.cve.org/CVERecord?id=

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

ERecord?id=CVE-2019-19462 Référence CVE CVE-2019-20806 https://www.cve.org/CVERecord?id=CVE-2019-20806 Référence CVE CVE-2019-20810 https://www.cve.org/CVERecord?id=CVE-2019-20810 Référence CVE CVE-2019-20812 https://www.cve.org/CVERecord?id=CVE-2019-20812 Référence CVE CVE-2019-20908 https://www.cve.org/CVERecord?id=CVE-2019-20908 Référence CVE CVE-2019-9455 https://www.cve.org/CVERecord?id=CVE-2019-9455 Référence CVE CVE-2020-0305 https://www.cve.org/CVERecord?id=CVE-2020-0305 Référence CVE CVE-2020-0543 https://www.cve.org/CVERecord?id=CVE-2020-0543 Référence CVE CVE-2020-10135 https://www.cve.org/CVERecord?id=CVE-2020-10135 Référence CVE CVE-2020-10690 https://www.cve.org/CVERecord?id=CVE-2020-10690 Référence CVE CVE-2020-10711 https://www.cve.org/CVERecord?id=CVE-2020-10711 Référence CVE CVE-2020-10720 https://www.cve.org/CVERecord?id=CVE-2020-10720 Référence CVE CVE-2020-10732 https://www.cve.org/CVERecord?id=CVE-2020-10732 Référence CVE CVE-2020-10751 https://www.cve.org/CVERecord?id=CVE-2020-10751 Référence CVE CVE-2020-10757 https://www.cve.org/CVERecord?id=CVE-2020-10757 Référence CVE CVE-2020-10766 https://www.cve.org/CVERecord?id=CVE-2020-10766 Référence CVE CVE-2020-10767 https://www.cve.org/CVERecord?id=CVE-2020-10767 Référence CVE CVE-2020-10768 https://www.cve.org/CVERecord?id=

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

De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire, un déni de service à distance et un contournement de la politique de sécurité.

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

/announcement/2020/suse-su-20201604-1/ Bulletin de sécurité SUSE suse-su-20201605-1 du 10 juin 2020 https://www.suse.com/support/update/announcement/2020/suse-su-20201605-1/ Référence CVE CVE-2018-1000199 https://www.cve.org/CVERecord?id=CVE-2018-1000199 Référence CVE CVE-2019-19462 https://www.cve.org/CVERecord?id=CVE-2019-19462 Référence CVE CVE-2019-20806 https://www.cve.org/CVERecord?id=CVE-2019-20806 Référence CVE CVE-2019-20812 https://www.cve.org/CVERecord?id=CVE-2019-20812 Référence CVE CVE-2019-9455 https://www.cve.org/CVERecord?id=CVE-2019-9455 Référence CVE CVE-2020-0543 https://www.cve.org/CVERecord?id=CVE-2020-0543 Référence CVE CVE-2020-10690 https://www.cve.org/CVERecord?id=CVE-2020-10690 Référence CVE CVE-2020-10711 https://www.cve.org/CVERecord?id=CVE-2020-10711 Référence CVE CVE-2020-10720 https://www.cve.org/CVERecord?id=CVE-2020-10720 Référence CVE CVE-2020-10732 https://www.cve.org/CVERecord?id=CVE-2020-10732 Référence CVE CVE-2020-10751 https://www.cve.org/CVERecord?id=CVE-2020-10751 Référence CVE CVE-2020-10757 https://www.cve.org/CVERecord?id=CVE-2020-10757 Référence CVE CVE-2020-12114 https://www.cve.org/CVERecord?id=CVE-2020-12114 Référence CVE CVE-2020-12464 https://www.cve.org/CVERecord?id=CVE-2020-12464 Référence CVE CVE-2020-12652 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2020-AVI-368Multiples vulnérabilités dans le noyau Linux de Debian

g/CVERecord?id=CVE-2019-19768 Référence CVE CVE-2019-20636 https://www.cve.org/CVERecord?id=CVE-2019-20636 Référence CVE CVE-2019-20806 https://www.cve.org/CVERecord?id=CVE-2019-20806 Référence CVE CVE-2019-20811 https://www.cve.org/CVERecord?id=CVE-2019-20811 Référence CVE CVE-2019-2182 https://www.cve.org/CVERecord?id=CVE-2019-2182 Référence CVE CVE-2019-3016 https://www.cve.org/CVERecord?id=CVE-2019-3016 Référence CVE CVE-2019-5108 https://www.cve.org/CVERecord?id=CVE-2019-5108 Référence CVE CVE-2020-0009 https://www.cve.org/CVERecord?id=CVE-2020-0009 Référence CVE CVE-2020-0543 https://www.cve.org/CVERecord?id=CVE-2020-0543 Référence CVE CVE-2020-10690 https://www.cve.org/CVERecord?id=CVE-2020-10690 Référence CVE CVE-2020-10711 https://www.cve.org/CVERecord?id=CVE-2020-10711 Référence CVE CVE-2020-10732 https://www.cve.org/CVERecord?id=CVE-2020-10732 Référence CVE CVE-2020-10751 https://www.cve.org/CVERecord?id=CVE-2020-10751 Référence CVE CVE-2020-10757 https://www.cve.org/CVERecord?id=CVE-2020-10757 Référence CVE CVE-2020-10942 https://www.cve.org/CVERecord?id=CVE-2020-10942 Référence CVE CVE-2020-11494 https://www.cve.org/CVERecord?id=CVE-2020-11494 Référence CVE CVE-2020-11565 https://www.cve.org/CVERecord?id=CVE-2020-11565 Référence CVE CVE-2020-11608 https://www.cve.org/CVERecord?id=

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

CVERecord?id=CVE-2019-19768 Référence CVE CVE-2019-19965 https://www.cve.org/CVERecord?id=CVE-2019-19965 Référence CVE CVE-2019-19966 https://www.cve.org/CVERecord?id=CVE-2019-19966 Référence CVE CVE-2019-20054 https://www.cve.org/CVERecord?id=CVE-2019-20054 Référence CVE CVE-2019-20096 https://www.cve.org/CVERecord?id=CVE-2019-20096 Référence CVE CVE-2019-3701 https://www.cve.org/CVERecord?id=CVE-2019-3701 Référence CVE CVE-2019-5108 https://www.cve.org/CVERecord?id=CVE-2019-5108 Référence CVE CVE-2019-9455 https://www.cve.org/CVERecord?id=CVE-2019-9455 Référence CVE CVE-2019-9458 https://www.cve.org/CVERecord?id=CVE-2019-9458 Référence CVE CVE-2020-10690 https://www.cve.org/CVERecord?id=CVE-2020-10690 Référence CVE CVE-2020-10720 https://www.cve.org/CVERecord?id=CVE-2020-10720 Référence CVE CVE-2020-10942 https://www.cve.org/CVERecord?id=CVE-2020-10942 Référence CVE CVE-2020-11494 https://www.cve.org/CVERecord?id=CVE-2020-11494 Référence CVE CVE-2020-11608 https://www.cve.org/CVERecord?id=CVE-2020-11608 Référence CVE CVE-2020-11609 https://www.cve.org/CVERecord?id=CVE-2020-11609 Référence CVE CVE-2020-2732 https://www.cve.org/CVERecord?id=CVE-2020-2732 Référence CVE CVE-2020-8647 https://www.cve.org/CVERecord?id=CVE-2020-8647 Référence CVE CVE-2020-8648 https://www.cve.org/CVERecord?id=CVE-2

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2020-005323Kernel における解放済みメモリの使用に関する脆弱性

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
An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 8 May 2020 · Last source change 4 Aug 2024, 11:06 UTC · CWE-416 · Use After Free

CVE recordCVE.org · 5.1
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-2020-3124
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCNA
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-2020-3124↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor 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-2020-10690 · cve.blacktree.nl