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

ocfs2: Avoid touching renamed directory if parent does not change

Linux · Linux

7.8HighCVSS 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 5 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.17% 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: 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 findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

4 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.7.7-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.7.7-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.7.7-1Debian Security Tracker ↗Source updated 6 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-52590 · CSAF 2.0 · revision 48 · interimSUSE Product Security TeamCVE-2023-52590
133 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 SP2
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • 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
Summary
In the Linux kernel, the following vulnerability has been resolved: ocfs2: Avoid touching renamed directory if parent does not change The VFS will not be locking moved directory if its parent does not change. Change ocfs2 rename code to avoid touching renamed directory if its parent does not change as without locking that can corrupt the filesystem.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2023-52590 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: ocfs2: Avoid touching renamed directory if parent does not change
198 known not affected

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

  • kernel as a component of Red Hat Enterprise Linux 6
  • kernel-abi-whitelists as a component of Red Hat Enterprise Linux 6
  • kernel-bootwrapper as a component of Red Hat Enterprise Linux 6
  • kernel-debug as a component of Red Hat Enterprise Linux 6
  • kernel-debug-devel as a component of Red Hat Enterprise Linux 6
  • kernel-devel as a component of Red Hat Enterprise Linux 6
  • kernel-doc as a component of Red Hat Enterprise Linux 6
  • kernel-firmware as a component of Red Hat Enterprise Linux 6
  • kernel-headers as a component of Red Hat Enterprise Linux 6
  • kernel-kdump as a component of Red Hat Enterprise Linux 6
  • kernel-kdump-devel as a component of Red Hat Enterprise Linux 6
  • kernel.src as a component of Red Hat Enterprise Linux 6
Summary
This Linux kernel bug affects the Oracle Cluster File System v2 (OCFS2). The issue arises during directory rename operations when a moved directory's parent remains the same, a scenario where the Virtual File System (VFS) does not natively lock the directory. Because the OCFS2 code was previously touching the renamed directory without ensuring it was properly locked, this flaw could potentially be triggered by a local user to cause filesystem corruption. Patched kernel versions resolve the vulnerability by updating the OCFS2 rename code to avoid touching the renamed directory if its parent does not change, preventing the unsafe, lockless operations that could corrupt data on disk.
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-57214

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

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

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: ocfs2: Avoid touching renamed directory if parent does not change The VFS will not be locking moved directory if its parent does not change. Change ocfs2 rename code to avoid touching renamed directory if its parent does not change as without locking that can corrupt the filesystem.

What

In the Linux kernel, the following vulnerability has been resolved: ocfs2: Avoid touching renamed directory if parent does not change The VFS will not be locking moved directory if its parent does not change. Change ocfs2 rename code to avoid touching renamed directory if its parent does not change as without locking that can corrupt the filesystem.

Why

The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

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: ocfs2: Avoid touching renamed directory if parent does not change The VFS will not be locking moved directory if its parent does not change. Change ocfs2 rename code to avoid touching renamed directory if its parent does not change as without locking that can corrupt the filesystem.

Why

The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

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 → Improper Locking → 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-667 ↗

CWE-667: Improper Locking. The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

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: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.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-667
A

Official authority intelligence

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

BSI · German · WID-SEC-2025-0612IBM Security Guardium: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM Security Guardium ausnutzen, um Sicherheitsbeschränkungen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, beliebigen Code auszuführen und vertrauliche Informationen preiszugeben.

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

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

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

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

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0326Multiples vulnérabilités dans les produits VMware

