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

In the Linux kernel before 6.4.5, drivers/gpu/drm/drm_atomic.c has a use-after-free during a race condition between a nonblocking atomic commit and a driver unload

Unknown · Unknown

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

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

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 29 Aug 2024

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.25% 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 Unknown Unknown and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

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

Cross-source reconciliation

Remediation availability differs by product scope

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

Distribution package intelligence

Release-specific package status

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

5 package states
Package result overrides the generic status

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

Repository candidate not checked

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

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.4.11-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.52-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.4.11-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.4.11-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-2023-51043 · CSAF 2.0 · revision 62 · interimSUSE Product Security TeamCVE-2023-51043
87 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
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 15
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 15
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15
Summary
In the Linux kernel before 6.4.5, drivers/gpu/drm/drm_atomic.c has a use-after-free during a race condition between a nonblocking atomic commit and a driver unload.
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-2023-55770

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 before 6.4.5, drivers/gpu/drm/drm_atomic.c has a use-after-free during a race condition between a nonblocking atomic commit and a driver unload.

What

In the Linux kernel before 6.4.5, drivers/gpu/drm/drm_atomic.c has a use-after-free during a race condition between a nonblocking atomic commit and a driver unload.

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 low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel before 6.4.5, drivers/gpu/drm/drm_atomic.c has a use-after-free during a race condition between a nonblocking atomic commit and a driver unload.

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 low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

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

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

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

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

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

Likely attack path
local access → Use After Free → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
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:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

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

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-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-1226Red Hat OpenShift: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Red Hat OpenShift ausnutzen, um Dateien zu manipulieren, einen Denial-of-Service-Zustand zu verursachen, beliebigen Code auszuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder um weitere nicht spezifizierte Angriffe auszuführen.

Official advisory ↗
BSI · German · WID-SEC-2024-1086IBM QRadar SIEM: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM QRadar SIEM ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, Dateien zu manipulieren, seine Privilegien zu erweitern, einen Cross-Site-Scripting (XSS)-Angriff durchzuführen oder einen nicht spezifizierten Angriff auszuführen.

Official advisory ↗
BSI · German · WID-SEC-2024-0182Linux Kernel: Mehrere Schwachstellen

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-20240124Security Bulletin 24 Jan 2024

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

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

ecord?id=CVE-2023-46813 Référence CVE CVE-2023-4732 https://www.cve.org/CVERecord?id=CVE-2023-4732 Référence CVE CVE-2023-48795 https://www.cve.org/CVERecord?id=CVE-2023-48795 Référence CVE CVE-2023-4921 https://www.cve.org/CVERecord?id=CVE-2023-4921 Référence CVE CVE-2023-50387 https://www.cve.org/CVERecord?id=CVE-2023-50387 Référence CVE CVE-2023-50868 https://www.cve.org/CVERecord?id=CVE-2023-50868 Référence CVE CVE-2023-50960 https://www.cve.org/CVERecord?id=CVE-2023-50960 Référence CVE CVE-2023-50961 https://www.cve.org/CVERecord?id=CVE-2023-50961 Référence CVE CVE-2023-51042 https://www.cve.org/CVERecord?id=CVE-2023-51042 Référence CVE CVE-2023-51043 https://www.cve.org/CVERecord?id=CVE-2023-51043 Référence CVE CVE-2023-51385 https://www.cve.org/CVERecord?id=CVE-2023-51385 Référence CVE CVE-2023-51779 https://www.cve.org/CVERecord?id=CVE-2023-51779 Référence CVE CVE-2023-5178 https://www.cve.org/CVERecord?id=CVE-2023-5178 Référence CVE CVE-2023-51780 https://www.cve.org/CVERecord?id=CVE-2023-51780 Référence CVE CVE-2023-52340 https://www.cve.org/CVERecord?id=CVE-2023-52340 Référence CVE CVE-2023-52425 https://www.cve.org/CVERecord?id=CVE-2023-52425 Référence CVE CVE-2023-52434 https://www.cve.org/CVERecord?id=CVE-2023-52434 Référence CVE CVE-2023-52448 https://www.cve.org/CVERecord?id=CV

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

