Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2021-47189btrfs: fix memory ordering between normal and ordered work functions

Description

In the Linux kernel, the following vulnerability has been resolved: btrfs: fix memory ordering between normal and ordered work functions Ordered work functions aren't guaranteed to be handled by the same thread which executed the normal work functions. The only way execution between normal/ordered functions is synchronized is via the WORK_DONE_BIT, unfortunately the used bitops don't guarantee any ordering whatsoever. This manifested as seemingly inexplicable crashes on ARM64, where async_chunk::inode is seen as non-null in async_cow_submit which causes submit_compressed_extents to be called and crash occurs because async_chunk::inode suddenly became NULL. The call trace was similar to: pc : submit_compressed_extents+0x38/0x3d0 lr : async_cow_submit+0x50/0xd0 sp : ffff800015d4bc20 <registers omitted for brevity> Call trace: submit_compressed_extents+0x38/0x3d0 async_cow_submit+0x50/0xd0 run_ordered_work+0xc8/0x280 btrfs_work_helper+0x98/0x250 process_one_work+0x1f0/0x4ac worker_thread+0x188/0x504 kthread+0x110/0x114 ret_from_fork+0x10/0x18 Fix this by adding respective barrier calls which ensure that all accesses preceding setting of WORK_DONE_BIT are strictly ordered before setting the flag. At the same time add a read barrier after reading of WORK_DONE_BIT in run_ordered_work which ensures all subsequent loads would be strictly ordered after reading the bit. This in turn ensures are all accesses before WORK_DONE_BIT are going to be strictly ordered before any access that can occur in ordered_func.

Timeline

  1. ID reserved

    By Linux

  2. · 16 days later

    Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2021-47189, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CISA-ADPADP (enrichment)3.1Medium6.3CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.67% · top 47% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 08a9ff3264181986d1d692a4e6fce3669700c9f8 – < bd660a20fea3ec60a49709ef5360f145ec0fe779
    • affected 08a9ff3264181986d1d692a4e6fce3669700c9f8 – < 637d652d351fd4f263ef302dc52f3971d314e500
    • affected 08a9ff3264181986d1d692a4e6fce3669700c9f8 – < 804a9d239ae9cbe88e861a7cd62319cc6ec7b136
    • affected 08a9ff3264181986d1d692a4e6fce3669700c9f8 – < ed058d735a70f4b063323f1a7bb33cda0f987513
    • affected 08a9ff3264181986d1d692a4e6fce3669700c9f8 – < 670f6b3867c8f0f11e5097f353b164cecfec6179
    • affected 08a9ff3264181986d1d692a4e6fce3669700c9f8 – < 6adbc07ebcaf8bead08b21687d49e0fc94400987
    • affected 08a9ff3264181986d1d692a4e6fce3669700c9f8 – < 47e6f9f69153247109042010f3a77579e9dc61ff
    • affected 08a9ff3264181986d1d692a4e6fce3669700c9f8 – < 45da9c1767ac31857df572f0a909fbe88fd5a7e9
  • Linux · Linux

    • affected 3.15
    • unaffected < 3.15
    • unaffected 4.4.293 – ≤ 4.4.*
    • unaffected 4.9.291 – ≤ 4.9.*
    • unaffected 4.14.256 – ≤ 4.14.*
    • unaffected 4.19.218 – ≤ 4.19.*
    • unaffected 5.4.162 – ≤ 5.4.*
    • unaffected 5.10.82 – ≤ 5.10.*
    • unaffected 5.15.5 – ≤ 5.15.*
    • unaffected 5.16 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2021-47189 badge
[![CVE-2021-47189](https://cveledger.app/badge/CVE-2021-47189.svg)](https://cveledger.app/cve/CVE-2021-47189)

Record last updated .