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

s390/dasd: protect device queue against concurrent access

Linux · Linux

5.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 11 May 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.24% 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 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: 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.6.6.8-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.66-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.6.8-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.6.8-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.

2 current
CVE-2023-52774 · CSAF 2.0 · revision 104 · interimSUSE Product Security TeamCVE-2023-52774
195 known affected

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

  • kernel-default as component of SUSE Enterprise Storage 7.1
  • kernel-default-devel as component of SUSE Enterprise Storage 7.1
  • kernel-devel as component of SUSE Enterprise Storage 7.1
  • kernel-macros as component of SUSE Enterprise Storage 7.1
  • kernel-source as component of SUSE Enterprise Storage 7.1
  • reiserfs-kmp-default as component of SUSE Enterprise Storage 7.1
  • 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
Summary
In the Linux kernel, the following vulnerability has been resolved: s390/dasd: protect device queue against concurrent access In dasd_profile_start() the amount of requests on the device queue are counted. The access to the device queue is unprotected against concurrent access. With a lot of parallel I/O, especially with alias devices enabled, the device queue can change while dasd_profile_start() is accessing the queue. In the worst case this leads to a kernel panic due to incorrect pointer accesses. Fix this by taking the device lock before accessing the queue and counting the requests. Additionally the check for a valid profile data pointer can be done earlier to avoid unnecessary locking in a hot path.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
SSA-613116 · CSAF 2.0 · revision 3 · interimSiemens ProductCERTSSA-613116: Multiple Vulnerabilities in Third-Party Components in SINEC OS before V3.1
3 known not affected

The vendor explicitly states that these products are not affected by this CVE.

  • RUGGEDCOM RST2428P (6GK6242-6PA00)
  • SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family
  • SCALANCE XCM-/XRM-/XCH-/XRH-300 family
Summary
In the Linux kernel, the following vulnerability has been resolved: s390/dasd: protect device queue against concurrent access
Remediation
No remediation text is recorded.
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-59491

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

In the Linux kernel, the following vulnerability has been resolved: s390/dasd: protect device queue against concurrent access In dasd_profile_start() the amount of requests on the device queue are counted. The access to the device queue is unprotected against concurrent access. With a lot of parallel I/O, especially with alias devices enabled, the device queue can change while dasd_profile_start() is accessing the queue. In the worst case this leads to a kernel panic due to incorrect pointer accesses. Fix this by taking the device lock before accessing the queue and counting the requests. Additionally the check for a valid profile data pointer can be done earlier to avoid unnecessary locking in a hot path.

What

In the Linux kernel, the following vulnerability has been resolved: s390/dasd: protect device queue against concurrent access In dasd_profile_start() the amount of requests on the device queue are counted. The access to the device queue is unprotected against concurrent access. With a lot of parallel I/O, especially with alias devices enabled, the device queue can change while dasd_profile_start() is accessing the queue. In the worst case this leads to a kernel panic due to incorrect pointer accesses. Fix this by taking the device lock before accessing the queue and counting the requests. Additionally the check for a valid profile data pointer can be done earlier to avoid unnecessary locking in a hot path.

Why

The product dereferences a pointer that it expects to be valid but is NULL.

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, the following vulnerability has been resolved: s390/dasd: protect device queue against concurrent access In dasd_profile_start() the amount of requests on the device queue are counted. The access to the device queue is unprotected against concurrent access. With a lot of parallel I/O, especially with alias devices enabled, the device queue can change while dasd_profile_start() is accessing the queue. In the worst case this leads to a kernel panic due to incorrect pointer accesses. Fix this by taking the device lock before accessing the queue and counting the requests. Additionally the check for a valid profile data pointer can be done earlier to avoid unnecessary locking in a hot path.

Why

The product dereferences a pointer that it expects to be valid but is NULL.

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 → NULL Pointer Dereference → 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
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-476 ↗

