Answer in brief
CVE-2025-21879 records a Unknown severity vulnerability in btrfs: fix use-after-free on inode when scanning root during em shrinking. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=fef55c4d9c9c22264d2b2ceae1e26922cb6129a5 <07836bc18f4ae42da4e922244f4685561c18755e || >=1020443840569535f6025a855958f07ea3eebf71 <5e79d26014f9386387575b9ed60d342057cee49b || >=1020443840569535f6025a855958f07ea3eebf71 <59f37036bb7ab3d554c24abc856aabca01126414 | 07836bc18f4ae42da4e922244f4685561c18755e, 5e79d26014f9386387575b9ed60d342057cee49b, 59f37036bb7ab3d554c24abc856aabca01126414 |
| Linux/Linuxgeneric | 6.13 | Not reported |
Published upstream
Mar 27, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: btrfs: fix use-after-free on inode when scanning root during em shrinking At btrfs_scan_root() we are accessing the inode's root (and fs_info) in a call to btrfs_fs_closing() after we have scheduled the inode for a delayed iput, and that can result in a use-after-free on the inode in case the cleaner kthread does the iput before we dereference the inode in the call to btrfs_fs_closing(). Fix this by using the fs_info stored already in a local variable instead of doing inode->root->fs_info.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2025-21879 records a Unknown severity vulnerability in btrfs: fix use-after-free on inode when scanning root during em shrinking. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=fef55c4d9c9c22264d2b2ceae1e26922cb6129a5 <07836bc18f4ae42da4e922244f4685561c18755e || >=1020443840569535f6025a855958f07ea3eebf71 <5e79d26014f9386387575b9ed60d342057cee49b || >=1020443840569535f6025a855958f07ea3eebf71 <59f37036bb7ab3d554c24abc856aabca01126414 | 07836bc18f4ae42da4e922244f4685561c18755e, 5e79d26014f9386387575b9ed60d342057cee49b, 59f37036bb7ab3d554c24abc856aabca01126414 |
| Linux/Linuxgeneric | 6.13 | Not reported |
Published upstream
Mar 27, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: btrfs: fix use-after-free on inode when scanning root during em shrinking At btrfs_scan_root() we are accessing the inode's root (and fs_info) in a call to btrfs_fs_closing() after we have scheduled the inode for a delayed iput, and that can result in a use-after-free on the inode in case the cleaner kthread does the iput before we dereference the inode in the call to btrfs_fs_closing(). Fix this by using the fs_info stored already in a local variable instead of doing inode->root->fs_info.
Quoted source text, attributed separately from HOL analysis.