CVE-2023-52810

HIGHNVD 8.48.4—
EchelonGraph scoreMEDIUM confidence

Score 8.4 from GitHub Security Advisory (severity: HIGH) published 2024-05-21. NVD baseline CVSS 8.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
8.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.4Exploit: 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:

fs/jfs: Add check for negative db_l2nbperpage

l2nbperpage is log2(number of blks per page), and the minimum legal value should be 0, not negative.

In the case of l2nbperpage being negative, an error will occur when subsequently used as shift exponent.

Syzbot reported this bug:

UBSAN: shift-out-of-bounds in fs/jfs/jfs_dmap.c:799:12 shift exponent -16777216 is negative

CVSS v3
8.4
EG Score
8.4(medium)
EG Risk
38(Track)
EG Risk 38/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
Severity84% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
17%
KEV
Not listed

Published

May 21, 2024

Last Modified

August 5, 2026

Advisory Details (9)

Auto-updated Aug 4, 2026
No patch confirmed yet.
generic

fs/jfs: Add check for negative db_l2nbperpage - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/525b861a008143048535011f3816d407940f4bfa
generic

fs/jfs: Add check for negative db_l2nbperpage - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1a7c53fdea1d189087544d9a606d249e93c4934b
generic

fs/jfs: Add check for negative db_l2nbperpage - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/491085258185ffc4fb91555b0dba895fe7656a45
generic

fs/jfs: Add check for negative db_l2nbperpage - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0cb567e727339a192f9fd0db00781d73a91d15a6
generic

fs/jfs: Add check for negative db_l2nbperpage - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5f148b16972e5f4592629b244d5109b15135f53f
generic

fs/jfs: Add check for negative db_l2nbperpage - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/524b4f203afcf87accfe387e846f33f916f0c907
generic

fs/jfs: Add check for negative db_l2nbperpage - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a81a56b4cbe3142cc99f6b98e8f9b3a631c768e1
generic

fs/jfs: Add check for negative db_l2nbperpage - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8f2964df6bfce9d92d81ca552010b8677af8d9dc
generic

fs/jfs: Add check for negative db_l2nbperpage - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/cc61fcf7d1c99f148fe8ddfb5c6ed0bb75861f01

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 4.14.331—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 rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (35 versions)5.10.205-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.27-1 ... 6.1.55-1~bpo11+1 (11 versions)6.1.64-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—6.6.8-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—6.6.8-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 36× 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 138 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2023-52810?
CVE-2023-52810 is a high vulnerability published on May 21, 2024. In the Linux kernel, the following vulnerability has been resolved: fs/jfs: Add check for negative db_l2nbperpage l2nbperpage is log2(number of blks per page), and the minimum legal value should be 0, not negative. In the case of l2nbperpage being negative, an error will occur when subsequently…
When was CVE-2023-52810 disclosed?
CVE-2023-52810 was first published in the National Vulnerability Database on May 21, 2024, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-52810 actively exploited?
CVE-2023-52810 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 82.8% of all scored CVEs.
What is the CVSS score of CVE-2023-52810?
CVE-2023-52810 has a CVSS v3 base score of 8.4 (NVD).
How do I remediate CVE-2023-52810?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-52810, 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-52810

Explore →

Is Your Infrastructure Affected by CVE-2023-52810?

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

Start Free Scan →Browse All CVEs