LiveActive security incident?Get immediate response
CVE Record

CVE-2023-52591: reiserfs: Avoid touching renamed directory if parent does not change

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

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This Linux kernel ReiserFS flaw can let a local low-privileged user trigger unsafe rename handling that may corrupt the filesystem. Business urgency is highest where ReiserFS is still mounted on affected kernels, especially on systems with local users, shared hosting, or untrusted workloads.

Executive priority

Treat as a targeted high-priority Linux maintenance item, not a broad remote emergency. Prioritize patching systems that actually use ReiserFS and allow local user or workload access.

Technical view

ReiserFS rename logic could touch a renamed directory when its parent did not change. The VFS does not lock the moved directory in that case, so ReiserFS could operate without expected locking and corrupt filesystem state. Supplied CVSS is 7.8, local, low-privilege, no user interaction, with high CIA impact.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions with ReiserFS in use. The attack path is local and requires low privileges, so internet-facing network exposure alone is not enough evidence of reachability.

Exploitation context

The bundle does not show CISA KEV listing or any cited evidence of active exploitation. The CVSS vector indicates local access with low privileges and no user interaction, so risk depends on whether untrusted users or workloads can access affected hosts.

Researcher notes

Evidence is limited to the CVE record data and Linux stable commit references. The core condition is a same-parent directory rename path where VFS locking expectations differ from ReiserFS behavior. No exploit details or independent exploitation reports are provided in the bundle.

Mitigation direction

  • Identify Linux hosts that mount or support ReiserFS filesystems.
  • Update affected kernels to vendor builds containing the referenced stable fixes.
  • Prioritize multi-user systems and hosts running untrusted local workloads.
  • Check Linux distribution advisories for exact fixed package versions.
  • Restrict local shell or workload access where patching is delayed.

Validation and detection

  • Inventory kernel versions and ReiserFS usage across Linux assets.
  • Confirm whether deployed kernels include the referenced stable commits.
  • Review package changelogs from the relevant Linux distribution vendor.
  • Check for systems with local untrusted users or shared workloads.
  • After updating, verify hosts rebooted into the fixed kernel.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-52591 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
2ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2023-52591Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2unaffected
LinuxLinux2.6.12, 0, 6.6.16, 6.7.4, 6.8affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.