CVE-2026-45934

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 2026-05-27. 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-2026-32218 (ENISA EUVD) · GHSA-62rp-r79h-7q8x (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 EEXIST abort due to non-consecutive gaps in chunk allocation

I have been observing a number of systems aborting at insert_dev_extents() in btrfs_create_pending_block_groups(). The following is a sample stack trace of such an abort coming from forced chunk allocation (typically behind CONFIG_BTRFS_EXPERIMENTAL) but this can theoretically happen to any DUP chunk allocation.

[81.801] ------------[ cut here ]------------ [81.801] BTRFS: Transaction aborted (error -17) [81.801] WARNING: fs/btrfs/block-group.c:2876 at btrfs_create_pending_block_groups+0x721/0x770 [btrfs], CPU#1: bash/319 [81.802] Modules linked in: virtio_net btrfs xor zstd_compress raid6_pq null_blk [81.803] CPU: 1 UID: 0 PID: 319 Comm: bash Kdump: loaded Not tainted 6.19.0-rc6+ #319 NONE [81.803] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Arch Linux 1.17.0-2-2 04/01/2014 [81.804] RIP: 0010:btrfs_create_pending_block_groups+0x723/0x770 [btrfs] [81.806] RSP: 0018:ffffa36241a6bce8 EFLAGS: 00010282 [81.806] RAX: 000000000000000d RBX: ffff8e699921e400 RCX: 0000000000000000 [81.807] RDX: 0000000002040001 RSI: 00000000ffffffef RDI: ffffffffc0608bf0 [81.807] RBP: 00000000ffffffef R08: ffff8e69830f6000 R09: 0000000000000007 [81.808] R10: ffff8e699921e5e8 R11: 0000000000000000 R12: ffff8e6999228000 [81.808] R13: ffff8e6984d82000 R14: ffff8e69966a69c0 R15: ffff8e69aa47b000 [81.809] FS: 00007fec6bdd9740(0000) GS:ffff8e6b1b379000(0000) knlGS:0000000000000000 [81.809] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [81.810] CR2: 00005604833670f0 CR3: 0000000116679000 CR4: 00000000000006f0 [81.810] Call Trace: [81.810] [81.810] __btrfs_end_transaction+0x3e/0x2b0 [btrfs] [81.811] btrfs_force_chunk_alloc_store+0xcd/0x140 [btrfs] [81.811] kernfs_fop_write_iter+0x15f/0x240 [81.812] vfs_write+0x264/0x500 [81.812] ksys_write+0x6c/0xe0 [81.812] do_syscall_64+0x66/0x770 [81.812] entry_SYSCALL_64_after_hwframe+0x76/0x7e [81.813] RIP: 0033:0x7fec6be66197 [81.814] RSP: 002b:00007fffb159dd30 EFLAGS: 00000202 ORIG_RAX: 0000000000000001 [81.815] RAX: ffffffffffffffda RBX: 00007fec6bdd9740 RCX: 00007fec6be66197 [81.815] RDX: 0000000000000002 RSI: 0000560483374f80 RDI: 0000000000000001 [81.816] RBP: 0000560483374f80 R08: 0000000000000000 R09: 0000000000000000 [81.816] R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000002 [81.817] R13: 00007fec6bfb85c0 R14: 00007fec6bfb5ee0 R15: 00005604833729c0 [81.817] [81.817] irq event stamp: 20039 [81.818] hardirqs last enabled at (20047): [] __up_console_sem+0x52/0x60 [81.818] hardirqs last disabled at (20056): [] __up_console_sem+0x37/0x60 [81.819] softirqs last enabled at (19470): [] __irq_exit_rcu+0x96/0xc0 [81.819] softirqs last disabled at (19463): [] __irq_exit_rcu+0x96/0xc0 [81.820] ---[ end trace 0000000000000000 ]--- [81.820] BTRFS: error (device dm-7 state A) in btrfs_create_pending_block_groups:2876: errno=-17 Object already exists

Inspecting these aborts with drgn, I observed a pattern of overlapping chunk_maps. Note how stripe 1 of the first chunk overlaps in physical address with stripe 0 of the second chunk.

Physical Start Physical End Length Logical Type Stripe ---------------------------------------------------------------------------------------------------- 0x0000000102500000 0x0000000142500000 1.0G 0x0000000641d00000 META|DUP 0/2 0x0000000142500000 0x0000000182500000 1.0G 0x0000000641d00000 META|DUP 1/2 0x0000000142500000 0x0000000182500000 1.0G 0x0000000601d00000 META|DUP 0/2 0x0000000182500000 0x00000001c2500000 1.0G 0x0000000601d00000 META|DUP 1/2

Now how could this possibly happen? All chunk allocation is ---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 BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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. 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 low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 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 low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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)14 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's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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 27, 2026

Last Modified

October 30, 2026

Advisory Details (3)

Auto-updated Jun 24, 2026
Patch available.
Web page

btrfs: fix EEXIST abort due to non-consecutive gaps in chunk allocation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b14c5e04bd0f722ed631845599d52d03fcae1bc1
Web page

btrfs: fix EEXIST abort due to non-consecutive gaps in chunk allocation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7d4eadee7042d27fcea659fcdd738f463a7d2e70
Web page

btrfs: fix EEXIST abort due to non-consecutive gaps in chunk allocation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/156cac365e27a82b64ae510c5f463fd81f0265b1

Vendor Advisories for CVE-2026-45934(2)

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

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 6.18.14 (fixes >=4.1.0)—osv
linuxKernel @ 6.6.160 (fixes >=4.1.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 (496 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (358 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (181 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (104 versions)
  • every version up to 6.18.14-1: fixed in 6.18.14-1
—

Data Freshness Timeline

(refreshed 7× in last 7d / 47× 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 100 of 249 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. None are among the latest 100 rows. The 149 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-45934?
CVE-2026-45934 is a medium-severity vulnerability; its CVE record was published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: btrfs: fix EEXIST abort due to non-consecutive gaps in chunk allocation I have been observing a number of systems aborting at insert_dev_extents() in btrfs_create_pending_block_groups(). The following is a sample stack trace of…
When was the CVE record for CVE-2026-45934 published?
The CVE record for CVE-2026-45934 was published on May 27, 2026. 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 October 30, 2026; the record at its source may have been updated since.
Is CVE-2026-45934 actively exploited?
CVE-2026-45934 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-2026-45934?
CVE-2026-45934 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-45934?
A fix for CVE-2026-45934 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-45934 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-2026-45934

Explore →

Is Your Infrastructure Affected by CVE-2026-45934?

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

Book a Demo →Browse All CVEs