CVEvulnerability

CVE-2023-53222

7.1 HIGH Published 2025-09-15 Modified 2026-08-04 Official page ↗
Status
Modified
Published
2025-09-15
Last modified
2026-08-04
Assigner
416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS 3.1 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)
7.8 HIGH — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS 3.1 ([email protected])
7.1 HIGH — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
CVSS 3.1 (134c704f-9b21-4f2e-91b3-4a467353bcc0)
7.1 HIGH — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
Weaknesses
CWE-125

Description

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

Affected configurations

• linux linux kernel (< 4.14.322) • linux linux kernel (>= 4.15 < 4.19.291) • linux linux kernel (>= 4.20 < 5.4.251) • linux linux kernel (>= 5.5 < 5.10.188) • linux linux kernel (>= 5.11 < 5.15.121) • linux linux kernel (>= 5.16 < 6.1.40) • linux linux kernel (>= 6.2 < 6.4.5)

Related

Weakness · CWE (1)

  • CWE-125 Out-of-bounds Read weakness

References