Answer in brief
CVE-2021-47113 records a High severity (CVSS 7.1) vulnerability in btrfs: abort in rename_exchange if we fail to insert the second ref. 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.
CVSS is 7.1. 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.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.13:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.13:rc2:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.13:rc3:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.13:rc4:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=cdd1fedf8261cd7a73c0596298902ff4f0f04492 <0df50d47d17401f9f140dfbe752a65e5d72f9932 || >=cdd1fedf8261cd7a73c0596298902ff4f0f04492 <ff8de2cec65a8c8521faade12a31b39c80e49f5b || >=cdd1fedf8261cd7a73c0596298902ff4f0f04492 <dc09ef3562726cd520c8338c1640872a60187af5 | 0df50d47d17401f9f140dfbe752a65e5d72f9932, ff8de2cec65a8c8521faade12a31b39c80e49f5b, dc09ef3562726cd520c8338c1640872a60187af5 |
| Linux/Linuxgeneric | 4.7 | Not reported |
Published upstream
Mar 15, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
In the Linux kernel, the following vulnerability has been resolved: btrfs: abort in rename_exchange if we fail to insert the second ref Error injection stress uncovered a problem where we'd leave a dangling inode ref if we failed during a rename_exchange. This happens because we insert the inode ref for one side of the rename, and then for the other side. If this second inode ref insert fails we'll leave the first one dangling and leave a corrupt file system behind. Fix this by aborting if we did the insert for the first inode ref.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2021-47113 records a High severity (CVSS 7.1) vulnerability in btrfs: abort in rename_exchange if we fail to insert the second ref. 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.
CVSS is 7.1. 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.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.13:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.13:rc2:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.13:rc3:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.13:rc4:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=cdd1fedf8261cd7a73c0596298902ff4f0f04492 <0df50d47d17401f9f140dfbe752a65e5d72f9932 || >=cdd1fedf8261cd7a73c0596298902ff4f0f04492 <ff8de2cec65a8c8521faade12a31b39c80e49f5b || >=cdd1fedf8261cd7a73c0596298902ff4f0f04492 <dc09ef3562726cd520c8338c1640872a60187af5 | 0df50d47d17401f9f140dfbe752a65e5d72f9932, ff8de2cec65a8c8521faade12a31b39c80e49f5b, dc09ef3562726cd520c8338c1640872a60187af5 |
| Linux/Linuxgeneric | 4.7 | Not reported |
Published upstream
Mar 15, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
In the Linux kernel, the following vulnerability has been resolved: btrfs: abort in rename_exchange if we fail to insert the second ref Error injection stress uncovered a problem where we'd leave a dangling inode ref if we failed during a rename_exchange. This happens because we insert the inode ref for one side of the rename, and then for the other side. If this second inode ref insert fails we'll leave the first one dangling and leave a corrupt file system behind. Fix this by aborting if we did the insert for the first inode ref.
Quoted source text, attributed separately from HOL analysis.