CVE-2023-54182

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2025-12-30. the CNA's CVSS baseline 7.1; sources differ by 0.0.

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

f2fs: fix to check readonly condition correctly

With below case, it can mount multi-device image w/ rw option, however one of secondary device is set as ro, later update will cause panic, so let's introduce f2fs_dev_is_readonly(), and check multi-devices rw status in f2fs_remount() w/ it in order to avoid such inconsistent mount status.

mkfs.f2fs -c /dev/zram1 /dev/zram0 -f blockdev --setro /dev/zram1 mount -t f2fs dev/zram0 /mnt/f2fs mount: /mnt/f2fs: WARNING: source write-protected, mounted read-only. mount -t f2fs -o remount,rw mnt/f2fs dd if=/dev/zero of=/mnt/f2fs/file bs=1M count=8192

kernel BUG at fs/f2fs/inline.c:258! RIP: 0010:f2fs_write_inline_data+0x23e/0x2d0 [f2fs] Call Trace: f2fs_write_single_data_page+0x26b/0x9f0 [f2fs] f2fs_write_cache_pages+0x389/0xa60 [f2fs] __f2fs_write_data_pages+0x26b/0x2d0 [f2fs] f2fs_write_data_pages+0x2e/0x40 [f2fs] do_writepages+0xd3/0x1b0 __writeback_single_inode+0x5b/0x420 writeback_sb_inodes+0x236/0x5a0 __writeback_inodes_wb+0x56/0xf0 wb_writeback+0x2a3/0x490 wb_do_writeback+0x2b2/0x330 wb_workfn+0x6a/0x260 process_one_work+0x270/0x5e0 worker_thread+0x52/0x3e0 kthread+0xf4/0x120 ret_from_fork+0x29/0x50

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

Published

December 30, 2025

Last Modified

August 5, 2026

Advisory Details (4)

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

f2fs: fix to check readonly condition correctly - kernel/git/stable/linux.git - Linux kernel stable tree

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

f2fs: fix to check readonly condition correctly - kernel/git/stable/linux.git - Linux kernel stable tree

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

f2fs: fix to check readonly condition correctly - kernel/git/stable/linux.git - Linux kernel stable tree

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

f2fs: fix to check readonly condition correctly - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2023-54182(1)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.15.113osv

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 ... 7.2~rc5-1~exp1 (498 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.27-16.1.37-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.3.7-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.3.7-1

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2023-54182?
CVE-2023-54182 is a high vulnerability published on December 30, 2025. In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to check readonly condition correctly With below case, it can mount multi-device image w/ rw option, however one of secondary device is set as ro, later update will cause panic, so let's introduce f2fsdevis_readonly(),…
When was CVE-2023-54182 disclosed?
CVE-2023-54182 was first published in the National Vulnerability Database on December 30, 2025, 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-54182 actively exploited?
CVE-2023-54182 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 95.8% of all scored CVEs.
What is the CVSS score of CVE-2023-54182?
CVE-2023-54182 has a CVSS v4.0 base score of 7.1 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2023-54182?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-54182, 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-54182

Explore →

Is Your Infrastructure Affected by CVE-2023-54182?

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