CVERecord?id=CVE-2023-46813 Référence CVE CVE-2023-4732 https://www.cve.org/CVERecord?id=CVE-2023-4732 Référence CVE CVE-2023-4807 https://www.cve.org/CVERecord?id=CVE-2023-4807 Référence CVE CVE-2023-4921 https://www.cve.org/CVERecord?id=CVE-2023-4921 Référence CVE CVE-2023-50387 https://www.cve.org/CVERecord?id=CVE-2023-50387 Référence CVE CVE-2023-5072 https://www.cve.org/CVERecord?id=CVE-2023-5072 Référence CVE CVE-2023-50782 https://www.cve.org/CVERecord?id=CVE-2023-50782 Référence CVE CVE-2023-50868 https://www.cve.org/CVERecord?id=CVE-2023-50868 Référence CVE CVE-2023-51042 https://www.cve.org/CVERecord?id=CVE-2023-51042 Référence CVE CVE-2023-51043 https://www.cve.org/CVERecord?id=CVE-2023-51043 Référence CVE CVE-2023-5178 https://www.cve.org/CVERecord?id=CVE-2023-5178 Référence CVE CVE-2023-52425 https://www.cve.org/CVERecord?id=CVE-2023-52425 Référence CVE CVE-2023-5633 https://www.cve.org/CVERecord?id=CVE-2023-5633 Référence CVE CVE-2023-5676 https://www.cve.org/CVERecord?id=CVE-2023-5676 Référence CVE CVE-2023-5717 https://www.cve.org/CVERecord?id=CVE-2023-5717 Référence CVE CVE-2023-6356 https://www.cve.org/CVERecord?id=CVE-2023-6356 Référence CVE CVE-2023-6535 https://www.cve.org/CVERecord?id=CVE-2023-6535 Référence CVE CVE-2023-6536 https://www.cve.org/CVERecord?id=CVE-2023-6536

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

ord?id=CVE-2023-39193 Référence CVE CVE-2023-39194 https://www.cve.org/CVERecord?id=CVE-2023-39194 Référence CVE CVE-2023-39198 https://www.cve.org/CVERecord?id=CVE-2023-39198 Référence CVE CVE-2023-40283 https://www.cve.org/CVERecord?id=CVE-2023-40283 Référence CVE CVE-2023-4133 https://www.cve.org/CVERecord?id=CVE-2023-4133 Référence CVE CVE-2023-42754 https://www.cve.org/CVERecord?id=CVE-2023-42754 Référence CVE CVE-2023-42756 https://www.cve.org/CVERecord?id=CVE-2023-42756 Référence CVE CVE-2023-45863 https://www.cve.org/CVERecord?id=CVE-2023-45863 Référence CVE CVE-2023-46862 https://www.cve.org/CVERecord?id=CVE-2023-46862 Référence CVE CVE-2023-51043 https://www.cve.org/CVERecord?id=CVE-2023-51043 Référence CVE CVE-2023-51779 https://www.cve.org/CVERecord?id=CVE-2023-51779 Référence CVE CVE-2023-51780 https://www.cve.org/CVERecord?id=CVE-2023-51780 Référence CVE CVE-2023-52434 https://www.cve.org/CVERecord?id=CVE-2023-52434 Référence CVE CVE-2023-52448 https://www.cve.org/CVERecord?id=CVE-2023-52448 Référence CVE CVE-2023-52476 https://www.cve.org/CVERecord?id=CVE-2023-52476 Référence CVE CVE-2023-52489 https://www.cve.org/CVERecord?id=CVE-2023-52489 Référence CVE CVE-2023-52522 https://www.cve.org/CVERecord?id=CVE-2023-52522 Référence CVE CVE-2023-52529 https://www.cve.org/CVERecord?id=

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

ERecord?id=CVE-2021-46936 Référence CVE CVE-2021-46955 https://www.cve.org/CVERecord?id=CVE-2021-46955 Référence CVE CVE-2021-46966 https://www.cve.org/CVERecord?id=CVE-2021-46966 Référence CVE CVE-2021-46990 https://www.cve.org/CVERecord?id=CVE-2021-46990 Référence CVE CVE-2022-20422 https://www.cve.org/CVERecord?id=CVE-2022-20422 Référence CVE CVE-2023-1382 https://www.cve.org/CVERecord?id=CVE-2023-1382 Référence CVE CVE-2023-1838 https://www.cve.org/CVERecord?id=CVE-2023-1838 Référence CVE CVE-2023-1998 https://www.cve.org/CVERecord?id=CVE-2023-1998 Référence CVE CVE-2023-24023 https://www.cve.org/CVERecord?id=CVE-2023-24023 Référence CVE CVE-2023-51043 https://www.cve.org/CVERecord?id=CVE-2023-51043 Référence CVE CVE-2023-51779 https://www.cve.org/CVERecord?id=CVE-2023-51779 Référence CVE CVE-2023-52429 https://www.cve.org/CVERecord?id=CVE-2023-52429 Référence CVE CVE-2023-52445 https://www.cve.org/CVERecord?id=CVE-2023-52445 Référence CVE CVE-2023-52451 https://www.cve.org/CVERecord?id=CVE-2023-52451 Référence CVE CVE-2023-52464 https://www.cve.org/CVERecord?id=CVE-2023-52464 Référence CVE CVE-2023-52600 https://www.cve.org/CVERecord?id=CVE-2023-52600 Référence CVE CVE-2023-52603 https://www.cve.org/CVERecord?id=CVE-2023-52603 Référence CVE CVE-2023-6915 https://www.cve.org/CVERecord?id=C

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

