CVE-2023-53317

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 5.5 from GitHub Security Advisory published 2025-09-16. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

ext4: fix WARNING in mb_find_extent

Syzbot found the following issue:

EXT4-fs: Warning: mounting with data=journal disables delayed allocation, dioread_nolock, O_DIRECT and fast_commit support! EXT4-fs (loop0): orphan cleanup on readonly fs ------------[ cut here ]------------ WARNING: CPU: 1 PID: 5067 at fs/ext4/mballoc.c:1869 mb_find_extent+0x8a1/0xe30 Modules linked in: CPU: 1 PID: 5067 Comm: syz-executor307 Not tainted 6.2.0-rc1-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022 RIP: 0010:mb_find_extent+0x8a1/0xe30 fs/ext4/mballoc.c:1869 RSP: 0018:ffffc90003c9e098 EFLAGS: 00010293 RAX: ffffffff82405731 RBX: 0000000000000041 RCX: ffff8880783457c0 RDX: 0000000000000000 RSI: 0000000000000041 RDI: 0000000000000040 RBP: 0000000000000040 R08: ffffffff82405723 R09: ffffed10053c9402 R10: ffffed10053c9402 R11: 1ffff110053c9401 R12: 0000000000000000 R13: ffffc90003c9e538 R14: dffffc0000000000 R15: ffffc90003c9e2cc FS: 0000555556665300(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000056312f6796f8 CR3: 0000000022437000 CR4: 00000000003506e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: ext4_mb_complex_scan_group+0x353/0x1100 fs/ext4/mballoc.c:2307 ext4_mb_regular_allocator+0x1533/0x3860 fs/ext4/mballoc.c:2735 ext4_mb_new_blocks+0xddf/0x3db0 fs/ext4/mballoc.c:5605 ext4_ext_map_blocks+0x1868/0x6880 fs/ext4/extents.c:4286 ext4_map_blocks+0xa49/0x1cc0 fs/ext4/inode.c:651 ext4_getblk+0x1b9/0x770 fs/ext4/inode.c:864 ext4_bread+0x2a/0x170 fs/ext4/inode.c:920 ext4_quota_write+0x225/0x570 fs/ext4/super.c:7105 write_blk fs/quota/quota_tree.c:64 [inline] get_free_dqblk+0x34a/0x6d0 fs/quota/quota_tree.c:130 do_insert_tree+0x26b/0x1aa0 fs/quota/quota_tree.c:340 do_insert_tree+0x722/0x1aa0 fs/quota/quota_tree.c:375 do_insert_tree+0x722/0x1aa0 fs/quota/quota_tree.c:375 do_insert_tree+0x722/0x1aa0 fs/quota/quota_tree.c:375 dq_insert_tree fs/quota/quota_tree.c:401 [inline] qtree_write_dquot+0x3b6/0x530 fs/quota/quota_tree.c:420 v2_write_dquot+0x11b/0x190 fs/quota/quota_v2.c:358 dquot_acquire+0x348/0x670 fs/quota/dquot.c:444 ext4_acquire_dquot+0x2dc/0x400 fs/ext4/super.c:6740 dqget+0x999/0xdc0 fs/quota/dquot.c:914 __dquot_initialize+0x3d0/0xcf0 fs/quota/dquot.c:1492 ext4_process_orphan+0x57/0x2d0 fs/ext4/orphan.c:329 ext4_orphan_cleanup+0xb60/0x1340 fs/ext4/orphan.c:474 __ext4_fill_super fs/ext4/super.c:5516 [inline] ext4_fill_super+0x81cd/0x8700 fs/ext4/super.c:5644 get_tree_bdev+0x400/0x620 fs/super.c:1282 vfs_get_tree+0x88/0x270 fs/super.c:1489 do_new_mount+0x289/0xad0 fs/namespace.c:3145 do_mount fs/namespace.c:3488 [inline] __do_sys_mount fs/namespace.c:3697 [inline] __se_sys_mount+0x2d3/0x3c0 fs/namespace.c:3674 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd

Add some debug information: mb_find_extent: mb_find_extent block=41, order=0 needed=64 next=0 ex=0/41/1@3735929054 64 64 7 block_bitmap: ff 3f 0c 00 fc 01 00 00 d2 3d 00 00 00 00 00 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff

Acctually, blocks per group is 64, but block bitmap indicate at least has 128 blocks. Now, ext4_validate_block_bitmap() didn't check invalid block's bitmap if set. To resolve above issue, add check like fsck "Padding at end of block bitmap is not set".

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
4th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 16, 2025

Last Modified

January 14, 2026

References (8)

Vendor Advisories for CVE-2023-53317(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:5.14.0-427.13.1.el9_42024-04-30redhat
linuxKernel @ 4.19.283 (fixes >=2.6.25)—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (33 versions)
  • every version up to 5.10.191-1: fixed in 5.10.191-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.27-1
  • every version up to 6.1.37-1: fixed in 6.1.37-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.3.7-1: fixed in 6.3.7-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.3.7-1: fixed in 6.3.7-1
—

Data Freshness Timeline

(refreshed 7× in last 7d / 31× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 90 of 174 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 10 repeat rows among the latest 100 are merged into the row they repeat. The 84 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  2. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  3. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  4. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  5. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  6. 2026-10-18 07:41 UTCEG score recompute
  7. 2026-10-17 16:30 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  8. 2026-10-16 16:36 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  9. 2026-10-15 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  10. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  11. 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  12. 2026-10-12 18:12 UTCEG score recompute
  13. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  14. 2026-10-11 21:38 UTCEG score recompute
  15. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  16. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  17. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  18. 2026-10-08 17:06 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  19. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  20. 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  21. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  22. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  23. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  24. 2026-10-02 05:10 UTCOSV refresh
  25. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.2% · 4th percentile
Show 65 more
  1. 2026-09-30 16:37 UTCEG score recompute
  2. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  3. 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  4. 2026-09-28 13:49 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  5. 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  6. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  7. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  8. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  9. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  10. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  11. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  12. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  13. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  14. 2026-09-13 00:36 UTCOSV refresh
  15. 2026-09-12 14:58 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  16. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  17. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  18. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  19. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  20. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  21. 2026-09-05 15:26 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  22. 2026-09-04 13:58 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  23. 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  24. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  25. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  26. 2026-09-01 04:36 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  27. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  28. 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  29. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  30. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  31. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  32. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  33. 2026-08-25 03:56 UTCOSV refresh
  34. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  35. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  36. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  37. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  38. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  39. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  40. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  41. 2026-08-15 01:28 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  42. 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  43. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  44. 2026-08-11 13:40 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  45. 2026-08-10 23:58 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  46. 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  47. 2026-08-08 21:19 UTCOSV refresh
  48. 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  49. 2026-08-07 16:25 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  50. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  51. 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  52. 2026-08-03 10:34 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  53. 2026-08-02 02:25 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  54. 2026-08-01 04:14 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  55. 2026-07-30 16:26 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  56. 2026-07-30 01:29 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  57. 2026-07-28 15:34 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  58. 2026-07-26 14:53 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  59. 2026-07-25 14:16 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  60. 2026-07-24 14:16 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  61. 2026-07-23 20:11 UTCOSV refresh
  62. 2026-07-23 14:16 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  63. 2026-07-23 02:29 UTCEG score recompute
  64. 2026-07-22 23:16 UTCEG score recompute
  65. 2026-07-22 14:07 UTCEPSS rescoreEPSS 0.1% · 4th percentile

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2023-53317?
CVE-2023-53317 is a medium-severity vulnerability; its CVE record was published on September 16, 2025. In the Linux kernel, the following vulnerability has been resolved: ext4: fix WARNING in mbfindextent Syzbot found the following issue: EXT4-fs: Warning: mounting with data=journal disables delayed allocation, dioreadnolock, ODIRECT and fast_commit support! EXT4-fs (loop0): orphan cleanup on…
When was the CVE record for CVE-2023-53317 published?
The CVE record for CVE-2023-53317 was published on September 16, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of January 14, 2026; the record at its source may have been updated since.
Is CVE-2023-53317 actively exploited?
CVE-2023-53317 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-53317?
CVE-2023-53317 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2023-53317?
A fix for CVE-2023-53317 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-53317 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-53317

Explore →

Is Your Infrastructure Affected by CVE-2023-53317?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs