Security readout for executives and security teams
Plain-English summary
This is a Linux kernel btrfs bug that can trigger a kernel warning while mount information is being read after specific btrfs device-list changes. The source describes a correctness and stability fix, not data theft, privilege escalation, or confirmed compromise.
Executive priority
Treat as routine kernel hygiene unless btrfs is operationally important in production. Patch through normal Linux update cycles, with higher priority for storage-heavy systems using btrfs device management features.
Technical view
btrfs_show_devname() could search fs_devices::devices after btrfs_prepare_sprout() moved devices into seed_list, finding none and warning. The fix uses latest_dev->name, relying on RCU protection and device lifetime rules during remove or replace operations.
Likely exposure
Exposure appears limited to Linux systems using btrfs on affected kernel builds, especially configurations involving seed devices, sprout behavior, or device replacement/removal paths. Non-btrfs systems are not indicated as exposed by the supplied sources.
Exploitation context
The supplied sources do not show active exploitation, and KEV is false. The evidence describes a kernel warning found by btrfs testing, not a public exploit path or weaponized attack scenario.
Researcher notes
The public description is narrow: a warning in btrfs_show_devname caused by device-list movement during prepare_sprout. No CVSS, CWE, exploitability detail, or downstream vendor matrix is included, so impact should not be overstated.
Mitigation direction
- Update to a vendor kernel containing the referenced stable btrfs fixes.
- Prioritize systems actively using btrfs with seed, sprout, remove, or replace workflows.
- Check Linux distribution advisories for exact fixed package versions.
- Avoid inventing workarounds; follow vendor guidance if patching is delayed.
Validation and detection
- Inventory hosts running Linux with btrfs mounted filesystems.
- Map running kernel packages against vendor advisories for CVE-2021-47599.
- Confirm the kernel includes commits e342c2558016 or 6605fd2f394b.
- Review logs for btrfs_show_devname warnings during mountinfo reads.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2021-47599 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/e342c2558016ead462f376b6c6c2ac5efc17f3b1CVE reference, Linux
- https://git.kernel.org/stable/c/6605fd2f394bba0a0059df2b6cfc87b0b6d393a2CVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.