Linux Kernel up to 6.6.15/6.7.3 ReiserFS privilege escalation

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.5 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as problematic has been found in Linux Kernel up to 6.6.15/6.7.3. This vulnerability affects unknown code of the component ReiserFS. Executing a manipulation can lead to an unknown weakness. The identification of this vulnerability is CVE-2023-52591. There is no exploit available. The affected component should be upgraded.
Details
A vulnerability has been found in Linux Kernel up to 6.6.15/6.7.3 (Operating System) and classified as problematic. This vulnerability affects an unknown part of the component ReiserFS. The impact remains unknown. CVE summarizes:
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.
The weakness was shared 03/06/2024. The advisory is available at git.kernel.org. This vulnerability was named CVE-2023-52591 since 03/02/2024. The technical details are unknown and an exploit is not available.
The vulnerability scanner Nessus provides a plugin with the ID 240010 (TencentOS Server 2: kernel (TSSA-2024:1031)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 6.6.16, 6.7.4 or 6.8-rc1 eliminates this vulnerability. Applying the patch 17e1361cb91d/c04c162f82ac/49db9b1b86a8 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the vulnerability database at Tenable (240010). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
Version
- 6.6.0
- 6.6.1
- 6.6.2
- 6.6.3
- 6.6.4
- 6.6.5
- 6.6.6
- 6.6.7
- 6.6.8
- 6.6.9
- 6.6.10
- 6.6.11
- 6.6.12
- 6.6.13
- 6.6.14
- 6.6.15
- 6.7.0
- 6.7.1
- 6.7.2
- 6.7.3
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.6VulDB Meta Temp Score: 6.5
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 7.8
CNA Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Privilege escalationCWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 240010
Nessus Name: TencentOS Server 2: kernel (TSSA-2024:1031)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Kernel 6.6.16/6.7.4/6.8-rc1
Patch: 17e1361cb91d/c04c162f82ac/49db9b1b86a8
Timeline
03/02/2024 🔍03/06/2024 🔍
03/06/2024 🔍
06/17/2025 🔍
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2023-52591 (🔍)
GCVE (CVE): GCVE-0-2023-52591
GCVE (VulDB): GCVE-100-255874
Entry
Created: 03/06/2024 08:45Updated: 06/17/2025 15:53
Changes: 03/06/2024 08:45 (41), 11/01/2024 18:44 (26), 06/17/2025 15:53 (2)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.