Skip to content
Noroxi
CVE-2023-52604· NVD / CVE Program· CNA Linux

FS:JFS:UBSAN:array-index-out-of-bounds in dbAdjTree

Noroxi assessment

Priority: Monitor (action score 31/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.25% (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 42f433785f108893de0dd5260bafb85d7d51db03, 59342822276f753e49d27ef5eebffbba990572b9, 6a44065dd604972ec1fbcccbdc4a70d266a89cdd.
  • Mentioned 2 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 42f433785f108893de0dd5260bafb85d7d51db03, 59342822276f753e49d27ef5eebffbba990572b9, 6a44065dd604972ec1fbcccbdc4a70d266a89cdd 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: FS:JFS:UBSAN:array-index-out-of-bounds in dbAdjTree Syzkaller reported the following issue: UBSAN: array-index-out-of-bounds in fs/jfs/jfs_dmap.c:2867:6 index 196694 is out of range for type 's8[1365]' (aka 'signed char[1365]') CPU: 1 PID: 109 Comm: jfsCommit Not tainted 6.6.0-rc3-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/04/2023 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106 ubsan_epilogue lib/ubsan.c:217 [inline] __ubsan_handle_out_of_bounds+0x11c/0x150 lib/ubsan.c:348 dbAdjTree+0x474/0x4f0 fs/jfs/jfs_dmap.c:2867 dbJoin+0x210/0x2d0 fs/jfs/jfs_dmap.c:2834 dbFreeBits+0x4eb/0xda0 fs/jfs/jfs_dmap.c:2331 dbFreeDmap fs/jfs/jfs_dmap.c:2080 [inline] dbFree+0x343/0x650 fs/jfs/jfs_dmap.c:402 txFreeMap+0x798/0xd50 fs/jfs/jfs_txnmgr.c:2534 txUpdateMap+0x342/0x9e0 txLazyCommit fs/jfs/jfs_txnmgr.c:2664 [inline] jfs_lazycommit+0x47a/0xb70 fs/jfs/jfs_txnmgr.c:2732 kthread+0x2d3/0x370 kernel/kthread.c:388 ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304 </TASK> ================================================================================ Kernel panic - not syncing: UBSAN: panic_on_warn set ... CPU: 1 PID: 109 Comm: jfsCommit Not tainted 6.6.0-rc3-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/04/2023 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106 panic+0x30f/0x770 kernel/panic.c:340 check_panic_on_warn+0x82/0xa0 kernel/panic.c:236 ubsan_epilogue lib/ubsan.c:223 [inline] __ubsan_handle_out_of_bounds+0x13c/0x150 lib/ubsan.c:348 dbAdjTree+0x474/0x4f0 fs/jfs/jfs_dmap.c:2867 dbJoin+0x210/0x2d0 fs/jfs/jfs_dmap.c:2834 dbFreeBits+0x4eb/0xda0 fs/jfs/jfs_dmap.c:2331 dbFreeDmap fs/jfs/jfs_dmap.c:2080 [inline] dbFree+0x343/0x650 fs/jfs/jfs_dmap.c:402 txFreeMap+0x798/0xd50 fs/jfs/jfs_txnmgr.c:2534 txUpdateMap+0x342/0x9e0 txLazyCommit fs/jfs/jfs_txnmgr.c:2664 [inline] jfs_lazycommit+0x47a/0xb70 fs/jfs/jfs_txnmgr.c:2732 kthread+0x2d3/0x370 kernel/kthread.c:388 ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304 </TASK> Kernel Offset: disabled Rebooting in 86400 seconds.. The issue is caused when the value of lp becomes greater than CTLTREESIZE which is the max size of stree. Adding a simple check solves this issue. Dave: As the function returns a void, good error handling would require a more intrusive code reorganization, so I modified Osama's patch at use WARN_ON_ONCE for lack of a cleaner option. The patch is tested via syzbot.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Mar 6, 2024
Updated
Aug 5, 2026
EPSS
0.2% · 15th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.8
CNA · Linux
7.8
agree

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-52604

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.19.307
  • linux linux kernel4.20 and later · before 5.4.269
  • linux linux kernel5.5 and later · before 5.10.210
  • linux linux kernel5.11 and later · before 5.15.149
  • linux linux kernel5.16 and later · before 6.1.77
  • linux linux kernel6.2 and later · before 6.6.16
  • linux linux kernel6.7 and later · before 6.7.4

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 e3e95c6850661c77e6dab079d9b5374a618ebb15affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 98f9537fe61b8382b3cc5dd97347531698517c56affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before de34de6e57bbbc868e4fcf9e98c76b3587cabb0baffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 6fe8b702125aeee6ce83f20092a2341446704e7baffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 42f433785f108893de0dd5260bafb85d7d51db03affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 6a44065dd604972ec1fbcccbdc4a70d266a89cddaffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 59342822276f753e49d27ef5eebffbba990572b9affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 9862ec7ac1cbc6eb5ee4a045b5d5b8edbb2f7e68affected · 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.82-16.1.82-1
Debian:13linuxbefore 6.7.7-16.7.7-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • 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
  • CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV
    83Now

Published before and after this one in the same product

  • ← EarlierCVE-2023-52602Mar 6, 2024 · jfs: fix slab-out-of-bounds Read in dtSearch
    31Monitor
  • ← EarlierCVE-2023-52603Mar 6, 2024 · UBSAN: array-index-out-of-bounds in dtSplitRoot
    31Monitor
  • Later →CVE-2023-52606Mar 6, 2024 · powerpc/lib: Validate size for vector operations
    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 Linux42f433785f108893de0dd5260bafb85d7d51db03Vendor (CNA)
Linux Linux59342822276f753e49d27ef5eebffbba990572b9Vendor (CNA)
Linux Linux6a44065dd604972ec1fbcccbdc4a70d266a89cddVendor (CNA)
Linux Linux6fe8b702125aeee6ce83f20092a2341446704e7bVendor (CNA)
Linux Linux9862ec7ac1cbc6eb5ee4a045b5d5b8edbb2f7e68Vendor (CNA)
Linux Linux98f9537fe61b8382b3cc5dd97347531698517c56Vendor (CNA)
Linux Linuxde34de6e57bbbc868e4fcf9e98c76b3587cabb0bVendor (CNA)
Linux Linuxe3e95c6850661c77e6dab079d9b5374a618ebb15Vendor (CNA)
debian:linux6.1.82-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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

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.

  • CVE-2021-4754879 days apartethernet: hisilicon: hns: hns_dsaf_misc: fix a possible array overflow in hns_dsaf_ge_srst_by_port()
    39Monitor
  • CVE-2023-2008327 days apartKernel: udmabuf: improper validation of array index leading to local privilege escalation
    32Monitor
  • CVE-2023-525940 days apartwifi: ath9k: Fix potential array-index-out-of-bounds read in ath9k_htc_txstatus()
    31Monitor
  • CVE-2023-525990 days apartjfs: fix array-index-out-of-bounds in diNewExt
    31Monitor
  • CVE-2023-526010 days apartjfs: fix array-index-out-of-bounds in dbAdjTree
    31Monitor
  • CVE-2023-526030 days apartUBSAN: array-index-out-of-bounds in dtSplitRoot
    31Monitor

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).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

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
high · data or configuration can be modified
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
High
Availability impact
High

Weakness class (CWE)

CWE-129 · Improper Validation of Array Index

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 (9 more)

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

All records