Linux Kernel up to 6.3.2 ext4_xattr_move_to_block allocation of resources

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Linux Kernel up to 6.3.2. This issue affects the function ext4_xattr_move_to_block. Performing a manipulation results in allocation of resources.
This vulnerability is identified as CVE-2023-54062. There is not any exploit available.
It is recommended to upgrade the affected component.
Details
A vulnerability was found in Linux Kernel up to 6.3.2. It has been classified as critical. This affects the function ext4_xattr_move_to_block. The manipulation with an unknown input leads to a allocation of resources vulnerability. CWE is classifying the issue as CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. The impact remains unknown. The summary by CVE is:
In the Linux kernel, the following vulnerability has been resolved: ext4: fix invalid free tracking in ext4_xattr_move_to_block() In ext4_xattr_move_to_block(), the value of the extended attribute which we need to move to an external block may be allocated by kvmalloc() if the value is stored in an external inode. So at the end of the function the code tried to check if this was the case by testing entry->e_value_inum. However, at this point, the pointer to the xattr entry is no longer valid, because it was removed from the original location where it had been stored. So we could end up calling kvfree() on a pointer which was not allocated by kvmalloc(); or we could also potentially leak memory by not freeing the buffer when it should be freed. Fix this by storing whether it should be freed in a separate variable.
The advisory is shared at git.kernel.org. This vulnerability is uniquely identified as CVE-2023-54062 since 12/24/2025. Technical details are known, but no exploit is available.
The vulnerability scanner Nessus provides a plugin with the ID 279916 (Linux Distros Unpatched Vulnerability : CVE-2023-54062), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 4.14.315, 4.19.283, 5.4.243, 5.10.180, 5.15.112, 6.1.29, 6.2.16 or 6.3.3 eliminates this vulnerability. Applying the patch 76887be2a96193cd11be818551b8934ecdb3123f/f30f3391d089dc91aef91d08f4b04a6c0df2b067/ba04d6af5ac440a6d5a2d35dc1d8e2cb0323550a/1a8822343e67432b658145d2760a524c884da9d4/8beaa3cb293a8f7bacf711cf52201d59859dbc40/c5fa4eedddd1c8342ce533cb401c0e693e55b4e3/a18670395e5f28acddeca037c5e4bd2ea961b70a/b2fab1807d26acd1c6115b95b5eddd697d84751b/b87c7cdf2bed4928b899e1ce91ef0d147017ba45 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 (279916) and CERT Bund (WID-SEC-2025-2929). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Affected
- Open Source Linux Kernel
Product
Type
Vendor
Name
Version
- 4.14.314
- 4.19.282
- 5.4.242
- 5.10.179
- 5.15.111
- 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.1.24
- 6.1.25
- 6.1.26
- 6.1.27
- 6.1.28
- 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
- 6.2.11
- 6.2.12
- 6.2.13
- 6.2.14
- 6.2.15
- 6.3.0
- 6.3.1
- 6.3.2
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
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: Allocation of resourcesCWE: CWE-770 / CWE-400 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
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: 279916
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2023-54062
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 4.14.315/4.19.283/5.4.243/5.10.180/5.15.112/6.1.29/6.2.16/6.3.3
Patch: 76887be2a96193cd11be818551b8934ecdb3123f/f30f3391d089dc91aef91d08f4b04a6c0df2b067/ba04d6af5ac440a6d5a2d35dc1d8e2cb0323550a/1a8822343e67432b658145d2760a524c884da9d4/8beaa3cb293a8f7bacf711cf52201d59859dbc40/c5fa4eedddd1c8342ce533cb401c0e693e55b4e3/a18670395e5f28acddeca037c5e4bd2ea961b70a/b2fab1807d26acd1c6115b95b5eddd697d84751b/b87c7cdf2bed4928b899e1ce91ef0d147017ba45
Timeline
12/24/2025 Advisory disclosed12/24/2025 CVE reserved
12/24/2025 VulDB entry created
12/30/2025 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2023-54062 (🔒)
GCVE (CVE): GCVE-0-2023-54062
GCVE (VulDB): GCVE-100-338001
CERT Bund: WID-SEC-2025-2929 - Linux Kernel: Mehrere Schwachstellen
Entry
Created: 12/24/2025 14:36Updated: 12/30/2025 09:56
Changes: 12/24/2025 14:36 (58), 12/26/2025 13:22 (2), 12/30/2025 09:56 (7)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.