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

Possible deadlock in Linux kernel event handling

Linux · Linux

4.9MediumCVSS 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:Medium, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.89% 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: 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.5.8-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.64-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.5.8-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.5.8-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2023-34324 · CSAF 2.0 · revision 37 · interimSUSE Product Security TeamCVE-2023-34324
80 known affected

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

  • xen as component of SUSE Linux Enterprise Desktop 15 SP4
  • xen-libs as component of SUSE Linux Enterprise Desktop 15 SP4
  • xen-tools-domU as component of SUSE Linux Enterprise Desktop 15 SP4
  • xen as component of SUSE Linux Enterprise Desktop 15 SP5
  • xen-libs as component of SUSE Linux Enterprise Desktop 15 SP5
  • xen-tools-domU as component of SUSE Linux Enterprise Desktop 15 SP5
  • xen as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • xen-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • xen-libs as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • xen-tools as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • xen-tools-domU as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • xen-tools-xendomains-wait-disk as component of SUSE Linux Enterprise High Performance Computing 15 SP4
Summary
Closing of an event channel in the Linux kernel can result in a deadlock. This happens when the close is being performed in parallel to an unrelated Xen console action and the handling of a Xen console interrupt in an unprivileged guest. The closing of an event channel is e.g. triggered by removal of a paravirtual device on the other side. As this action will cause console messages to be issued on the other side quite often, the chance of triggering the deadlock is not neglectable. Note that 32-bit Arm-guests are not affected, as the 32-bit Linux kernel on Arm doesn't use queued-RW-locks, which are required to trigger the issue (on Arm32 a waiting writer doesn't block further readers to get the lock).
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-38405

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

Closing of an event channel in the Linux kernel can result in a deadlock. This happens when the close is being performed in parallel to an unrelated Xen console action and the handling of a Xen console interrupt in an unprivileged guest. The closing of an event channel is e.g. triggered by removal of a paravirtual device on the other side. As this action will cause console messages to be issued on the other side quite often, the chance of triggering the deadlock is not neglectable. Note that 32-bit Arm-guests are not affected, as the 32-bit Linux kernel on Arm doesn't use queued-RW-locks, which are required to trigger the issue (on Arm32 a waiting writer doesn't block further readers to get the lock).

What

Closing of an event channel in the Linux kernel can result in a deadlock. This happens when the close is being performed in parallel to an unrelated Xen console action and the handling of a Xen console interrupt in an unprivileged guest. The closing of an event channel is e.g. triggered by removal of a paravirtual device on the other side. As this action will cause console messages to be issued on the other side quite often, the chance of triggering the deadlock is not neglectable. Note that 32-bit Arm-guests are not affected, as the 32-bit Linux kernel on Arm doesn't use queued-RW-locks, which are required to trigger the issue (on Arm32 a waiting writer doesn't block further readers to get the lock).

Why

The product does not properly control the allocation and maintenance of a limited resource.

How

An attacker operating through a network path may attempt exploitation with elevated privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

Closing of an event channel in the Linux kernel can result in a deadlock. This happens when the close is being performed in parallel to an unrelated Xen console action and the handling of a Xen console interrupt in an unprivileged guest. The closing of an event channel is e.g. triggered by removal of a paravirtual device on the other side. As this action will cause console messages to be issued on the other side quite often, the chance of triggering the deadlock is not neglectable. Note that 32-bit Arm-guests are not affected, as the 32-bit Linux kernel on Arm doesn't use queued-RW-locks, which are required to trigger the issue (on Arm32 a waiting writer doesn't block further readers to get the lock).

Why

The product does not properly control the allocation and maintenance of a limited resource.

How

An attacker operating through a network path may attempt exploitation with elevated 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
a network path → Uncontrolled Resource Consumption → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
High: elevated access 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-400 ↗

CWE-400: Uncontrolled Resource Consumption. The product does not properly control the allocation and maintenance of a limited resource.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:H/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.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRHighPrivileges required: The attacker needs elevated or administrative 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
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.
NetworkCWE-400
A

Official authority intelligence

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

