CVE-2023-53100

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-05-02. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2025-13162 (ENISA EUVD) · GHSA-mvqv-rc3q-g8hm (GitHub Security Advisories)Source: ENISA EUVD

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 ext4_update_inline_data

Syzbot found the following issue: EXT4-fs (loop0): mounted filesystem 00000000-0000-0000-0000-000000000000 without journal. Quota mode: none. fscrypt: AES-256-CTS-CBC using implementation "cts-cbc-aes-aesni" fscrypt: AES-256-XTS using implementation "xts-aes-aesni" ------------[ cut here ]------------ WARNING: CPU: 0 PID: 5071 at mm/page_alloc.c:5525 __alloc_pages+0x30a/0x560 mm/page_alloc.c:5525 Modules linked in: CPU: 1 PID: 5071 Comm: syz-executor263 Not tainted 6.2.0-rc1-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022 RIP: 0010:__alloc_pages+0x30a/0x560 mm/page_alloc.c:5525 RSP: 0018:ffffc90003c2f1c0 EFLAGS: 00010246 RAX: ffffc90003c2f220 RBX: 0000000000000014 RCX: 0000000000000000 RDX: 0000000000000028 RSI: 0000000000000000 RDI: ffffc90003c2f248 RBP: ffffc90003c2f2d8 R08: dffffc0000000000 R09: ffffc90003c2f220 R10: fffff52000785e49 R11: 1ffff92000785e44 R12: 0000000000040d40 R13: 1ffff92000785e40 R14: dffffc0000000000 R15: 1ffff92000785e3c FS: 0000555556c0d300(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f95d5e04138 CR3: 00000000793aa000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: __alloc_pages_node include/linux/gfp.h:237 [inline] alloc_pages_node include/linux/gfp.h:260 [inline] __kmalloc_large_node+0x95/0x1e0 mm/slab_common.c:1113 __do_kmalloc_node mm/slab_common.c:956 [inline] __kmalloc+0xfe/0x190 mm/slab_common.c:981 kmalloc include/linux/slab.h:584 [inline] kzalloc include/linux/slab.h:720 [inline] ext4_update_inline_data+0x236/0x6b0 fs/ext4/inline.c:346 ext4_update_inline_dir fs/ext4/inline.c:1115 [inline] ext4_try_add_inline_entry+0x328/0x990 fs/ext4/inline.c:1307 ext4_add_entry+0x5a4/0xeb0 fs/ext4/namei.c:2385 ext4_add_nondir+0x96/0x260 fs/ext4/namei.c:2772 ext4_create+0x36c/0x560 fs/ext4/namei.c:2817 lookup_open fs/namei.c:3413 [inline] open_last_lookups fs/namei.c:3481 [inline] path_openat+0x12ac/0x2dd0 fs/namei.c:3711 do_filp_open+0x264/0x4f0 fs/namei.c:3741 do_sys_openat2+0x124/0x4e0 fs/open.c:1310 do_sys_open fs/open.c:1326 [inline] __do_sys_openat fs/open.c:1342 [inline] __se_sys_openat fs/open.c:1337 [inline] __x64_sys_openat+0x243/0x290 fs/open.c:1337 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

Above issue happens as follows: ext4_iget ext4_find_inline_data_nolock ->i_inline_off=164 i_inline_size=60 ext4_try_add_inline_entry __ext4_mark_inode_dirty ext4_expand_extra_isize_ea ->i_extra_isize=32 s_want_extra_isize=44 ext4_xattr_shift_entries ->after shift i_inline_off is incorrect, actually is change to 176 ext4_try_add_inline_entry ext4_update_inline_dir get_max_inline_xattr_value_size if (EXT4_I(inode)->i_inline_off) entry = (struct ext4_xattr_entry *)((void *)raw_inode + EXT4_I(inode)->i_inline_off); free += EXT4_XATTR_SIZE(le32_to_cpu(entry->e_value_size)); ->As entry is incorrect, then 'free' may be negative ext4_update_inline_data value = kzalloc(len, GFP_NOFS); -> len is unsigned int, maybe very large, then trigger warning when 'kzalloc()'

To resolve the above issue we need to update 'i_inline_off' after 'ext4_xattr_shift_entries()'. We do not need to set EXT4_STATE_MAY_INLINE_DATA flag here, since ext4_mark_inode_dirty() already sets this flag if needed. Setting EXT4_STATE_MAY_INLINE_DATA when it is needed may trigger a BUG_ON in ext4_writepages().

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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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
11th
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. 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 low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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

May 2, 2025

Last Modified

October 15, 2026

References (8)

Vendor Advisories for CVE-2023-53100(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-362.8.1.el9_32023-11-07redhat
linuxKernel @ 4.14.310 (fixes >=3.8.0)—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 (25 versions)
  • every version up to 5.10.178-1: fixed in 5.10.178-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.20-1: fixed in 6.1.20-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.20-1: fixed in 6.1.20-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.20-1: fixed in 6.1.20-1
—

Data Freshness Timeline

(refreshed 8× in last 7d / 36× 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 93 of 196 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. 7 repeat rows among the latest 100 are merged into the row they repeat. The 103 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2023-53100?
CVE-2023-53100 is a medium-severity vulnerability; its CVE record was published on May 2, 2025. In the Linux kernel, the following vulnerability has been resolved: ext4: fix WARNING in ext4_update_inline_data Syzbot found the following issue: EXT4-fs (loop0): mounted filesystem 00000000-0000-0000-0000-000000000000 without journal. Quota mode: none. fscrypt: AES-256-CTS-CBC using…
When was the CVE record for CVE-2023-53100 published?
The CVE record for CVE-2023-53100 was published on May 2, 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 October 15, 2026; the record at its source may have been updated since.
Is CVE-2023-53100 actively exploited?
CVE-2023-53100 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (11th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-53100?
CVE-2023-53100 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2023-53100?
A fix for CVE-2023-53100 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-53100 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-53100

Explore →

Is Your Infrastructure Affected by CVE-2023-53100?

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

Book a Demo →Browse All CVEs