Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-53222: jfs: jfs_dmap: Validate db_l2nbperpage while mounting

Noroxi assessment

Priority: Monitor (action score 28/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 11509910c599cbd04585ec35a6d5e1a0053d84c1, 2a03c4e683d33d17b667418eb717b13dda1fac6b, 47b7eaae08e8b2f25bdf37bc14d21be090bcb20f.

Low priority for now. Upgrade to Linux Linux 11509910c599cbd04585ec35a6d5e1a0053d84c1, 2a03c4e683d33d17b667418eb717b13dda1fac6b, 47b7eaae08e8b2f25bdf37bc14d21be090bcb20f or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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

HighCVSS 7.1 · v3.1—No exploit Fix available
Published
Sep 15, 2025
Updated
Aug 5, 2026
EPSS
0.1% · 6th percentile

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.1
CNA · Linux
7.8
0.7 point gap

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2023-53222

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernelbefore 4.14.322
  • linux linux kernel4.15 and later · before 4.19.291
  • linux linux kernel4.20 and later · before 5.4.251
  • linux linux kernel5.5 and later · before 5.10.188
  • linux linux kernel5.11 and later · before 5.15.121
  • linux linux kernel5.16 and later · before 6.1.40
  • linux linux kernel6.2 and later · before 6.4.5

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 2.6.12affected
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 8c1efe3f74a7864461b0dff281c5562154b4aa8eaffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before ef5c205b6e6f8d1f18ef0b4a9832b1b5fa85f7f2affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before a4855aeb13e4ad1f23e16753b68212e180f7d848affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 47b7eaae08e8b2f25bdf37bc14d21be090bcb20faffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before de984faecddb900fa850af4df574a25b32bb93f5affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before c7feb54b113802d2aba98708769d3c33fb017254affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 2a03c4e683d33d17b667418eb717b13dda1fac6baffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 11509910c599cbd04585ec35a6d5e1a0053d84c1affected · git
    • before 2.6.12not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.52-16.1.52-1
Debian:13linuxbefore 6.4.11-16.4.11-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2023-53220Sep 15, 2025 · media: az6007: Fix null-ptr-deref in az6007_i2c_xfer()
    22Monitor
  • ← EarlierCVE-2023-53221Sep 15, 2025 · bpf: Fix memleak due to fentry attach failure
    22Monitor
  • Later →CVE-2023-53223Sep 15, 2025 · drm/msm/dsi: Add missing check for alloc_ordered_workqueue
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux11509910c599cbd04585ec35a6d5e1a0053d84c1Vendor (CNA)
Linux Linux2a03c4e683d33d17b667418eb717b13dda1fac6bVendor (CNA)
Linux Linux47b7eaae08e8b2f25bdf37bc14d21be090bcb20fVendor (CNA)
Linux Linux8c1efe3f74a7864461b0dff281c5562154b4aa8eVendor (CNA)
Linux Linuxa4855aeb13e4ad1f23e16753b68212e180f7d848Vendor (CNA)
Linux Linuxc7feb54b113802d2aba98708769d3c33fb017254Vendor (CNA)
Linux Linuxde984faecddb900fa850af4df574a25b32bb93f5Vendor (CNA)
Linux Linuxef5c205b6e6f8d1f18ef0b4a9832b1b5fa85f7f2Vendor (CNA)
debian:linux6.1.52-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-125 · Out-of-bounds Read

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records