CVE-2023-52705

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 2024-05-21. 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-2023-57329 (ENISA EUVD) · GHSA-rwq9-67rv-755x (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.3%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

nilfs2: fix underflow in second superblock position calculations

Macro NILFS_SB2_OFFSET_BYTES, which computes the position of the second superblock, underflows when the argument device size is less than 4096 bytes. Therefore, when using this macro, it is necessary to check in advance that the device size is not less than a lower limit, or at least that underflow does not occur.

The current nilfs2 implementation lacks this check, causing out-of-bound block access when mounting devices smaller than 4096 bytes:

I/O error, dev loop0, sector 36028797018963960 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 NILFS (loop0): unable to read secondary superblock (blocksize = 1024)

In addition, when trying to resize the filesystem to a size below 4096 bytes, this underflow occurs in nilfs_resize_fs(), passing a huge number of segments to nilfs_sufile_resize(), corrupting parameters such as the number of segments in superblocks. This causes excessive loop iterations in nilfs_sufile_resize() during a subsequent resize ioctl, causing semaphore ns_segctor_sem to block for a long time and hang the writer thread:

INFO: task segctord:5067 blocked for more than 143 seconds. Not tainted 6.2.0-rc8-syzkaller-00015-gf6feea56f66d #0 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:segctord state:D stack:23456 pid:5067 ppid:2 flags:0x00004000 Call Trace: context_switch kernel/sched/core.c:5293 [inline] __schedule+0x1409/0x43f0 kernel/sched/core.c:6606 schedule+0xc3/0x190 kernel/sched/core.c:6682 rwsem_down_write_slowpath+0xfcf/0x14a0 kernel/locking/rwsem.c:1190 nilfs_transaction_lock+0x25c/0x4f0 fs/nilfs2/segment.c:357 nilfs_segctor_thread_construct fs/nilfs2/segment.c:2486 [inline] nilfs_segctor_thread+0x52f/0x1140 fs/nilfs2/segment.c:2570 kthread+0x270/0x300 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308 ... Call Trace: folio_mark_accessed+0x51c/0xf00 mm/swap.c:515 __nilfs_get_page_block fs/nilfs2/page.c:42 [inline] nilfs_grab_buffer+0x3d3/0x540 fs/nilfs2/page.c:61 nilfs_mdt_submit_block+0xd7/0x8f0 fs/nilfs2/mdt.c:121 nilfs_mdt_read_block+0xeb/0x430 fs/nilfs2/mdt.c:176 nilfs_mdt_get_block+0x12d/0xbb0 fs/nilfs2/mdt.c:251 nilfs_sufile_get_segment_usage_block fs/nilfs2/sufile.c:92 [inline] nilfs_sufile_truncate_range fs/nilfs2/sufile.c:679 [inline] nilfs_sufile_resize+0x7a3/0x12b0 fs/nilfs2/sufile.c:777 nilfs_resize_fs+0x20c/0xed0 fs/nilfs2/super.c:422 nilfs_ioctl_resize fs/nilfs2/ioctl.c:1033 [inline] nilfs_ioctl+0x137c/0x2440 fs/nilfs2/ioctl.c:1301 ...

This fixes these issues by inserting appropriate minimum device size checks or anti-underflow checks, depending on where the macro is used.

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.3%
EPSS %ILE
16th
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.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). 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, and whom BOD 26-04 binds: 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.

The score's inputs: 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

May 21, 2024

Last Modified

December 31, 2024

References (7)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 4.14.306 (fixes >=2.6.30)—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.15-1: fixed in 6.1.15-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.15-1: fixed in 6.1.15-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.15-1: fixed in 6.1.15-1
—

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2023-52705?
CVE-2023-52705 is a medium-severity vulnerability; its CVE record was published on May 21, 2024. In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix underflow in second superblock position calculations Macro NILFS_SB2_OFFSET_BYTES, which computes the position of the second superblock, underflows when the argument device size is less than 4096 bytes. Therefore, when…
When was the CVE record for CVE-2023-52705 published?
The CVE record for CVE-2023-52705 was published on May 21, 2024. 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 December 31, 2024; the record at its source may have been updated since.
Is CVE-2023-52705 actively exploited?
CVE-2023-52705 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (16th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-52705?
CVE-2023-52705 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2023-52705?
A fix for CVE-2023-52705 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2023-52705?

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

Book a Demo →Browse All CVEs