Linux Kernel up to 6.2.10 nilfs_sysfs_create_device_group use after free

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Linux Kernel up to 6.2.10. It has been rated as critical. The impacted element is the function nilfs_sysfs_create_device_group. The manipulation leads to use after free.
This vulnerability is uniquely identified as CVE-2023-53440. No exploit exists.
Upgrading the affected component is advised.
Details
A vulnerability, which was classified as critical, has been found in Linux Kernel up to 6.2.10. This issue affects the function nilfs_sysfs_create_device_group. The manipulation with an unknown input leads to a use after free vulnerability. Using CWE to declare the problem leads to CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix sysfs interface lifetime The current nilfs2 sysfs support has issues with the timing of creation and deletion of sysfs entries, potentially leading to null pointer dereferences, use-after-free, and lockdep warnings. Some of the sysfs attributes for nilfs2 per-filesystem instance refer to metadata file "cpfile", "sufile", or "dat", but nilfs_sysfs_create_device_group that creates those attributes is executed before the inodes for these metadata files are loaded, and nilfs_sysfs_delete_device_group which deletes these sysfs entries is called after releasing their metadata file inodes. Therefore, access to some of these sysfs attributes may occur outside of the lifetime of these metadata files, resulting in inode NULL pointer dereferences or use-after-free. In addition, the call to nilfs_sysfs_create_device_group() is made during the locking period of the semaphore "ns_sem" of nilfs object, so the shrinker call caused by the memory allocation for the sysfs entries, may derive lock dependencies "ns_sem" -> (shrinker) -> "locks acquired in nilfs_evict_inode()". Since nilfs2 may acquire "ns_sem" deep in the call stack holding other locks via its error handler __nilfs_error(), this causes lockdep to report circular locking. This is a false positive and no circular locking actually occurs as no inodes exist yet when nilfs_sysfs_create_device_group() is called. Fortunately, the lockdep warnings can be resolved by simply moving the call to nilfs_sysfs_create_device_group() out of "ns_sem". This fixes these sysfs issues by revising where the device's sysfs interface is created/deleted and keeping its lifetime within the lifetime of the metadata files above.
It is possible to read the advisory at git.kernel.org. The identification of this vulnerability is CVE-2023-53440 since 09/17/2025. The exploitation is known to be easy. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 12/12/2025).
The vulnerability scanner Nessus provides a plugin with the ID 265907 (Linux Distros Unpatched Vulnerability : CVE-2023-53440), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 4.14.313, 4.19.281, 5.4.241, 5.10.178, 5.15.107, 6.1.24 or 6.2.11 eliminates this vulnerability. Applying the patch d20dcec8f326deb77b6688f8441e014045dac457/5fe0ea141fbb887d407f1bf572ebf24427480d5c/83b16a60e413148685739635901937e2f16a7873/3dbee84bf9e3273c4bb9ca6fc18ff22fba23dd24/d540aea451ab5489777a8156560f1388449b3109/1942ccb7d95f287a312fcbabfa8bc9ba501b1953/daf4eb3a908b108279b60172d2f176e70d2df875/42560f9c92cc43dce75dbf06cc0d840dced39b12 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 databases at Tenable (265907) and CERT Bund (WID-SEC-2025-2092). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Affected
- Amazon Linux 2
- Red Hat Enterprise Linux
- SUSE Linux
- Oracle Linux
- SUSE openSUSE
- RESF Rocky Linux
- Open Source Linux Kernel
- Dell Secure Connect Gateway
- IBM QRadar SIEM
Product
Type
Vendor
Name
Version
- 4.14.312
- 4.19.280
- 5.4.240
- 5.10.177
- 5.15.106
- 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.1.22
- 6.1.23
- 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
- 6.2.9
- 6.2.10
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.8VulDB Meta Temp Score: 6.6
VulDB Base Score: 8.0
VulDB Temp Score: 7.6
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: Use after freeCWE: CWE-416 / CWE-119
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: 265907
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2023-53440
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 4.14.313/4.19.281/5.4.241/5.10.178/5.15.107/6.1.24/6.2.11
Patch: d20dcec8f326deb77b6688f8441e014045dac457/5fe0ea141fbb887d407f1bf572ebf24427480d5c/83b16a60e413148685739635901937e2f16a7873/3dbee84bf9e3273c4bb9ca6fc18ff22fba23dd24/d540aea451ab5489777a8156560f1388449b3109/1942ccb7d95f287a312fcbabfa8bc9ba501b1953/daf4eb3a908b108279b60172d2f176e70d2df875/42560f9c92cc43dce75dbf06cc0d840dced39b12
Timeline
09/17/2025 CVE reserved09/18/2025 Advisory disclosed
09/18/2025 VulDB entry created
12/12/2025 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2023-53440 (🔒)
GCVE (CVE): GCVE-0-2023-53440
GCVE (VulDB): GCVE-100-324947
CERT Bund: WID-SEC-2025-2092 - Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service
Entry
Created: 09/18/2025 19:25Updated: 12/12/2025 01:00
Changes: 09/18/2025 19:25 (58), 09/20/2025 20:01 (7), 09/26/2025 07:05 (2), 11/29/2025 19:33 (1), 12/12/2025 01:00 (11)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.