Linux Kernel up to 6.4.4 jfs jfs_dmap.c dbFree out-of-bounds

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Linux Kernel up to 6.4.4. The affected element is the function dbFree of the file jfs_dmap.c of the component jfs. Performing a manipulation results in out-of-bounds.
This vulnerability is cataloged as CVE-2023-53222. There is no exploit available.
It is recommended to upgrade the affected component.
Details
A vulnerability classified as problematic has been found in Linux Kernel up to 6.4.4. This affects the function dbFree of the file jfs_dmap.c of the component jfs. The manipulation with an unknown input leads to a out-of-bounds vulnerability. CWE is classifying the issue as CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. This is going to have an impact on confidentiality. The summary by CVE is:
In the Linux kernel, the following vulnerability has been resolved: jfs: jfs_dmap: Validate db_l2nbperpage while mounting In jfs_dmap.c at line 381, BLKTODMAP is used to get a logical block number inside dbFree(). db_l2nbperpage, which is the log2 number of blocks per page, is passed as an argument to BLKTODMAP which uses it for shifting. Syzbot reported a shift out-of-bounds crash because db_l2nbperpage is too big. This happens because the large value is set without any validation in dbMount() at line 181. Thus, make sure that db_l2nbperpage is correct while mounting. Max number of blocks per page = Page size / Min block size => log2(Max num_block per page) = log2(Page size / Min block size) = log2(Page size) - log2(Min block size) => Max db_l2nbperpage = L2PSIZE - L2MINBLOCKSIZE
It is possible to read the advisory at git.kernel.org. This vulnerability is uniquely identified as CVE-2023-53222 since 09/15/2025. Technical details of the vulnerability are known, but there is no available exploit.
The vulnerability scanner Nessus provides a plugin with the ID 265237 (Linux Distros Unpatched Vulnerability : CVE-2023-53222), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 4.14.322, 4.19.291, 5.4.251, 5.10.188, 5.15.121, 6.1.40 or 6.4.5 eliminates this vulnerability. Applying the patch 8c1efe3f74a7864461b0dff281c5562154b4aa8e/ef5c205b6e6f8d1f18ef0b4a9832b1b5fa85f7f2/a4855aeb13e4ad1f23e16753b68212e180f7d848/47b7eaae08e8b2f25bdf37bc14d21be090bcb20f/de984faecddb900fa850af4df574a25b32bb93f5/c7feb54b113802d2aba98708769d3c33fb017254/2a03c4e683d33d17b667418eb717b13dda1fac6b/11509910c599cbd04585ec35a6d5e1a0053d84c1 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 (265237) and CERT Bund (WID-SEC-2025-2053). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Affected
- Debian Linux
- Amazon Linux 2
- Red Hat Enterprise Linux
- Ubuntu Linux
- SUSE Linux
- Oracle Linux
- IBM QRadar SIEM
- SUSE openSUSE
- Open Source Linux Kernel
- RESF Rocky Linux
- Dell Secure Connect Gateway
- F5 F5OS
Product
Type
Vendor
Name
Version
- 4.14.321
- 4.19.290
- 5.4.250
- 5.10.187
- 5.15.120
- 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.1.29
- 6.1.30
- 6.1.31
- 6.1.32
- 6.1.33
- 6.1.34
- 6.1.35
- 6.1.36
- 6.1.37
- 6.1.38
- 6.1.39
- 6.4.0
- 6.4.1
- 6.4.2
- 6.4.3
- 6.4.4
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.2
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 7.1
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: Out-of-boundsCWE: CWE-125 / 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: 265237
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2023-53222
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 4.14.322/4.19.291/5.4.251/5.10.188/5.15.121/6.1.40/6.4.5
Patch: 8c1efe3f74a7864461b0dff281c5562154b4aa8e/ef5c205b6e6f8d1f18ef0b4a9832b1b5fa85f7f2/a4855aeb13e4ad1f23e16753b68212e180f7d848/47b7eaae08e8b2f25bdf37bc14d21be090bcb20f/de984faecddb900fa850af4df574a25b32bb93f5/c7feb54b113802d2aba98708769d3c33fb017254/2a03c4e683d33d17b667418eb717b13dda1fac6b/11509910c599cbd04585ec35a6d5e1a0053d84c1
Timeline
09/15/2025 Advisory disclosed09/15/2025 CVE reserved
09/15/2025 VulDB entry created
01/10/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2023-53222 (🔒)
GCVE (CVE): GCVE-0-2023-53222
GCVE (VulDB): GCVE-100-324099
CERT Bund: WID-SEC-2025-2053 - Linux Kernel: Mehrere Schwachstellen
Entry
Created: 09/15/2025 18:20Updated: 01/10/2026 22:22
Changes: 09/15/2025 18:20 (60), 09/19/2025 11:29 (2), 12/05/2025 11:25 (11), 12/29/2025 03:25 (7), 01/10/2026 22:22 (1)
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.