Skip to content
Noroxi
CVE-2022-48901· NVD / CVE Program· CNA Linux

btrfs: do not start relocation until in progress drops are done

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 5e70bc827b563caf22e1203428cc3719643de5aa, 6599d5e8bd758d897fd2ef4dc388ae50278b1f7e, b4be6aefa73c9a6899ef3ba9c5faaa8a66e333ef.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 5e70bc827b563caf22e1203428cc3719643de5aa, 6599d5e8bd758d897fd2ef4dc388ae50278b1f7e, b4be6aefa73c9a6899ef3ba9c5faaa8a66e333ef or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

In the Linux kernel, the following vulnerability has been resolved: btrfs: do not start relocation until in progress drops are done We hit a bug with a recovering relocation on mount for one of our file systems in production. I reproduced this locally by injecting errors into snapshot delete with balance running at the same time. This presented as an error while looking up an extent item WARNING: CPU: 5 PID: 1501 at fs/btrfs/extent-tree.c:866 lookup_inline_extent_backref+0x647/0x680 CPU: 5 PID: 1501 Comm: btrfs-balance Not tainted 5.16.0-rc8+ #8 RIP: 0010:lookup_inline_extent_backref+0x647/0x680 RSP: 0018:ffffae0a023ab960 EFLAGS: 00010202 RAX: 0000000000000001 RBX: 0000000000000000 RCX: 0000000000000000 RDX: 0000000000000000 RSI: 000000000000000c RDI: 0000000000000000 RBP: ffff943fd2a39b60 R08: 0000000000000000 R09: 0000000000000001 R10: 0001434088152de0 R11: 0000000000000000 R12: 0000000001d05000 R13: ffff943fd2a39b60 R14: ffff943fdb96f2a0 R15: ffff9442fc923000 FS: 0000000000000000(0000) GS:ffff944e9eb40000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f1157b1fca8 CR3: 000000010f092000 CR4: 0000000000350ee0 Call Trace: <TASK> insert_inline_extent_backref+0x46/0xd0 __btrfs_inc_extent_ref.isra.0+0x5f/0x200 ? btrfs_merge_delayed_refs+0x164/0x190 __btrfs_run_delayed_refs+0x561/0xfa0 ? btrfs_search_slot+0x7b4/0xb30 ? btrfs_update_root+0x1a9/0x2c0 btrfs_run_delayed_refs+0x73/0x1f0 ? btrfs_update_root+0x1a9/0x2c0 btrfs_commit_transaction+0x50/0xa50 ? btrfs_update_reloc_root+0x122/0x220 prepare_to_merge+0x29f/0x320 relocate_block_group+0x2b8/0x550 btrfs_relocate_block_group+0x1a6/0x350 btrfs_relocate_chunk+0x27/0xe0 btrfs_balance+0x777/0xe60 balance_kthread+0x35/0x50 ? btrfs_balance+0xe60/0xe60 kthread+0x16b/0x190 ? set_kthread_struct+0x40/0x40 ret_from_fork+0x22/0x30 </TASK> Normally snapshot deletion and relocation are excluded from running at the same time by the fs_info->cleaner_mutex. However if we had a pending balance waiting to get the ->cleaner_mutex, and a snapshot deletion was running, and then the box crashed, we would come up in a state where we have a half deleted snapshot. Again, in the normal case the snapshot deletion needs to complete before relocation can start, but in this case relocation could very well start before the snapshot deletion completes, as we simply add the root to the dead roots list and wait for the next time the cleaner runs to clean up the snapshot. Fix this by setting a bit on the fs_info if we have any DEAD_ROOT's that had a pending drop_progress key. If they do then we know we were in the middle of the drop operation and set a flag on the fs_info. Then balance can wait until this flag is cleared to start up again. If there are DEAD_ROOT's that don't have a drop_progress set then we're safe to start balance right away as we'll be properly protected by the cleaner_mutex.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Aug 21, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 10th percentile
CWE
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2022-48901

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Port scanning: 5 full scans a day (members only)
  • Uptime monitoring: 1 site, instant email when it goes down
  • Verify your domain: subdomains and takeover risk scanned every week
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernelbefore 5.15.27
  • linux linux kernel5.16 and later · before 5.16.13
  • linux linux kernel5.17

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 3.10affected
    • 9d1a2a3ad59f7ae810bf04a5a05995bf2d79300c and later · before 6599d5e8bd758d897fd2ef4dc388ae50278b1f7eaffected · git
    • 9d1a2a3ad59f7ae810bf04a5a05995bf2d79300c and later · before 5e70bc827b563caf22e1203428cc3719643de5aaaffected · git
    • 9d1a2a3ad59f7ae810bf04a5a05995bf2d79300c and later · before b4be6aefa73c9a6899ef3ba9c5faaa8a66e333efaffected · git
    • before 3.10not affected · semver
    • 5.15.27 and later · up to and including 5.15.*not affected · semver
    • 5.16.13 and later · up to and including 5.16.*not affected · semver
    • 5.17 and laternot affected · original_commit_for_fix

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 5.16.14-15.16.14-1
SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSkernel-default-basebefore 5.3.18-150200.24.203.1.150200.9.105.15.3.18-150200.24.203.1.150200.9.105.1
SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSkernel-docsbefore 5.3.18-150200.24.203.15.3.18-150200.24.203.1
SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSkernel-obs-buildbefore 5.3.18-150200.24.203.15.3.18-150200.24.203.1
SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSkernel-preemptbefore 5.3.18-150200.24.203.15.3.18-150200.24.203.1
SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSkernel-sourcebefore 5.3.18-150200.24.203.15.3.18-150200.24.203.1
SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSkernel-symsbefore 5.3.18-150200.24.203.15.3.18-150200.24.203.1
SUSE:Linux Enterprise Live Patching 15 SP2kernel-defaultbefore 5.3.18-150200.24.203.15.3.18-150200.24.203.1
SUSE:Linux Enterprise Live Patching 15 SP2kernel-livepatch-SLE15-SP2_Update_52before 1-150200.5.3.11-150200.5.3.1
SUSE:Linux Enterprise Live Patching 15 SP5kernel-livepatch-SLE15-SP5_Update_20before 1-150500.11.3.11-150500.11.3.1
SUSE:Linux Enterprise Live Patching 15 SP5kernel-livepatch-SLE15-SP5_Update_20before 1-150500.11.3.11-150500.11.3.1
SUSE:Linux Enterprise Live Patching 15 SP5kernel-livepatch-SLE15-SP5-RT_Update_21before 1-150500.11.3.11-150500.11.3.1
SUSE:Linux Enterprise Live Patching 15 SP5kernel-livepatch-SLE15-SP5-RT_Update_21before 1-150500.11.3.11-150500.11.3.1
SUSE:Linux Enterprise Micro 5.5kernel-defaultbefore 5.14.21-150500.55.83.15.14.21-150500.55.83.1
SUSE:Linux Enterprise Micro 5.5kernel-defaultbefore 5.14.21-150500.55.83.15.14.21-150500.55.83.1
SUSE:Linux Enterprise Micro 5.5kernel-default-basebefore 5.14.21-150500.55.83.1.150500.6.37.15.14.21-150500.55.83.1.150500.6.37.1
SUSE:Linux Enterprise Micro 5.5kernel-default-basebefore 5.14.21-150500.55.83.1.150500.6.37.15.14.21-150500.55.83.1.150500.6.37.1
SUSE:Linux Enterprise Micro 5.5kernel-rtbefore 5.14.21-150500.13.73.15.14.21-150500.13.73.1
SUSE:Linux Enterprise Micro 5.5kernel-rtbefore 5.14.21-150500.13.73.15.14.21-150500.13.73.1
SUSE:Linux Enterprise Micro 5.5kernel-source-rtbefore 5.14.21-150500.13.73.15.14.21-150500.13.73.1
SUSE:Linux Enterprise Micro 5.5kernel-source-rtbefore 5.14.21-150500.13.73.15.14.21-150500.13.73.1
SUSE:Linux Enterprise Module for Basesystem 15 SP5kernel-64kbbefore 5.14.21-150500.55.83.15.14.21-150500.55.83.1
SUSE:Linux Enterprise Module for Basesystem 15 SP5kernel-64kbbefore 5.14.21-150500.55.83.15.14.21-150500.55.83.1
SUSE:Linux Enterprise Module for Basesystem 15 SP5kernel-sourcebefore 5.14.21-150500.55.83.15.14.21-150500.55.83.1

