CVE-2023-53348

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-09-17. 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-59978 (ENISA EUVD) · GHSA-vmvh-gj86-w48f (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:

btrfs: fix deadlock when aborting transaction during relocation with scrub

Before relocating a block group we pause scrub, then do the relocation and then unpause scrub. The relocation process requires starting and committing a transaction, and if we have a failure in the critical section of the transaction commit path (transaction state >= TRANS_STATE_COMMIT_START), we will deadlock if there is a paused scrub.

That results in stack traces like the following:

[42.479] BTRFS info (device sdc): relocating block group 53876686848 flags metadata|raid6 [42.936] BTRFS warning (device sdc): Skipping commit of aborted transaction. [42.936] ------------[ cut here ]------------ [42.936] BTRFS: Transaction aborted (error -28) [42.936] WARNING: CPU: 11 PID: 346822 at fs/btrfs/transaction.c:1977 btrfs_commit_transaction+0xcc8/0xeb0 [btrfs] [42.936] Modules linked in: dm_flakey dm_mod loop btrfs (...) [42.936] CPU: 11 PID: 346822 Comm: btrfs Tainted: G W 6.3.0-rc2-btrfs-next-127+ #1 [42.936] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014 [42.936] RIP: 0010:btrfs_commit_transaction+0xcc8/0xeb0 [btrfs] [42.936] Code: ff ff 45 8b (...) [42.936] RSP: 0018:ffffb58649633b48 EFLAGS: 00010282 [42.936] RAX: 0000000000000000 RBX: ffff8be6ef4d5bd8 RCX: 0000000000000000 [42.936] RDX: 0000000000000002 RSI: ffffffffb35e7782 RDI: 00000000ffffffff [42.936] RBP: ffff8be6ef4d5c98 R08: 0000000000000000 R09: ffffb586496339e8 [42.936] R10: 0000000000000001 R11: 0000000000000001 R12: ffff8be6d38c7c00 [42.936] R13: 00000000ffffffe4 R14: ffff8be6c268c000 R15: ffff8be6ef4d5cf0 [42.936] FS: 00007f381a82b340(0000) GS:ffff8beddfcc0000(0000) knlGS:0000000000000000 [42.936] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [42.936] CR2: 00007f1e35fb7638 CR3: 0000000117680006 CR4: 0000000000370ee0 [42.936] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [42.936] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [42.936] Call Trace: [42.936] [42.936] ? start_transaction+0xcb/0x610 [btrfs] [42.936] prepare_to_relocate+0x111/0x1a0 [btrfs] [42.936] relocate_block_group+0x57/0x5d0 [btrfs] [42.936] ? btrfs_wait_nocow_writers+0x25/0xb0 [btrfs] [42.936] btrfs_relocate_block_group+0x248/0x3c0 [btrfs] [42.936] ? __pfx_autoremove_wake_function+0x10/0x10 [42.936] btrfs_relocate_chunk+0x3b/0x150 [btrfs] [42.936] btrfs_balance+0x8ff/0x11d0 [btrfs] [42.936] ? __kmem_cache_alloc_node+0x14a/0x410 [42.936] btrfs_ioctl+0x2334/0x32c0 [btrfs] [42.937] ? mod_objcg_state+0xd2/0x360 [42.937] ? refill_obj_stock+0xb0/0x160 [42.937] ? seq_release+0x25/0x30 [42.937] ? __rseq_handle_notify_resume+0x3b5/0x4b0 [42.937] ? percpu_counter_add_batch+0x2e/0xa0 [42.937] ? __x64_sys_ioctl+0x88/0xc0 [42.937] __x64_sys_ioctl+0x88/0xc0 [42.937] do_syscall_64+0x38/0x90 [42.937] entry_SYSCALL_64_after_hwframe+0x72/0xdc [42.937] RIP: 0033:0x7f381a6ffe9b [42.937] Code: 00 48 89 44 24 (...) [42.937] RSP: 002b:00007ffd45ecf060 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 [42.937] RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007f381a6ffe9b [42.937] RDX: 00007ffd45ecf150 RSI: 00000000c4009420 RDI: 0000000000000003 [42.937] RBP: 0000000000000003 R08: 0000000000000013 R09: 0000000000000000 [42.937] R10: 00007f381a60c878 R11: 0000000000000246 R12: 00007ffd45ed0423 [42.937] R13: 00007ffd45ecf150 R14: 0000000000000000 R15: 00007ffd45ecf148 [42.937] [42.937] ---[ end trace 0000000000000000 ]--- [42.937] BTRFS: error (device sdc: state A) in cleanup_transaction:1977: errno=-28 No space left [59.196] INFO: task btrfs:346772 blocked for more than 120 seconds. [59.196] Tainted: G W 6.3.0-rc2-btrfs-next-127+ #1 [59.196] "echo 0 > /proc/sys/kernel/hung_ ---truncated---

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.2%
EPSS %ILE
4th
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 (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

September 17, 2025

Last Modified

January 14, 2026

Vendor Advisories for CVE-2023-53348(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 / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 6.1.23 (fixes >=4.3.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 ... 7.2~rc5-1~exp1 (499 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.25-1: fixed in 6.1.25-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.25-1: fixed in 6.1.25-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.25-1: fixed in 6.1.25-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 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 189 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 97 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.2% · 4th percentile
  2. 2026-11-01 16:31 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  3. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  4. 2026-10-30 16:31 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  5. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  6. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  7. 2026-10-27 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  8. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  9. 2026-10-25 17:28 UTCEG score recompute
  10. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  11. 2026-10-24 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  12. 2026-10-24 11:36 UTCEG score recompute
  13. 2026-10-24 11:36 UTCGHSA enrichmentGHSA-vmvh-gj86-w48f · GitHub CVSS 5.5
  14. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  15. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  16. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  17. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  18. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  19. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  20. 2026-10-18 07:41 UTCEG score recompute
  21. 2026-10-17 16:30 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  22. 2026-10-16 16:36 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  23. 2026-10-15 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  24. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  25. 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.2% · 4th percentile
Show 67 more
  1. 2026-10-12 18:12 UTCEG score recompute
  2. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  3. 2026-10-11 21:38 UTCEG score recompute
  4. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  5. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  6. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  7. 2026-10-08 17:06 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  8. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  9. 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  10. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  11. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  12. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  13. 2026-10-02 05:10 UTCOSV refresh
  14. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  15. 2026-09-30 16:37 UTCEG score recompute
  16. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  17. 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  18. 2026-09-28 13:49 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  19. 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  20. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  21. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  22. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  23. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  24. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  25. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  26. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  27. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  28. 2026-09-13 00:36 UTCOSV refresh
  29. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  30. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  31. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  32. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  33. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  34. 2026-09-05 15:26 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  35. 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  36. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  37. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  38. 2026-09-01 04:36 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  39. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  40. 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  41. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  42. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  43. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  44. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  45. 2026-08-25 03:56 UTCOSV refresh
  46. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  47. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  48. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  49. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  50. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  51. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  52. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  53. 2026-08-15 01:28 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  54. 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  55. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  56. 2026-08-11 13:40 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  57. 2026-08-10 23:58 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  58. 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  59. 2026-08-08 21:19 UTCOSV refresh
  60. 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  61. 2026-08-07 16:25 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  62. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  63. 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  64. 2026-08-04 10:36 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  65. 2026-08-03 10:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  66. 2026-08-02 02:25 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  67. 2026-08-01 04:14 UTCEPSS rescoreEPSS 0.1% · 3rd percentile

Frequently asked(5)

What is CVE-2023-53348?
CVE-2023-53348 is a medium-severity vulnerability; its CVE record was published on September 17, 2025. In the Linux kernel, the following vulnerability has been resolved: btrfs: fix deadlock when aborting transaction during relocation with scrub Before relocating a block group we pause scrub, then do the relocation and then unpause scrub. The relocation process requires starting and committing a…
When was the CVE record for CVE-2023-53348 published?
The CVE record for CVE-2023-53348 was published on September 17, 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 January 14, 2026; the record at its source may have been updated since.
Is CVE-2023-53348 actively exploited?
CVE-2023-53348 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-53348?
CVE-2023-53348 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2023-53348?
A fix for CVE-2023-53348 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-53348 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-53348

Explore →

Is Your Infrastructure Affected by CVE-2023-53348?

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