CWE-476: NULL Pointer Dereference. The product dereferences a pointer that it expects to be valid but is NULL.

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:L/UI:N/S:U/C:N/I:N/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.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.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.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-476
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-1197Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service und unspezifische Angriffe

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder unspezifische Angriffe durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20240522Security Bulletin 22 May 2024

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

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0677Multiples vulnérabilités dans les produits Siemens

d?id=CVE-2023-52619 Référence CVE CVE-2023-52622 https://www.cve.org/CVERecord?id=CVE-2023-52622 Référence CVE CVE-2023-52623 https://www.cve.org/CVERecord?id=CVE-2023-52623 Référence CVE CVE-2023-52637 https://www.cve.org/CVERecord?id=CVE-2023-52637 Référence CVE CVE-2023-52654 https://www.cve.org/CVERecord?id=CVE-2023-52654 Référence CVE CVE-2023-52655 https://www.cve.org/CVERecord?id=CVE-2023-52655 Référence CVE CVE-2023-52670 https://www.cve.org/CVERecord?id=CVE-2023-52670 Référence CVE CVE-2023-52753 https://www.cve.org/CVERecord?id=CVE-2023-52753 Référence CVE CVE-2023-52764 https://www.cve.org/CVERecord?id=CVE-2023-52764 Référence CVE CVE-2023-52774 https://www.cve.org/CVERecord?id=CVE-2023-52774 Référence CVE CVE-2023-52784 https://www.cve.org/CVERecord?id=CVE-2023-52784 Référence CVE CVE-2023-52789 https://www.cve.org/CVERecord?id=CVE-2023-52789 Référence CVE CVE-2023-52791 https://www.cve.org/CVERecord?id=CVE-2023-52791 Référence CVE CVE-2023-52796 https://www.cve.org/CVERecord?id=CVE-2023-52796 Référence CVE CVE-2023-52799 https://www.cve.org/CVERecord?id=CVE-2023-52799 Référence CVE CVE-2023-52804 https://www.cve.org/CVERecord?id=CVE-2023-52804 Référence CVE CVE-2023-52805 https://www.cve.org/CVERecord?id=CVE-2023-52805 Référence CVE CVE-2023-52806 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2023-52764 Référence CVE CVE-2023-52765 https://www.cve.org/CVERecord?id=CVE-2023-52765 Référence CVE CVE-2023-52766 https://www.cve.org/CVERecord?id=CVE-2023-52766 Référence CVE CVE-2023-52767 https://www.cve.org/CVERecord?id=CVE-2023-52767 Référence CVE CVE-2023-52768 https://www.cve.org/CVERecord?id=CVE-2023-52768 Référence CVE CVE-2023-52769 https://www.cve.org/CVERecord?id=CVE-2023-52769 Référence CVE CVE-2023-52771 https://www.cve.org/CVERecord?id=CVE-2023-52771 Référence CVE CVE-2023-52772 https://www.cve.org/CVERecord?id=CVE-2023-52772 Référence CVE CVE-2023-52773 https://www.cve.org/CVERecord?id=CVE-2023-52773 Référence CVE CVE-2023-52774 https://www.cve.org/CVERecord?id=CVE-2023-52774 Référence CVE CVE-2023-52775 https://www.cve.org/CVERecord?id=CVE-2023-52775 Référence CVE CVE-2023-52776 https://www.cve.org/CVERecord?id=CVE-2023-52776 Référence CVE CVE-2023-52777 https://www.cve.org/CVERecord?id=CVE-2023-52777 Référence CVE CVE-2023-52780 https://www.cve.org/CVERecord?id=CVE-2023-52780 Référence CVE CVE-2023-52781 https://www.cve.org/CVERecord?id=CVE-2023-52781 Référence CVE CVE-2023-52782 https://www.cve.org/CVERecord?id=CVE-2023-52782 Référence CVE CVE-2023-52783 https://www.cve.org/CVERecord?id=CVE-2023-52783 Référence CVE CVE-2023-52784 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2023-52762 Référence CVE CVE-2023-52763 https://www.cve.org/CVERecord?id=CVE-2023-52763 Référence CVE CVE-2023-52764 https://www.cve.org/CVERecord?id=CVE-2023-52764 Référence CVE CVE-2023-52765 https://www.cve.org/CVERecord?id=CVE-2023-52765 Référence CVE CVE-2023-52766 https://www.cve.org/CVERecord?id=CVE-2023-52766 Référence CVE CVE-2023-52767 https://www.cve.org/CVERecord?id=CVE-2023-52767 Référence CVE CVE-2023-52768 https://www.cve.org/CVERecord?id=CVE-2023-52768 Référence CVE CVE-2023-52769 https://www.cve.org/CVERecord?id=CVE-2023-52769 Référence CVE CVE-2023-52773 https://www.cve.org/CVERecord?id=CVE-2023-52773 Référence CVE CVE-2023-52774 https://www.cve.org/CVERecord?id=CVE-2023-52774 Référence CVE CVE-2023-52775 https://www.cve.org/CVERecord?id=CVE-2023-52775 Référence CVE CVE-2023-52776 https://www.cve.org/CVERecord?id=CVE-2023-52776 Référence CVE CVE-2023-52777 https://www.cve.org/CVERecord?id=CVE-2023-52777 Référence CVE CVE-2023-52780 https://www.cve.org/CVERecord?id=CVE-2023-52780 Référence CVE CVE-2023-52781 https://www.cve.org/CVERecord?id=CVE-2023-52781 Référence CVE CVE-2023-52782 https://www.cve.org/CVERecord?id=CVE-2023-52782 Référence CVE CVE-2023-52783 https://www.cve.org/CVERecord?id=CVE-2023-52783 Référence CVE CVE-2023-52784 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2023-52762 Référence CVE CVE-2023-52763 https://www.cve.org/CVERecord?id=CVE-2023-52763 Référence CVE CVE-2023-52764 https://www.cve.org/CVERecord?id=CVE-2023-52764 Référence CVE CVE-2023-52765 https://www.cve.org/CVERecord?id=CVE-2023-52765 Référence CVE CVE-2023-52766 https://www.cve.org/CVERecord?id=CVE-2023-52766 Référence CVE CVE-2023-52767 https://www.cve.org/CVERecord?id=CVE-2023-52767 Référence CVE CVE-2023-52768 https://www.cve.org/CVERecord?id=CVE-2023-52768 Référence CVE CVE-2023-52769 https://www.cve.org/CVERecord?id=CVE-2023-52769 Référence CVE CVE-2023-52773 https://www.cve.org/CVERecord?id=CVE-2023-52773 Référence CVE CVE-2023-52774 https://www.cve.org/CVERecord?id=CVE-2023-52774 Référence CVE CVE-2023-52776 https://www.cve.org/CVERecord?id=CVE-2023-52776 Référence CVE CVE-2023-52777 https://www.cve.org/CVERecord?id=CVE-2023-52777 Référence CVE CVE-2023-52780 https://www.cve.org/CVERecord?id=CVE-2023-52780 Référence CVE CVE-2023-52781 https://www.cve.org/CVERecord?id=CVE-2023-52781 Référence CVE CVE-2023-52782 https://www.cve.org/CVERecord?id=CVE-2023-52782 Référence CVE CVE-2023-52783 https://www.cve.org/CVERecord?id=CVE-2023-52783 Référence CVE CVE-2023-52784 https://www.cve.org/CVERecord?id=CVE-2023-52784 Référence CVE CVE-2023-52786 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2023-52756 Référence CVE CVE-2023-52757 https://www.cve.org/CVERecord?id=CVE-2023-52757 Référence CVE CVE-2023-52759 https://www.cve.org/CVERecord?id=CVE-2023-52759 Référence CVE CVE-2023-52763 https://www.cve.org/CVERecord?id=CVE-2023-52763 Référence CVE CVE-2023-52764 https://www.cve.org/CVERecord?id=CVE-2023-52764 Référence CVE CVE-2023-52766 https://www.cve.org/CVERecord?id=CVE-2023-52766 Référence CVE CVE-2023-52771 https://www.cve.org/CVERecord?id=CVE-2023-52771 Référence CVE CVE-2023-52772 https://www.cve.org/CVERecord?id=CVE-2023-52772 Référence CVE CVE-2023-52773 https://www.cve.org/CVERecord?id=CVE-2023-52773 Référence CVE CVE-2023-52774 https://www.cve.org/CVERecord?id=CVE-2023-52774 Référence CVE CVE-2023-52777 https://www.cve.org/CVERecord?id=CVE-2023-52777 Référence CVE CVE-2023-52781 https://www.cve.org/CVERecord?id=CVE-2023-52781 Référence CVE CVE-2023-52788 https://www.cve.org/CVERecord?id=CVE-2023-52788 Référence CVE CVE-2023-52789 https://www.cve.org/CVERecord?id=CVE-2023-52789 Référence CVE CVE-2023-52791 https://www.cve.org/CVERecord?id=CVE-2023-52791 Référence CVE CVE-2023-52795 https://www.cve.org/CVERecord?id=CVE-2023-52795 Référence CVE CVE-2023-52796 https://www.cve.org/CVERecord?id=CVE-2023-52796 Référence CVE CVE-2023-52798 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2023-52753 Référence CVE CVE-2023-52754 https://www.cve.org/CVERecord?id=CVE-2023-52754 Référence CVE CVE-2023-52756 https://www.cve.org/CVERecord?id=CVE-2023-52756 Référence CVE CVE-2023-52757 https://www.cve.org/CVERecord?id=CVE-2023-52757 Référence CVE CVE-2023-52759 https://www.cve.org/CVERecord?id=CVE-2023-52759 Référence CVE CVE-2023-52763 https://www.cve.org/CVERecord?id=CVE-2023-52763 Référence CVE CVE-2023-52764 https://www.cve.org/CVERecord?id=CVE-2023-52764 Référence CVE CVE-2023-52766 https://www.cve.org/CVERecord?id=CVE-2023-52766 Référence CVE CVE-2023-52773 https://www.cve.org/CVERecord?id=CVE-2023-52773 Référence CVE CVE-2023-52774 https://www.cve.org/CVERecord?id=CVE-2023-52774 Référence CVE CVE-2023-52777 https://www.cve.org/CVERecord?id=CVE-2023-52777 Référence CVE CVE-2023-52781 https://www.cve.org/CVERecord?id=CVE-2023-52781 Référence CVE CVE-2023-52788 https://www.cve.org/CVERecord?id=CVE-2023-52788 Référence CVE CVE-2023-52789 https://www.cve.org/CVERecord?id=CVE-2023-52789 Référence CVE CVE-2023-52791 https://www.cve.org/CVERecord?id=CVE-2023-52791 Référence CVE CVE-2023-52795 https://www.cve.org/CVERecord?id=CVE-2023-52795 Référence CVE CVE-2023-52796 https://www.cve.org/CVERecord?id=CVE-2023-52796 Référence CVE CVE-2023-52798 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2023-029775Linux の Linux Kernel における NULL ポインタデリファレンスに関する脆弱性

Linux の Linux Kernel には、NULL ポインタデリファレンスに関する脆弱性が存在します。

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: < 3.1, 4.14.332 ≤ 4.14.*, 4.19.301 ≤ 4.19.*, 5.4.263 ≤ 5.4.*, 5.10.203 ≤ 5.10.*, 5.15.141 ≤ 5.15.*, 6.1.65 ≤ 6.1.*, 6.6.4 ≤ 6.6.*, 6.7 ≤ *
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 21 May 2024 · Last source change 11 May 2026, 19:32 UTC · CWE-476 · NULL Pointer Dereference

CVE recordCVE.org · 5.2
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-59491
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
NVD statusNVD enriched

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-2023-59491↗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-2023-52774 · cve.blacktree.nl