CVE Tools

CVE-2026-98245

btrfs: take commit root semaphore when iterating in mark_block_group_to_copy()

No known exploitation. EPSS puts it in the 6th percentile. Fixed versions are out.

Published Updated Sources: CVE.org, NVD

What to do

Find your product and version, then upgrade to the build on the right.

  • LinuxAffected: ≥ 78ce9fc269af6e69c1399ab910ba6bc81c934f67, < 8e2007b263ea250251ec3021a0a197da990ee1a8Upgrade to: 8e2007b263ea250251ec3021a0a197da990ee1a8Affected: ≥ 78ce9fc269af6e69c1399ab910ba6bc81c934f67, < 709f6a5e986535005110c6c69b322f63631cb200Upgrade to: 709f6a5e986535005110c6c69b322f63631cb200Affected: ≥ 78ce9fc269af6e69c1399ab910ba6bc81c934f67, < c32490c6d3f3a9f2d177d57c7eb8bbc347561d08Upgrade to: c32490c6d3f3a9f2d177d57c7eb8bbc347561d08Affected: ≥ 78ce9fc269af6e69c1399ab910ba6bc81c934f67, < 0594e3423f4ba3137c734371169491f9a98e9af4Upgrade to: 0594e3423f4ba3137c734371169491f9a98e9af4Stated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

What it is

From the CVE record

In the Linux kernel, the following vulnerability has been resolved: btrfs: take commit root semaphore when iterating in mark_block_group_to_copy() mark_block_group_to_copy() iterates over the commit root with skip_locking=true. A concurrent transaction commit can swap and free the commit root during iteration, causing use-after-free when accessing extent buffers. Fix it by using path->need_commit_sem to protect the commit root search.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS6th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.2% chance of exploitation activity in the next 30 days, which ranks it in the 6th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

2 events over 0 days, from the signal feeds we watch.

  1. Publishedrecord updated

Affected products

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Linux, not every advisory.