CVE-2021-47599

MEDIUMNVD 4.74.7
EchelonGraph scoreMEDIUM confidence

Score 4.7 from GitHub Security Advisory published 2024-06-19. NVD baseline CVSS 4.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
4.7
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.7Exploit: NoneExposed: 0

A fix is available — apply it.

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

btrfs: use latest_dev in btrfs_show_devname

The test case btrfs/238 reports the warning below:

WARNING: CPU: 3 PID: 481 at fs/btrfs/super.c:2509 btrfs_show_devname+0x104/0x1e8 [btrfs] CPU: 2 PID: 1 Comm: systemd Tainted: G W O 5.14.0-rc1-custom #72 Hardware name: QEMU QEMU Virtual Machine, BIOS 0.0.0 02/06/2015 Call trace: btrfs_show_devname+0x108/0x1b4 [btrfs] show_mountinfo+0x234/0x2c4 m_show+0x28/0x34 seq_read_iter+0x12c/0x3c4 vfs_read+0x29c/0x2c8 ksys_read+0x80/0xec __arm64_sys_read+0x28/0x34 invoke_syscall+0x50/0xf8 do_el0_svc+0x88/0x138 el0_svc+0x2c/0x8c el0t_64_sync_handler+0x84/0xe4 el0t_64_sync+0x198/0x19c

Reason: While btrfs_prepare_sprout() moves the fs_devices::devices into fs_devices::seed_list, the btrfs_show_devname() searches for the devices and found none, leading to the warning as in above.

Fix: latest_dev is updated according to the changes to the device list. That means we could use the latest_dev->name to show the device name in /proc/self/mounts, the pointer will be always valid as it's assigned before the device is deleted from the list in remove or replace. The RCU protection is sufficient as the device structure is freed after synchronization.

CVSS v3
4.7
EG Score
4.7(medium)
EG Risk
21(Track)
EG Risk 21/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity47% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
4.5%
KEV
Not listed

Published

June 19, 2024

Last Modified

November 21, 2024

Patch Availability(21)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-lts-xenial (4.4.0.278.284) @ xenial2026-05-23ubuntu
ubuntulinux-virtual-lts-xenial (4.4.0.278.312~14.04.1) @ trusty2026-05-23ubuntu
ubuntulinux-tools-fips (4.4.0.1122.123) @ xenial2026-05-23ubuntu
ubuntulinux-tools-ibm-edge (5.4.0.1102.107~18.04.1) @ bionic2026-05-23ubuntu
ubuntulinux-virtual-hwe-18.04-edge (5.4.0.227.219) @ focal2026-05-23ubuntu
ubuntulinux-tools-gcp-lts-20.04 (5.4.0.1159.161) @ focal2026-05-23ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1074 (5.4.0-1074.78) @ focal2026-05-23ubuntu
ubuntulinux-tools-aws-fips-5.4 (5.4.0.1155.102) @ focal2026-05-23ubuntu
ubuntulinux-virtual-hwe-16.04-edge (4.15.0.247.259~16.04.1) @ xenial2026-05-23ubuntu
ubuntulinux-tools-gcp-fips-4.15 (4.15.0.2090.88) @ bionic2026-05-23ubuntu
ubuntulinux-virtual-hwe-18.04-edge (5.4.0.227.247~18.04.1) @ bionic2026-05-23ubuntu
ubuntulinux-tools-azure-lts-20.04 (5.4.0.1160.153) @ focal2026-05-23ubuntu
ubuntulinux-tools-kvm-5.4 (5.4.0.1143.139) @ focal2026-05-23ubuntu
ubuntulinux-tools-azure (4.15.0.1197.212~14.04.1) @ trusty2026-05-23ubuntu
ubuntulinux-tools-azure-edge (4.15.0.1197.212~16.04.1) @ xenial2026-05-23ubuntu
ubuntulinux-tools-azure-fips-4.15 (4.15.0.2106.102) @ bionic2026-05-23ubuntu
ubuntulinux-tools-gcp-fips-5.4 (5.4.0.1159.101) @ focal2026-05-23ubuntu
ubuntulinux-tools-azure-fips-5.4 (5.4.0.1160.97) @ focal2026-05-23ubuntu
ubuntulinux-tools-azure-edge (5.4.0.1161.167~18.04.1) @ bionic2026-05-23ubuntu
ubuntulinux-tools-raspi2-hwe-18.04-edge (5.4.0.1139.170) @ focal2026-05-23ubuntu
ubuntulinux-tools-bluefield-5.4 (5.4.0.1116.112) @ focal2026-05-23ubuntu

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.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(21)

Data Freshness Timeline

(refreshed 9× in last 7d / 46× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

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

Frequently asked(5)

What is CVE-2021-47599?
CVE-2021-47599 is a medium vulnerability published on June 19, 2024. In the Linux kernel, the following vulnerability has been resolved: btrfs: use latestdev in btrfsshow_devname The test case btrfs/238 reports the warning below: WARNING: CPU: 3 PID: 481 at fs/btrfs/super.c:2509 btrfsshowdevname+0x104/0x1e8 [btrfs] CPU: 2 PID: 1 Comm: systemd Tainted: G W O…
When was CVE-2021-47599 disclosed?
CVE-2021-47599 was first published in the National Vulnerability Database on June 19, 2024, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2021-47599 actively exploited?
CVE-2021-47599 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2021-47599?
CVE-2021-47599 has a CVSS v3 base score of 4.7 (NVD).
How do I remediate CVE-2021-47599?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2021-47599, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2021-47599

Explore →

Is Your Infrastructure Affected by CVE-2021-47599?

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