nday
CVE-2021-47508

btrfs: free exchange changeset on failures

Linux / Linux

Disclosed . nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it. Not in CISA KEV.

tags weakness typeresource exhaustion accesslocalno user interaction productLinux kernel product typeoperating system
why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

resource exhaustion
CWE-401, stated by NVD's analysts
local
AV:L in CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (CVSS 3.1) from NVD's analysts
no user interaction
UI:N in CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (CVSS 3.1) from NVD's analysts
Linux kernel
affected products in the CVE record: Linux · LinuxCPE names NVD's analysts give as vulnerable: o:linux:linux_kernel
operating system
affected products in the CVE record: Linux · LinuxCPE names NVD's analysts give as vulnerable: o:linux:linux_kernelthe product type of Linux kernel in nday's product registry
stage
DIS
disclosed
cvss
no score yet

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
2024-05-24T15:01Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
no record yet
KEVKEV
no record yet

Summary

In the Linux kernel, the following vulnerability has been resolved:

btrfs: free exchange changeset on failures

Fstests runs on my VMs have show several kmemleak reports like the following.

unreferenced object 0xffff88811ae59080 (size 64):
  comm "xfs_io", pid 12124, jiffies 4294987392 (age 6.368s)
  hex dump (first 32 bytes):
    00 c0 1c 00 00 00 00 00 ff cf 1c 00 00 00 00 00  ................
    90 97 e5 1a 81 88 ff ff 90 97 e5 1a 81 88 ff ff  ................
  backtrace:
    [<00000000ac0176d2>] ulist_add_merge+0x60/0x150 [btrfs]
    [<0000000076e9f312>] set_state_bits+0x86/0xc0 [btrfs]
    [<0000000014fe73d6>] set_extent_bit+0x270/0x690 [btrfs]
    [<000000004f675208>] set_record_extent_bits+0x19/0x20 [btrfs]
    [<00000000b96137b1>] qgroup_reserve_data+0x274/0x310 [btrfs]
    [<0000000057e9dcbb>] btrfs_check_data_free_space+0x5c/0xa0 [btrfs]
    [<0000000019c4511d>] btrfs_delalloc_reserve_space+0x1b/0xa0 [btrfs]
    [<000000006d37e007>] btrfs_dio_iomap_begin+0x415/0x970 [btrfs]
    [<00000000fb8a74b8>] iomap_iter+0x161/0x1e0
    [<0000000071dff6ff>] __iomap_dio_rw+0x1df/0x700
    [<000000002567ba53>] iomap_dio_rw+0x5/0x20
    [<0000000072e555f8>] btrfs_file_write_iter+0x290/0x530 [btrfs]
    [<000000005eb3d845>] new_sync_write+0x106/0x180
    [<000000003fb505bf>] vfs_write+0x24d/0x2f0
    [<000000009bb57d37>] __x64_sys_pwrite64+0x69/0xa0
    [<000000003eba3fdf>] do_syscall_64+0x43/0x90

In case brtfs_qgroup_reserve_data() or btrfs_delalloc_reserve_metadata() fail the allocated extent_changeset will not be freed.

So in btrfs_check_data_free_space() and btrfs_delalloc_reserve_space() free the allocated extent_changeset to get rid of the allocated memory.

The issue currently only happens in the direct IO write path, but only after 65b3c08606e5 ("btrfs: fix ENOSPC failure when attempting direct IO write into NOCOW range"), and also at defrag_one_locked_target(). Every other place is always calling extent_changeset_free() even if its call to btrfs_delalloc_reserve_space() or btrfs_check_data_free_space() has failed.

Original text of the CVE record (cvelist), shown as published.

Event log

+DISdisclosed

CVE record published by Linux.

src cvelist · nday , bulk import · raw
{
  "id": 253281,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2021-47508",
  "occurred_at": "2024-05-24T15:01:54.048Z",
  "observed_at": "2026-11-13T05:37:31.591644Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "ssvc": {
      "timestamp": "2024-09-10T15:35:39.656794Z",
      "automatable": "no",
      "exploitation": "none",
      "technical_impact": "partial"
    },
    "state": "PUBLISHED",
    "date_published": "2024-05-24T15:01:54.048Z",
    "assigner_short_name": "Linux"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.