Answer in brief
CVE-2023-53222 records a High severity (CVSS 7.8) vulnerability in jfs: jfs_dmap: Validate db_l2nbperpage while mounting. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2023-53222 records a High severity (CVSS 7.8) vulnerability in jfs: jfs_dmap: Validate db_l2nbperpage while mounting. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <8c1efe3f74a7864461b0dff281c5562154b4aa8e || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ef5c205b6e6f8d1f18ef0b4a9832b1b5fa85f7f2 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a4855aeb13e4ad1f23e16753b68212e180f7d848 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <47b7eaae08e8b2f25bdf37bc14d21be090bcb20f || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <de984faecddb900fa850af4df574a25b32bb93f5 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c7feb54b113802d2aba98708769d3c33fb017254 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2a03c4e683d33d17b667418eb717b13dda1fac6b || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <11509910c599cbd04585ec35a6d5e1a0053d84c1 | 8c1efe3f74a7864461b0dff281c5562154b4aa8e, ef5c205b6e6f8d1f18ef0b4a9832b1b5fa85f7f2, a4855aeb13e4ad1f23e16753b68212e180f7d848, 47b7eaae08e8b2f25bdf37bc14d21be090bcb20f, de984faecddb900fa850af4df574a25b32bb93f5, c7feb54b113802d2aba98708769d3c33fb017254, 2a03c4e683d33d17b667418eb717b13dda1fac6b, 11509910c599cbd04585ec35a6d5e1a0053d84c1 |
| Linux/Linuxgeneric | 2.6.12 | Not reported |
Published upstream
Sep 15, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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
Quoted source text, attributed separately from HOL analysis.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <8c1efe3f74a7864461b0dff281c5562154b4aa8e || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ef5c205b6e6f8d1f18ef0b4a9832b1b5fa85f7f2 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a4855aeb13e4ad1f23e16753b68212e180f7d848 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <47b7eaae08e8b2f25bdf37bc14d21be090bcb20f || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <de984faecddb900fa850af4df574a25b32bb93f5 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c7feb54b113802d2aba98708769d3c33fb017254 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2a03c4e683d33d17b667418eb717b13dda1fac6b || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <11509910c599cbd04585ec35a6d5e1a0053d84c1 | 8c1efe3f74a7864461b0dff281c5562154b4aa8e, ef5c205b6e6f8d1f18ef0b4a9832b1b5fa85f7f2, a4855aeb13e4ad1f23e16753b68212e180f7d848, 47b7eaae08e8b2f25bdf37bc14d21be090bcb20f, de984faecddb900fa850af4df574a25b32bb93f5, c7feb54b113802d2aba98708769d3c33fb017254, 2a03c4e683d33d17b667418eb717b13dda1fac6b, 11509910c599cbd04585ec35a6d5e1a0053d84c1 |
| Linux/Linuxgeneric | 2.6.12 | Not reported |
Published upstream
Sep 15, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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
Quoted source text, attributed separately from HOL analysis.