+19

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now
  • CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV
    83Now
  • CVE-2019-13272In the Linux kernel before 5.1.17, ptrace_link in kernel/ptrace.c mishandles the recording of the credentials of a process that wants to creKEV
    77This week
  • CVE-2013-6282The (1) get_user and (2) put_user API functions in the Linux kernel before 3.5.5 on the v6k and v7 ARM platforms do not validate certain addKEV
    77This week
  • CVE-2013-2094The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows loKEV
    77This week

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux5e70bc827b563caf22e1203428cc3719643de5aaVendor (CNA)
Linux Linux6599d5e8bd758d897fd2ef4dc388ae50278b1f7eVendor (CNA)
Linux Linuxb4be6aefa73c9a6899ef3ba9c5faaa8a66e333efVendor (CNA)
debian:linux5.16.14-1 · Debian:12Package registry (OSV)
opensuse:kernel-default5.14.21-150500.55.83.1 · openSUSE:Leap Micro 5.5Package registry (OSV)
opensuse:kernel-default-base5.14.21-150500.55.83.1.150500.6.37.1 · openSUSE:Leap Micro 5.5Package registry (OSV)
suse:kernel-64kb5.14.21-150500.55.83.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP5Package registry (OSV)
suse:kernel-azure5.14.21-150500.33.69.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP5Package registry (OSV)
suse:kernel-default5.14.21-150500.55.83.1 · SUSE:Linux Enterprise Micro 5.5Package registry (OSV)
suse:kernel-default5.3.18-150200.24.203.1 · SUSE:Linux Enterprise Live Patching 15 SP2Package registry (OSV)
suse:kernel-default-base5.14.21-150500.55.83.1.150500.6.37.1 · SUSE:Linux Enterprise Micro 5.5Package registry (OSV)
suse:kernel-default-base5.3.18-150200.24.203.1.150200.9.105.1 · SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSPackage registry (OSV)
suse:kernel-docs5.14.21-150500.55.83.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP5Package registry (OSV)
suse:kernel-docs5.3.18-150200.24.203.1 · SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSPackage registry (OSV)
suse:kernel-livepatch-SLE15-SP2_Update_521-150200.5.3.1 · SUSE:Linux Enterprise Live Patching 15 SP2Package registry (OSV)
suse:kernel-livepatch-SLE15-SP5_Update_201-150500.11.3.1 · SUSE:Linux Enterprise Live Patching 15 SP5Package registry (OSV)
suse:kernel-obs-build5.14.21-150500.55.83.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP5Package registry (OSV)
suse:kernel-obs-build5.3.18-150200.24.203.1 · SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSPackage registry (OSV)
suse:kernel-preempt5.3.18-150200.24.203.1 · SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSPackage registry (OSV)
suse:kernel-source5.14.21-150500.55.83.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP5Package registry (OSV)
suse:kernel-source5.3.18-150200.24.203.1 · SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSPackage registry (OSV)
suse:kernel-syms5.14.21-150500.55.83.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP5Package registry (OSV)
suse:kernel-syms5.3.18-150200.24.203.1 · SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSPackage registry (OSV)
suse:kernel-zfcpdump5.14.21-150500.55.83.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP5Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records