d?id=CVE-2023-52481 Référence CVE CVE-2023-52485 https://www.cve.org/CVERecord?id=CVE-2023-52485 Référence CVE CVE-2023-52508 https://www.cve.org/CVERecord?id=CVE-2023-52508 Référence CVE CVE-2023-52561 https://www.cve.org/CVERecord?id=CVE-2023-52561 Référence CVE CVE-2023-52569 https://www.cve.org/CVERecord?id=CVE-2023-52569 Référence CVE CVE-2023-52576 https://www.cve.org/CVERecord?id=CVE-2023-52576 Référence CVE CVE-2023-52582 https://www.cve.org/CVERecord?id=CVE-2023-52582 Référence CVE CVE-2023-52586 https://www.cve.org/CVERecord?id=CVE-2023-52586 Référence CVE CVE-2023-52589 https://www.cve.org/CVERecord?id=CVE-2023-52589 Référence CVE CVE-2023-52590 https://www.cve.org/CVERecord?id=CVE-2023-52590 Référence CVE CVE-2023-52591 https://www.cve.org/CVERecord?id=CVE-2023-52591 Référence CVE CVE-2023-52624 https://www.cve.org/CVERecord?id=CVE-2023-52624 Référence CVE CVE-2023-52625 https://www.cve.org/CVERecord?id=CVE-2023-52625 Référence CVE CVE-2023-52632 https://www.cve.org/CVERecord?id=CVE-2023-52632 Référence CVE CVE-2023-52634 https://www.cve.org/CVERecord?id=CVE-2023-52634 Référence CVE CVE-2023-52648 https://www.cve.org/CVERecord?id=CVE-2023-52648 Référence CVE CVE-2023-52653 https://www.cve.org/CVERecord?id=CVE-2023-52653 Référence CVE CVE-2023-52657 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0316Multiples vulnérabilités dans les produits VMware

d?id=CVE-2023-52481 Référence CVE CVE-2023-52485 https://www.cve.org/CVERecord?id=CVE-2023-52485 Référence CVE CVE-2023-52508 https://www.cve.org/CVERecord?id=CVE-2023-52508 Référence CVE CVE-2023-52561 https://www.cve.org/CVERecord?id=CVE-2023-52561 Référence CVE CVE-2023-52569 https://www.cve.org/CVERecord?id=CVE-2023-52569 Référence CVE CVE-2023-52576 https://www.cve.org/CVERecord?id=CVE-2023-52576 Référence CVE CVE-2023-52582 https://www.cve.org/CVERecord?id=CVE-2023-52582 Référence CVE CVE-2023-52586 https://www.cve.org/CVERecord?id=CVE-2023-52586 Référence CVE CVE-2023-52589 https://www.cve.org/CVERecord?id=CVE-2023-52589 Référence CVE CVE-2023-52590 https://www.cve.org/CVERecord?id=CVE-2023-52590 Référence CVE CVE-2023-52591 https://www.cve.org/CVERecord?id=CVE-2023-52591 Référence CVE CVE-2023-52624 https://www.cve.org/CVERecord?id=CVE-2023-52624 Référence CVE CVE-2023-52625 https://www.cve.org/CVERecord?id=CVE-2023-52625 Référence CVE CVE-2023-52632 https://www.cve.org/CVERecord?id=CVE-2023-52632 Référence CVE CVE-2023-52634 https://www.cve.org/CVERecord?id=CVE-2023-52634 Référence CVE CVE-2023-52648 https://www.cve.org/CVERecord?id=CVE-2023-52648 Référence CVE CVE-2023-52653 https://www.cve.org/CVERecord?id=CVE-2023-52653 Référence CVE CVE-2023-52657 https://www.cve.org/CVERecord?id=

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