BSI · German · WID-SEC-2023-2617Xen: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Xen ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen, beliebigen Code auszuführen, vertrauliche Informationen offenzulegen oder seine Privilegien zu erweitern.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20240110Security Bulletin 10 Jan 2024

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 10 Jan 2024, published on 10 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-0178Multiples 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 élévation de privilèges, un déni de service à distance et une exécution de code arbitraire.

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

De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu . Elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, un déni de service à distance et une atteinte à la confidentialité des données.

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

urité Ubuntu USN-6626-2 du 14 février 2024 https://ubuntu.com/security/notices/USN-6626-2 Bulletin de sécurité Ubuntu USN-6628-2 du 15 février 2024 https://ubuntu.com/security/notices/USN-6628-2 Bulletin de sécurité Ubuntu USN-6635-1 du 14 février 2024 https://ubuntu.com/security/notices/USN-6635-1 Bulletin de sécurité Ubuntu USN-6639-1 du 15 février 2024 https://ubuntu.com/security/notices/USN-6639-1 Référence CVE CVE-2023-32250 https://www.cve.org/CVERecord?id=CVE-2023-32250 Référence CVE CVE-2023-32252 https://www.cve.org/CVERecord?id=CVE-2023-32252 Référence CVE CVE-2023-32257 https://www.cve.org/CVERecord?id=CVE-2023-32257 Référence CVE CVE-2023-34324 https://www.cve.org/CVERecord?id=CVE-2023-34324 Référence CVE CVE-2023-35827 https://www.cve.org/CVERecord?id=CVE-2023-35827 Référence CVE CVE-2023-37453 https://www.cve.org/CVERecord?id=CVE-2023-37453 Référence CVE CVE-2023-39189 https://www.cve.org/CVERecord?id=CVE-2023-39189 Référence CVE CVE-2023-39192 https://www.cve.org/CVERecord?id=CVE-2023-39192 Référence CVE CVE-2023-39193 https://www.cve.org/CVERecord?id=CVE-2023-39193 Référence CVE CVE-2023-42754 https://www.cve.org/CVERecord?id=CVE-2023-42754 Référence CVE CVE-2023-45863 https://www.cve.org/CVERecord?id=CVE-2023-45863 Référence CVE CVE-2023-46343 https://www.cve.org/CVERecord?id=

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

De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu . Elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, un déni de service à distance et une atteinte à la confidentialité des données.

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

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

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

SU-2023:4378-1 du 06 novembre 2023 https://www.suse.com/support/update/announcement/2023/suse-su-20234378-1/ Référence CVE CVE-2023-1192 https://www.cve.org/CVERecord?id=CVE-2023-1192 Référence CVE CVE-2023-1206 https://www.cve.org/CVERecord?id=CVE-2023-1206 Référence CVE CVE-2023-1859 https://www.cve.org/CVERecord?id=CVE-2023-1859 Référence CVE CVE-2023-2163 https://www.cve.org/CVERecord?id=CVE-2023-2163 Référence CVE CVE-2023-2177 https://www.cve.org/CVERecord?id=CVE-2023-2177 Référence CVE CVE-2023-31085 https://www.cve.org/CVERecord?id=CVE-2023-31085 Référence CVE CVE-2023-3111 https://www.cve.org/CVERecord?id=CVE-2023-3111 Référence CVE CVE-2023-34324 https://www.cve.org/CVERecord?id=CVE-2023-34324 Référence CVE CVE-2023-3777 https://www.cve.org/CVERecord?id=CVE-2023-3777 Référence CVE CVE-2023-39189 https://www.cve.org/CVERecord?id=CVE-2023-39189 Référence CVE CVE-2023-39191 https://www.cve.org/CVERecord?id=CVE-2023-39191 Référence CVE CVE-2023-39192 https://www.cve.org/CVERecord?id=CVE-2023-39192 Référence CVE CVE-2023-39193 https://www.cve.org/CVERecord?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-4155 https://www.cve.org/CVERecord?id=CVE-2023-4155 Référence CVE CVE-2023-42753 https://www.cve.org/CVERecord?id=CVE-

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

