CVE-2023-52900

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2024-08-21. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

nilfs2: fix general protection fault in nilfs_btree_insert()

If nilfs2 reads a corrupted disk image and tries to reads a b-tree node block by calling __nilfs_btree_get_block() against an invalid virtual block address, it returns -ENOENT because conversion of the virtual block address to a disk block address fails. However, this return value is the same as the internal code that b-tree lookup routines return to indicate that the block being searched does not exist, so functions that operate on that b-tree may misbehave.

When nilfs_btree_insert() receives this spurious 'not found' code from nilfs_btree_do_lookup(), it misunderstands that the 'not found' check was successful and continues the insert operation using incomplete lookup path data, causing the following crash:

general protection fault, probably for non-canonical address 0xdffffc0000000005: 0000 [#1] PREEMPT SMP KASAN KASAN: null-ptr-deref in range [0x0000000000000028-0x000000000000002f] ... RIP: 0010:nilfs_btree_get_nonroot_node fs/nilfs2/btree.c:418 [inline] RIP: 0010:nilfs_btree_prepare_insert fs/nilfs2/btree.c:1077 [inline] RIP: 0010:nilfs_btree_insert+0x6d3/0x1c10 fs/nilfs2/btree.c:1238 Code: bc 24 80 00 00 00 4c 89 f8 48 c1 e8 03 42 80 3c 28 00 74 08 4c 89 ff e8 4b 02 92 fe 4d 8b 3f 49 83 c7 28 4c 89 f8 48 c1 e8 03 <42> 80 3c 28 00 74 08 4c 89 ff e8 2e 02 92 fe 4d 8b 3f 49 83 c7 02 ... Call Trace: nilfs_bmap_do_insert fs/nilfs2/bmap.c:121 [inline] nilfs_bmap_insert+0x20d/0x360 fs/nilfs2/bmap.c:147 nilfs_get_block+0x414/0x8d0 fs/nilfs2/inode.c:101 __block_write_begin_int+0x54c/0x1a80 fs/buffer.c:1991 __block_write_begin fs/buffer.c:2041 [inline] block_write_begin+0x93/0x1e0 fs/buffer.c:2102 nilfs_write_begin+0x9c/0x110 fs/nilfs2/inode.c:261 generic_perform_write+0x2e4/0x5e0 mm/filemap.c:3772 __generic_file_write_iter+0x176/0x400 mm/filemap.c:3900 generic_file_write_iter+0xab/0x310 mm/filemap.c:3932 call_write_iter include/linux/fs.h:2186 [inline] new_sync_write fs/read_write.c:491 [inline] vfs_write+0x7dc/0xc50 fs/read_write.c:584 ksys_write+0x177/0x2a0 fs/read_write.c:637 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 ...

This patch fixes the root cause of this problem by replacing the error code that __nilfs_btree_get_block() returns on block address conversion failure from -ENOENT to another internal code -EINVAL which means that the b-tree metadata is corrupted.

By returning -EINVAL, it propagates without glitches, and for all relevant b-tree operations, functions in the upper bmap layer output an error message indicating corrupted b-tree metadata via nilfs_bmap_convert_error(), and code -EIO will be eventually returned as it should be.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
25(Track)
EG Risk 25/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
15%
KEV
Not listed

Published

August 21, 2024

Last Modified

September 13, 2024

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 4.14.304osv

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 rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (25 versions)5.10.178-1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.8-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.1.8-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.1.8-1

Data Freshness Timeline

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

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 159 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2023-52900?
CVE-2023-52900 is a medium vulnerability published on August 21, 2024. In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix general protection fault in nilfsbtreeinsert() If nilfs2 reads a corrupted disk image and tries to reads a b-tree node block by calling nilfsbtreeget_block() against an invalid virtual block address, it returns -ENOENT…
When was CVE-2023-52900 disclosed?
CVE-2023-52900 was first published in the National Vulnerability Database on August 21, 2024, with the most recent update on September 13, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-52900 actively exploited?
CVE-2023-52900 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 84.5% of all scored CVEs.
What is the CVSS score of CVE-2023-52900?
CVE-2023-52900 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2023-52900?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-52900, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2023-52900?

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