CVE-2026-23214

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 (severity: MODERATE) published 2026-02-18. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2026-8015 (ENISA EUVD) · GHSA-vqcj-rgfw-jjcq (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: reject new transactions if the fs is fully read-only

[BUG] There is a bug report where a heavily fuzzed fs is mounted with all rescue mount options, which leads to the following warnings during unmount:

BTRFS: Transaction aborted (error -22) Modules linked in: CPU: 0 UID: 0 PID: 9758 Comm: repro.out Not tainted 6.19.0-rc5-00002-gb71e635feefc #7 PREEMPT(full) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 RIP: 0010:find_free_extent_update_loop fs/btrfs/extent-tree.c:4208 [inline] RIP: 0010:find_free_extent+0x52f0/0x5d20 fs/btrfs/extent-tree.c:4611 Call Trace: btrfs_reserve_extent+0x2cd/0x790 fs/btrfs/extent-tree.c:4705 btrfs_alloc_tree_block+0x1e1/0x10e0 fs/btrfs/extent-tree.c:5157 btrfs_force_cow_block+0x578/0x2410 fs/btrfs/ctree.c:517 btrfs_cow_block+0x3c4/0xa80 fs/btrfs/ctree.c:708 btrfs_search_slot+0xcad/0x2b50 fs/btrfs/ctree.c:2130 btrfs_truncate_inode_items+0x45d/0x2350 fs/btrfs/inode-item.c:499 btrfs_evict_inode+0x923/0xe70 fs/btrfs/inode.c:5628 evict+0x5f4/0xae0 fs/inode.c:837 __dentry_kill+0x209/0x660 fs/dcache.c:670 finish_dput+0xc9/0x480 fs/dcache.c:879 shrink_dcache_for_umount+0xa0/0x170 fs/dcache.c:1661 generic_shutdown_super+0x67/0x2c0 fs/super.c:621 kill_anon_super+0x3b/0x70 fs/super.c:1289 btrfs_kill_super+0x41/0x50 fs/btrfs/super.c:2127 deactivate_locked_super+0xbc/0x130 fs/super.c:474 cleanup_mnt+0x425/0x4c0 fs/namespace.c:1318 task_work_run+0x1d4/0x260 kernel/task_work.c:233 exit_task_work include/linux/task_work.h:40 [inline] do_exit+0x694/0x22f0 kernel/exit.c:971 do_group_exit+0x21c/0x2d0 kernel/exit.c:1112 __do_sys_exit_group kernel/exit.c:1123 [inline] __se_sys_exit_group kernel/exit.c:1121 [inline] __x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1121 x64_sys_call+0x2210/0x2210 arch/x86/include/generated/asm/syscalls_64.h:232 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xe8/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x44f639 Code: Unable to access opcode bytes at 0x44f60f. RSP: 002b:00007ffc15c4e088 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7 RAX: ffffffffffffffda RBX: 00000000004c32f0 RCX: 000000000044f639 RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000001 RBP: 0000000000000001 R08: ffffffffffffffc0 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 00000000004c32f0 R13: 0000000000000001 R14: 0000000000000000 R15: 0000000000000001

Since rescue mount options will mark the full fs read-only, there should be no new transaction triggered.

But during unmount we will evict all inodes, which can trigger a new transaction, and triggers warnings on a heavily corrupted fs.

[CAUSE] Btrfs allows new transaction even on a read-only fs, this is to allow log replay happen even on read-only mounts, just like what ext4/xfs do.

However with rescue mount options, the fs is fully read-only and cannot be remounted read-write, thus in that case we should also reject any new transactions.

[FIX] If we find the fs has rescue mount options, we should treat the fs as error, so that no new transaction can be started.

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
7th
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-11-05). 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

February 18, 2026

Last Modified

November 5, 2026

Advisory Details (3)

Auto-updated Aug 7, 2026
Patch available.
Web page

btrfs: reject new transactions if the fs is fully read-only - kernel/git/stable/linux.git - Linux kernel stable tree

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

btrfs: reject new transactions if the fs is fully read-only - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3228b2eceb6c3d7e237f8a5330113dbd164fb90d
Web page

btrfs: reject new transactions if the fs is fully read-only - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1972f44c189c8aacde308fa9284e474c1a5cbd9f

Vendor Advisories for CVE-2026-23214(2)

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

Patch Availability(11)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-6.8 (6.8.0-117.117) @ noble2026-10-30ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1059.65+fips1) @ noble2026-10-30ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-116.116+fips1) @ noble2026-10-30ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.8.0-1054.57~22.04.1) @ jammy2026-10-30ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1054.57.1) @ noble2026-10-30ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1024.24) @ noble2026-10-30ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1056.62) @ noble2026-10-30ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-10-30ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1059.65~22.04.1) @ jammy2026-10-30ubuntu
linuxKernel @ 6.12.70 (fixes >=5.11.0)—osv
linuxKernel @ 6.6.160 (fixes >=5.11.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

(3 across 3 ecosystems)
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.38-1 ... 6.12.73-1~bpo12+1 (12 versions)
  • every version up to 6.12.73-1: fixed in 6.12.73-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (100 versions)
  • every version up to 6.18.10-1: fixed in 6.18.10-1
—

Additional Vendor Advisories

(9)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 11× in last 7d / 55× 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 99 of 135 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 36 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-23214?
CVE-2026-23214 is a medium-severity vulnerability; its CVE record was published on February 18, 2026. In the Linux kernel, the following vulnerability has been resolved: btrfs: reject new transactions if the fs is fully read-only [BUG] There is a bug report where a heavily fuzzed fs is mounted with all rescue mount options, which leads to the following warnings during unmount: BTRFS: Transaction…
When was the CVE record for CVE-2026-23214 published?
The CVE record for CVE-2026-23214 was published on February 18, 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 November 5, 2026; the record at its source may have been updated since.
Is CVE-2026-23214 actively exploited?
CVE-2026-23214 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (7th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-23214?
CVE-2026-23214 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-23214?
A fix for CVE-2026-23214 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-23214 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-23214

Explore →

Is Your Infrastructure Affected by CVE-2026-23214?

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

Book a Demo →Browse All CVEs