ERecord?id=CVE-2023-31436 Référence CVE CVE-2023-33951 https://www.cve.org/CVERecord?id=CVE-2023-33951 Référence CVE CVE-2023-33952 https://www.cve.org/CVERecord?id=CVE-2023-33952 Référence CVE CVE-2023-3611 https://www.cve.org/CVERecord?id=CVE-2023-3611 Référence CVE CVE-2023-40283 https://www.cve.org/CVERecord?id=CVE-2023-40283 Référence CVE CVE-2023-4459 https://www.cve.org/CVERecord?id=CVE-2023-4459 Référence CVE CVE-2023-45862 https://www.cve.org/CVERecord?id=CVE-2023-45862 Référence CVE CVE-2023-4921 https://www.cve.org/CVERecord?id=CVE-2023-4921 Référence CVE CVE-2023-51042 https://www.cve.org/CVERecord?id=CVE-2023-51042 Référence CVE CVE-2023-51043 https://www.cve.org/CVERecord?id=CVE-2023-51043 Référence CVE CVE-2023-5633 https://www.cve.org/CVERecord?id=CVE-2023-5633 Référence CVE CVE-2023-6606 https://www.cve.org/CVERecord?id=CVE-2023-6606 Référence CVE CVE-2023-6610 https://www.cve.org/CVERecord?id=CVE-2023-6610 Référence CVE CVE-2023-6817 https://www.cve.org/CVERecord?id=CVE-2023-6817 Référence CVE CVE-2023-6931 https://www.cve.org/CVERecord?id=CVE-2023-6931 Référence CVE CVE-2023-6932 https://www.cve.org/CVERecord?id=CVE-2023-6932 Référence CVE CVE-2023-7192 https://www.cve.org/CVERecord?id=CVE-2023-7192 Référence CVE CVE-2024-0565 https://www.cve.org/CVERecord?id=CVE-2024-0565 R

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

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

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

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

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

SUSE-SU-2024:0515-1 du 15 février 2024 https://www.suse.com/support/update/announcement/2024/suse-su-20240515-1/ Bulletin de sécurité SUSE SUSE-SU-2024:0516-1 du 15 février 2024 https://www.suse.com/support/update/announcement/2024/suse-su-20240516-1/ Référence CVE CVE-2021-33631 https://www.cve.org/CVERecord?id=CVE-2021-33631 Référence CVE CVE-2023-46838 https://www.cve.org/CVERecord?id=CVE-2023-46838 Référence CVE CVE-2023-47233 https://www.cve.org/CVERecord?id=CVE-2023-47233 Référence CVE CVE-2023-4921 https://www.cve.org/CVERecord?id=CVE-2023-4921 Référence CVE CVE-2023-51042 https://www.cve.org/CVERecord?id=CVE-2023-51042 Référence CVE CVE-2023-51043 https://www.cve.org/CVERecord?id=CVE-2023-51043 Référence CVE CVE-2023-51780 https://www.cve.org/CVERecord?id=CVE-2023-51780 Référence CVE CVE-2023-51782 https://www.cve.org/CVERecord?id=CVE-2023-51782 Référence CVE CVE-2023-6040 https://www.cve.org/CVERecord?id=CVE-2023-6040 Référence CVE CVE-2023-6356 https://www.cve.org/CVERecord?id=CVE-2023-6356 Référence CVE CVE-2023-6531 https://www.cve.org/CVERecord?id=CVE-2023-6531 Référence CVE CVE-2023-6535 https://www.cve.org/CVERecord?id=CVE-2023-6535 Référence CVE CVE-2023-6536 https://www.cve.org/CVERecord?id=CVE-2023-6536 Référence CVE CVE-2023-6610 https://www.cve.org/CVERecord?id=CVE-2023-66

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2023-025740Linux の 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
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 23 Jan 2024 · Last source change 29 Aug 2024, 14:28 UTC · CWE-416 · Use After Free

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

Missing structured fields: affected product. Missing data is not evidence of low risk; review the primary advisory.

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
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-2023-51043 · cve.blacktree.nl