rd?id=CVE-2023-5115 Référence CVE CVE-2023-52425 https://www.cve.org/CVERecord?id=CVE-2023-52425 Référence CVE CVE-2023-52451 https://www.cve.org/CVERecord?id=CVE-2023-52451 Référence CVE CVE-2023-52463 https://www.cve.org/CVERecord?id=CVE-2023-52463 Référence CVE CVE-2023-52469 https://www.cve.org/CVERecord?id=CVE-2023-52469 Référence CVE CVE-2023-52471 https://www.cve.org/CVERecord?id=CVE-2023-52471 Référence CVE CVE-2023-52486 https://www.cve.org/CVERecord?id=CVE-2023-52486 Référence CVE CVE-2023-52530 https://www.cve.org/CVERecord?id=CVE-2023-52530 Référence CVE CVE-2023-52584 https://www.cve.org/CVERecord?id=CVE-2023-52584 Référence CVE CVE-2023-52590 https://www.cve.org/CVERecord?id=CVE-2023-52590 Référence CVE CVE-2023-52591 https://www.cve.org/CVERecord?id=CVE-2023-52591 Référence CVE CVE-2023-52596 https://www.cve.org/CVERecord?id=CVE-2023-52596 Référence CVE CVE-2023-52599 https://www.cve.org/CVERecord?id=CVE-2023-52599 Référence CVE CVE-2023-52600 https://www.cve.org/CVERecord?id=CVE-2023-52600 Référence CVE CVE-2023-52608 https://www.cve.org/CVERecord?id=CVE-2023-52608 Référence CVE CVE-2023-52609 https://www.cve.org/CVERecord?id=CVE-2023-52609 Référence CVE CVE-2023-52619 https://www.cve.org/CVERecord?id=CVE-2023-52619 Référence CVE CVE-2023-52622 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2023-52486 Référence CVE CVE-2023-52488 https://www.cve.org/CVERecord?id=CVE-2023-52488 Référence CVE CVE-2023-52509 https://www.cve.org/CVERecord?id=CVE-2023-52509 Référence CVE CVE-2023-52515 https://www.cve.org/CVERecord?id=CVE-2023-52515 Référence CVE CVE-2023-52524 https://www.cve.org/CVERecord?id=CVE-2023-52524 Référence CVE CVE-2023-52528 https://www.cve.org/CVERecord?id=CVE-2023-52528 Référence CVE CVE-2023-52575 https://www.cve.org/CVERecord?id=CVE-2023-52575 Référence CVE CVE-2023-52583 https://www.cve.org/CVERecord?id=CVE-2023-52583 Référence CVE CVE-2023-52587 https://www.cve.org/CVERecord?id=CVE-2023-52587 Référence CVE CVE-2023-52590 https://www.cve.org/CVERecord?id=CVE-2023-52590 Référence CVE CVE-2023-52591 https://www.cve.org/CVERecord?id=CVE-2023-52591 Référence CVE CVE-2023-52595 https://www.cve.org/CVERecord?id=CVE-2023-52595 Référence CVE CVE-2023-52598 https://www.cve.org/CVERecord?id=CVE-2023-52598 Référence CVE CVE-2023-52607 https://www.cve.org/CVERecord?id=CVE-2023-52607 Référence CVE CVE-2023-52614 https://www.cve.org/CVERecord?id=CVE-2023-52614 Référence CVE CVE-2023-52620 https://www.cve.org/CVERecord?id=CVE-2023-52620 Référence CVE CVE-2023-52628 https://www.cve.org/CVERecord?id=CVE-2023-52628 Référence CVE CVE-2023-52635 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2023-52488 Référence CVE CVE-2023-52502 https://www.cve.org/CVERecord?id=CVE-2023-52502 Référence CVE CVE-2023-52509 https://www.cve.org/CVERecord?id=CVE-2023-52509 Référence CVE CVE-2023-52515 https://www.cve.org/CVERecord?id=CVE-2023-52515 Référence CVE CVE-2023-52524 https://www.cve.org/CVERecord?id=CVE-2023-52524 Référence CVE CVE-2023-52528 https://www.cve.org/CVERecord?id=CVE-2023-52528 Référence CVE CVE-2023-52575 https://www.cve.org/CVERecord?id=CVE-2023-52575 Référence CVE CVE-2023-52583 https://www.cve.org/CVERecord?id=CVE-2023-52583 Référence CVE CVE-2023-52587 https://www.cve.org/CVERecord?id=CVE-2023-52587 Référence CVE CVE-2023-52590 https://www.cve.org/CVERecord?id=CVE-2023-52590 Référence CVE CVE-2023-52591 https://www.cve.org/CVERecord?id=CVE-2023-52591 Référence CVE CVE-2023-52595 https://www.cve.org/CVERecord?id=CVE-2023-52595 Référence CVE CVE-2023-52598 https://www.cve.org/CVERecord?id=CVE-2023-52598 Référence CVE CVE-2023-52607 https://www.cve.org/CVERecord?id=CVE-2023-52607 Référence CVE CVE-2023-52614 https://www.cve.org/CVERecord?id=CVE-2023-52614 Référence CVE CVE-2023-52620 https://www.cve.org/CVERecord?id=CVE-2023-52620 Référence CVE CVE-2023-52628 https://www.cve.org/CVERecord?id=CVE-2023-52628 Référence CVE CVE-2023-52635 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2023-52515 Référence CVE CVE-2023-52524 https://www.cve.org/CVERecord?id=CVE-2023-52524 Référence CVE CVE-2023-52528 https://www.cve.org/CVERecord?id=CVE-2023-52528 Référence CVE CVE-2023-52561 https://www.cve.org/CVERecord?id=CVE-2023-52561 Référence CVE CVE-2023-52575 https://www.cve.org/CVERecord?id=CVE-2023-52575 Référence CVE CVE-2023-52583 https://www.cve.org/CVERecord?id=CVE-2023-52583 Référence CVE CVE-2023-52585 https://www.cve.org/CVERecord?id=CVE-2023-52585 Référence CVE CVE-2023-52587 https://www.cve.org/CVERecord?id=CVE-2023-52587 Référence CVE CVE-2023-52589 https://www.cve.org/CVERecord?id=CVE-2023-52589 Référence CVE CVE-2023-52590 https://www.cve.org/CVERecord?id=CVE-2023-52590 Référence CVE CVE-2023-52591 https://www.cve.org/CVERecord?id=CVE-2023-52591 Référence CVE CVE-2023-52593 https://www.cve.org/CVERecord?id=CVE-2023-52593 Référence CVE CVE-2023-52595 https://www.cve.org/CVERecord?id=CVE-2023-52595 Référence CVE CVE-2023-52598 https://www.cve.org/CVERecord?id=CVE-2023-52598 Référence CVE CVE-2023-52607 https://www.cve.org/CVERecord?id=CVE-2023-52607 Référence CVE CVE-2023-52614 https://www.cve.org/CVERecord?id=CVE-2023-52614 Référence CVE CVE-2023-52616 https://www.cve.org/CVERecord?id=CVE-2023-52616 Référence CVE CVE-2023-52620 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2023-52567 Référence CVE CVE-2023-52569 https://www.cve.org/CVERecord?id=CVE-2023-52569 Référence CVE CVE-2023-52572 https://www.cve.org/CVERecord?id=CVE-2023-52572 Référence CVE CVE-2023-52574 https://www.cve.org/CVERecord?id=CVE-2023-52574 Référence CVE CVE-2023-52575 https://www.cve.org/CVERecord?id=CVE-2023-52575 Référence CVE CVE-2023-52576 https://www.cve.org/CVERecord?id=CVE-2023-52576 Référence CVE CVE-2023-52582 https://www.cve.org/CVERecord?id=CVE-2023-52582 Référence CVE CVE-2023-52583 https://www.cve.org/CVERecord?id=CVE-2023-52583 Référence CVE CVE-2023-52587 https://www.cve.org/CVERecord?id=CVE-2023-52587 Référence CVE CVE-2023-52590 https://www.cve.org/CVERecord?id=CVE-2023-52590 Référence CVE CVE-2023-52591 https://www.cve.org/CVERecord?id=CVE-2023-52591 Référence CVE CVE-2023-52594 https://www.cve.org/CVERecord?id=CVE-2023-52594 Référence CVE CVE-2023-52595 https://www.cve.org/CVERecord?id=CVE-2023-52595 Référence CVE CVE-2023-52597 https://www.cve.org/CVERecord?id=CVE-2023-52597 Référence CVE CVE-2023-52598 https://www.cve.org/CVERecord?id=CVE-2023-52598 Référence CVE CVE-2023-52599 https://www.cve.org/CVERecord?id=CVE-2023-52599 Référence CVE CVE-2023-52600 https://www.cve.org/CVERecord?id=CVE-2023-52600 Référence CVE CVE-2023-52601 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2023-028149Linux の Linux Kernel におけるリソースのロックに関する脆弱性

Linux の Linux Kernel には、リソースのロックに関する脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 2.6.16, 6.7.4 ≤ 6.7.*, 6.8 ≤ *
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 6 Mar 2024 · Last source change 5 Aug 2026, 09:10 UTC · CWE-667 · Improper Locking

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

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2023-57214↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor 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-52590 · cve.blacktree.nl