Linux Kernel up to 5.15.104/6.1.21/6.2.8 ksmbd smb2_open reference count

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Linux Kernel up to 5.15.104/6.1.21/6.2.8. It has been rated as critical. The impacted element is the function smb2_open of the component ksmbd. This manipulation causes reference count.
This vulnerability is tracked as CVE-2023-53061. No exploit exists.
Upgrading the affected component is advised.
Details
A vulnerability has been found in Linux Kernel up to 5.15.104/6.1.21/6.2.8 and classified as critical. Affected by this vulnerability is the function smb2_open of the component ksmbd. The manipulation with an unknown input leads to a reference count vulnerability. The CWE definition for the vulnerability is CWE-911. The product uses a reference count to manage a resource, but it does not update or incorrectly updates the reference count. As an impact it is known to affect availability. The summary by CVE is:
In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix possible refcount leak in smb2_open() Reference count of acls will leak when memory allocation fails. Fix this by adding the missing posix_acl_release().
The advisory is shared at git.kernel.org. This vulnerability is known as CVE-2023-53061 since 05/02/2025. Technical details are known, but no exploit is available.
Upgrading to version 5.15.105, 6.1.22 or 6.2.9 eliminates this vulnerability. Applying the patch c33344b7972225b232966f95d31f6312dcc6273d/303f8e58cc3ace744801dcdcabfc06ffc72ed62d/a22c49a05e5e7aa2c414fbc42c49c4c01a5c9a78/2624b445544ffc1472ccabfb6ec867c199d4c95c 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.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
- 5.15.104
- 6.1.0
- 6.1.1
- 6.1.2
- 6.1.3
- 6.1.4
- 6.1.5
- 6.1.6
- 6.1.7
- 6.1.8
- 6.1.9
- 6.1.10
- 6.1.11
- 6.1.12
- 6.1.13
- 6.1.14
- 6.1.15
- 6.1.16
- 6.1.17
- 6.1.18
- 6.1.19
- 6.1.20
- 6.1.21
- 6.2.0
- 6.2.1
- 6.2.2
- 6.2.3
- 6.2.4
- 6.2.5
- 6.2.6
- 6.2.7
- 6.2.8
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.6VulDB Meta Temp Score: 5.5
VulDB Base Score: 5.7
VulDB Temp Score: 5.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD 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: Reference countCWE: CWE-911 / CWE-664
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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Kernel 5.15.105/6.1.22/6.2.9
Patch: c33344b7972225b232966f95d31f6312dcc6273d/303f8e58cc3ace744801dcdcabfc06ffc72ed62d/a22c49a05e5e7aa2c414fbc42c49c4c01a5c9a78/2624b445544ffc1472ccabfb6ec867c199d4c95c
Timeline
05/02/2025 🔍05/02/2025 🔍
05/02/2025 🔍
11/07/2025 🔍
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2023-53061 (🔍)
GCVE (CVE): GCVE-0-2023-53061
GCVE (VulDB): GCVE-100-307237
Entry
Created: 05/02/2025 19:52Updated: 11/07/2025 18:30
Changes: 05/02/2025 19:52 (59), 11/07/2025 18:30 (11)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.