CVE-2023-52599: jfs: fix array-index-out-of-bounds in diNewExt
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 3537f92cd22c672db97fae6997481e678ad14641, 49f9637aafa6e63ba686c13cb8549bf5e6920402, 5a6660139195f5e2fbbda459eeecb8788f3885fe.
- Mentioned 2 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 3537f92cd22c672db97fae6997481e678ad14641, 49f9637aafa6e63ba686c13cb8549bf5e6920402, 5a6660139195f5e2fbbda459eeecb8788f3885fe 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: fix array-index-out-of-bounds in diNewExt [Syz report] UBSAN: array-index-out-of-bounds in fs/jfs/jfs_imap.c:2360:2 index -878706688 is out of range for type 'struct iagctl[128]' CPU: 1 PID: 5065 Comm: syz-executor282 Not tainted 6.7.0-rc4-syzkaller-00009-gbee0e7762ad2 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/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 diNewExt+0x3cf3/0x4000 fs/jfs/jfs_imap.c:2360 diAllocExt fs/jfs/jfs_imap.c:1949 [inline] diAllocAG+0xbe8/0x1e50 fs/jfs/jfs_imap.c:1666 diAlloc+0x1d3/0x1760 fs/jfs/jfs_imap.c:1587 ialloc+0x8f/0x900 fs/jfs/jfs_inode.c:56 jfs_mkdir+0x1c5/0xb90 fs/jfs/namei.c:225 vfs_mkdir+0x2f1/0x4b0 fs/namei.c:4106 do_mkdirat+0x264/0x3a0 fs/namei.c:4129 __do_sys_mkdir fs/namei.c:4149 [inline] __se_sys_mkdir fs/namei.c:4147 [inline] __x64_sys_mkdir+0x6e/0x80 fs/namei.c:4147 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x45/0x110 arch/x86/entry/common.c:82 entry_SYSCALL_64_after_hwframe+0x63/0x6b RIP: 0033:0x7fcb7e6a0b57 Code: ff ff 77 07 31 c0 c3 0f 1f 40 00 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff c3 66 0f 1f 44 00 00 b8 53 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffd83023038 EFLAGS: 00000286 ORIG_RAX: 0000000000000053 RAX: ffffffffffffffda RBX: 00000000ffffffff RCX: 00007fcb7e6a0b57 RDX: 00000000000a1020 RSI: 00000000000001ff RDI: 0000000020000140 RBP: 0000000020000140 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000286 R12: 00007ffd830230d0 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 [Analysis] When the agstart is too large, it can cause agno overflow. [Fix] After obtaining agno, if the value is invalid, exit the subsequent process. Modified the test from agno > MAXAG to agno >= MAXAG based on linux-next report by kernel test robot (Dan Carpenter).
- Published
- Mar 6, 2024
- Updated
- Aug 5, 2026
- EPSS
- 0.2% · 16th percentile
- CWE
- CWE-129
Report tools
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.
Is your version affected? Check itNoroxi 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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_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 f423528488e4f9606cef858eceea210bf1163f41affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before de6a91aed1e0b1a23e9c11e7d7557f088eeeb017affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before e2b77d107b33bb31c8b1f5c4cb8f277b23728f1eaffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 6aa30020879042d46df9f747e4f0a486eea6fe98affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 3537f92cd22c672db97fae6997481e678ad14641affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 6996d43b14486f4a6655b10edc541ada1b580b4baffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 5a6660139195f5e2fbbda459eeecb8788f3885feaffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 49f9637aafa6e63ba686c13cb8549bf5e6920402affected · git
- before 2.6.12not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.82-1 | 6.1.82-1 |
| Debian:13 | linux | before 6.7.7-1 | 6.7.7-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- 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…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2023-52597Mar 6, 2024 · KVM: s390: fix setting of fpc register16Monitor
- ← EarlierCVE-2023-52598Mar 6, 2024 · s390/ptrace: handle setting of fpc register correctly28Monitor
- Later →CVE-2023-52600Mar 6, 2024 · jfs: fix uaf in jfs_evict_inode31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 3537f92cd22c672db97fae6997481e678ad14641 | Vendor (CNA) |
| Linux Linux | 49f9637aafa6e63ba686c13cb8549bf5e6920402 | Vendor (CNA) |
| Linux Linux | 5a6660139195f5e2fbbda459eeecb8788f3885fe | Vendor (CNA) |
| Linux Linux | 6996d43b14486f4a6655b10edc541ada1b580b4b | Vendor (CNA) |
| Linux Linux | 6aa30020879042d46df9f747e4f0a486eea6fe98 | Vendor (CNA) |
| Linux Linux | de6a91aed1e0b1a23e9c11e7d7557f088eeeb017 | Vendor (CNA) |
| Linux Linux | e2b77d107b33bb31c8b1f5c4cb8f277b23728f1e | Vendor (CNA) |
| Linux Linux | f423528488e4f9606cef858eceea210bf1163f41 | Vendor (CNA) |
| debian:linux | 6.1.82-1 · Debian:12 | Package 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 researchersFinders, 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 escalation32Monitor
- CVE-2023-525940 days apartwifi: ath9k: Fix potential array-index-out-of-bounds read in ath9k_htc_txstatus()31Monitor
- CVE-2023-526010 days apartjfs: fix array-index-out-of-bounds in dbAdjTree31Monitor
- CVE-2023-526030 days apartUBSAN: array-index-out-of-bounds in dtSplitRoot31Monitor
- CVE-2023-526040 days apartFS:JFS:UBSAN:array-index-out-of-bounds in dbAdjTree31Monitor
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.
- TR-24-0494 · May 16, 2024(Linux Kernel Güncellemesi)
- TR-24-0176 · Mar 6, 2024(Linux Kernel Güncellemesi)
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 IndexCVSS 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.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (9 more)Show less
- git.kernel.org/stable/c/49f9637aafa6e63ba686c13cb8549bf5e6920402
- git.kernel.org/stable/c/5a6660139195f5e2fbbda459eeecb8788f3885fe
- git.kernel.org/stable/c/6996d43b14486f4a6655b10edc541ada1b580b4b
- git.kernel.org/stable/c/6aa30020879042d46df9f747e4f0a486eea6fe98
- git.kernel.org/stable/c/de6a91aed1e0b1a23e9c11e7d7557f088eeeb017
- git.kernel.org/stable/c/e2b77d107b33bb31c8b1f5c4cb8f277b23728f1e
- git.kernel.org/stable/c/f423528488e4f9606cef858eceea210bf1163f41
- lists.debian.org/debian-lts-announce/2024/06/msg00017.html
- lists.debian.org/debian-lts-announce/2024/06/msg00020.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.