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.
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.
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.
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.
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.