CVE-2023-53243

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-15. 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-59841 (ENISA EUVD) · GHSA-hcgh-mwq2-gxfm (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: add handling for RAID1C23/DUP to btrfs_reduce_alloc_profile

Callers of btrfs_reduce_alloc_profile expect it to return exactly one allocation profile flag, and failing to do so may ultimately result in a WARN_ON and remount-ro when allocating new blocks, like the below transaction abort on 6.1.

btrfs_reduce_alloc_profile has two ways of determining the profile, first it checks if a conversion balance is currently running and uses the profile we're converting to. If no balance is currently running, it returns the max-redundancy profile which at least one block in the selected block group has.

This works by simply checking each known allocation profile bit in redundancy order. However, btrfs_reduce_alloc_profile has not been updated as new flags have been added - first with the DUP profile and later with the RAID1C34 profiles.

Because of the way it checks, if we have blocks with different profiles and at least one is known, that profile will be selected. However, if none are known we may return a flag set with multiple allocation profiles set.

This is currently only possible when a balance from one of the three unhandled profiles to another of the unhandled profiles is canceled after allocating at least one block using the new profile.

In that case, a transaction abort like the below will occur and the filesystem will need to be mounted with -o skip_balance to get it mounted rw again (but the balance cannot be resumed without a similar abort).

[770.648] ------------[ cut here ]------------ [770.648] BTRFS: Transaction aborted (error -22) [770.648] WARNING: CPU: 43 PID: 1159593 at fs/btrfs/extent-tree.c:4122 find_free_extent+0x1d94/0x1e00 [btrfs] [770.648] CPU: 43 PID: 1159593 Comm: btrfs Tainted: G W 6.1.0-0.deb11.7-powerpc64le #1 Debian 6.1.20-2~bpo11+1a~test [770.648] Hardware name: T2P9D01 REV 1.00 POWER9 0x4e1202 opal:skiboot-bc106a0 PowerNV [770.648] NIP: c00800000f6784fc LR: c00800000f6784f8 CTR: c000000000d746c0 [770.648] REGS: c000200089afe9a0 TRAP: 0700 Tainted: G W (6.1.0-0.deb11.7-powerpc64le Debian 6.1.20-2~bpo11+1a~test) [770.648] MSR: 9000000002029033 CR: 28848282 XER: 20040000 [770.648] CFAR: c000000000135110 IRQMASK: 0 GPR00: c00800000f6784f8 c000200089afec40 c00800000f7ea800 0000000000000026 GPR04: 00000001004820c2 c000200089afea00 c000200089afe9f8 0000000000000027 GPR08: c000200ffbfe7f98 c000000002127f90 ffffffffffffffd8 0000000026d6a6e8 GPR12: 0000000028848282 c000200fff7f3800 5deadbeef0000122 c00000002269d000 GPR16: c0002008c7797c40 c000200089afef17 0000000000000000 0000000000000000 GPR20: 0000000000000000 0000000000000001 c000200008bc5a98 0000000000000001 GPR24: 0000000000000000 c0000003c73088d0 c000200089afef17 c000000016d3a800 GPR28: c0000003c7308800 c00000002269d000 ffffffffffffffea 0000000000000001 [770.648] NIP [c00800000f6784fc] find_free_extent+0x1d94/0x1e00 [btrfs] [770.648] LR [c00800000f6784f8] find_free_extent+0x1d90/0x1e00 [btrfs] [770.648] Call Trace: [770.648] [c000200089afec40] [c00800000f6784f8] find_free_extent+0x1d90/0x1e00 [btrfs] (unreliable) [770.648] [c000200089afed30] [c00800000f681398] btrfs_reserve_extent+0x1a0/0x2f0 [btrfs] [770.648] [c000200089afeea0] [c00800000f681bf0] btrfs_alloc_tree_block+0x108/0x670 [btrfs] [770.648] [c000200089afeff0] [c00800000f66bd68] __btrfs_cow_block+0x170/0x850 [btrfs] [770.648] [c000200089aff100] [c00800000f66c58c] btrfs_cow_block+0x144/0x288 [btrfs] [770.648] [c000200089aff1b0] [c00800000f67113c] btrfs_search_slot+0x6b4/0xcb0 [btrfs] [770.648] [c000200089aff2a0] [c00800000f679f60] lookup_inline_extent_backref+0x128/0x7c0 [btrfs] [770.648] [c000200089aff3b0] [c00800000f67b338] lookup_extent_backref+0x70/0x190 [btrfs] [770.648] [c000200089aff470] [c00800000f67b54c] __btrfs_free_extent+0xf4/0x1490 [btrfs] [770.648] [ ---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
5th
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 15, 2025

Last Modified

January 14, 2026

References (5)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 5.10.188 (fixes >=5.5.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 ... 5.10.92-2 (33 versions)
  • every version up to 5.10.191-1: fixed in 5.10.191-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.27-1 ... 6.1.38-4~bpo11+1 (8 versions)
  • every version up to 6.1.52-1: fixed in 6.1.52-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.4.4-1: fixed in 6.4.4-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.4.4-1: fixed in 6.4.4-1
—

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 93 of 191 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. 7 repeat rows among the latest 100 are merged into the row they repeat. The 98 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2023-53243?
CVE-2023-53243 is a medium-severity vulnerability; its CVE record was published on September 15, 2025. In the Linux kernel, the following vulnerability has been resolved: btrfs: add handling for RAID1C23/DUP to btrfs_reduce_alloc_profile Callers of btrfs_reduce_alloc_profile expect it to return exactly one allocation profile flag, and failing to do so may ultimately result in a WARN_ON and…
When was the CVE record for CVE-2023-53243 published?
The CVE record for CVE-2023-53243 was published on September 15, 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-53243 actively exploited?
CVE-2023-53243 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-53243?
CVE-2023-53243 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2023-53243?
A fix for CVE-2023-53243 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-53243

Explore →

Is Your Infrastructure Affected by CVE-2023-53243?

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

Book a Demo →Browse All CVEs