ve.org/CVERecord?id=CVE-2023-1206 Référence CVE CVE-2023-1281 https://www.cve.org/CVERecord?id=CVE-2023-1281 Référence CVE CVE-2023-1829 https://www.cve.org/CVERecord?id=CVE-2023-1829 Référence CVE CVE-2023-1859 https://www.cve.org/CVERecord?id=CVE-2023-1859 Référence CVE CVE-2023-2163 https://www.cve.org/CVERecord?id=CVE-2023-2163 Référence CVE CVE-2023-2860 https://www.cve.org/CVERecord?id=CVE-2023-2860 Référence CVE CVE-2023-31085 https://www.cve.org/CVERecord?id=CVE-2023-31085 Référence CVE CVE-2023-3111 https://www.cve.org/CVERecord?id=CVE-2023-3111 Référence CVE CVE-2023-3390 https://www.cve.org/CVERecord?id=CVE-2023-3390 Référence CVE CVE-2023-34324 https://www.cve.org/CVERecord?id=CVE-2023-34324 Référence CVE CVE-2023-3777 https://www.cve.org/CVERecord?id=CVE-2023-3777 Référence CVE CVE-2023-39189 https://www.cve.org/CVERecord?id=CVE-2023-39189 Référence CVE CVE-2023-39191 https://www.cve.org/CVERecord?id=CVE-2023-39191 Référence CVE CVE-2023-39192 https://www.cve.org/CVERecord?id=CVE-2023-39192 Référence CVE CVE-2023-39193 https://www.cve.org/CVERecord?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-4004 https://www.cve.org/CVERecord?id=CVE-2023-4004 Référence CVE CVE-2023-40283 https://www.cve.org/CVERecord?id=CVE-

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

ecord?id=CVE-2023-20569 Référence CVE CVE-2023-20588 https://www.cve.org/CVERecord?id=CVE-2023-20588 Référence CVE CVE-2023-21264 https://www.cve.org/CVERecord?id=CVE-2023-21264 Référence CVE CVE-2023-2156 https://www.cve.org/CVERecord?id=CVE-2023-2156 Référence CVE CVE-2023-31083 https://www.cve.org/CVERecord?id=CVE-2023-31083 Référence CVE CVE-2023-31085 https://www.cve.org/CVERecord?id=CVE-2023-31085 Référence CVE CVE-2023-31436 https://www.cve.org/CVERecord?id=CVE-2023-31436 Référence CVE CVE-2023-3212 https://www.cve.org/CVERecord?id=CVE-2023-3212 Référence CVE CVE-2023-34319 https://www.cve.org/CVERecord?id=CVE-2023-34319 Référence CVE CVE-2023-34324 https://www.cve.org/CVERecord?id=CVE-2023-34324 Référence CVE CVE-2023-35001 https://www.cve.org/CVERecord?id=CVE-2023-35001 Référence CVE CVE-2023-3772 https://www.cve.org/CVERecord?id=CVE-2023-3772 Référence CVE CVE-2023-38427 https://www.cve.org/CVERecord?id=CVE-2023-38427 Référence CVE CVE-2023-38430 https://www.cve.org/CVERecord?id=CVE-2023-38430 Référence CVE CVE-2023-38431 https://www.cve.org/CVERecord?id=CVE-2023-38431 Référence CVE CVE-2023-38432 https://www.cve.org/CVERecord?id=CVE-2023-38432 Référence CVE CVE-2023-3863 https://www.cve.org/CVERecord?id=CVE-2023-3863 Référence CVE CVE-2023-3865 https://www.cve.org/CVERecord?id=CVE-2

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-0834Multiples vulnérabilités dans Xen

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

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-0823Multiples vulnérabilités dans les produits Citrix

De multiples vulnérabilités ont été découvertes dans les produits Citrix. Elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, un déni de service à distance et une atteinte à la confidentialité des données.

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2023-024902Linux の 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. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 5 Jan 2024 · Last source change 4 Nov 2025, 19:16 UTC · CWE-400 · Uncontrolled Resource Consumption

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-38405
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCISA ADP
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
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-34324 · cve.blacktree.nl