Answer in brief
CVE-2022-49995 records a High severity (CVSS 7.8) vulnerability in writeback: avoid use-after-free after removing device. 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.8. 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:6.0:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.0:rc2:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | 5.15 | Not reported |
| Linux/Linuxgeneric | >=45a2966fd64147518dc5bca25f447bd0fb5359ac <f96b9f7c1676923bce871e728bb49c0dfa5013cc || >=45a2966fd64147518dc5bca25f447bd0fb5359ac <9a6c710f3bc10bc9cc23e1c080b53245b7f9d5b7 || >=45a2966fd64147518dc5bca25f447bd0fb5359ac <f87904c075515f3e1d8f4a7115869d3b914674fd | f96b9f7c1676923bce871e728bb49c0dfa5013cc, 9a6c710f3bc10bc9cc23e1c080b53245b7f9d5b7, f87904c075515f3e1d8f4a7115869d3b914674fd |
Published upstream
Jun 18, 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 4, 2026
In the Linux kernel, the following vulnerability has been resolved: writeback: avoid use-after-free after removing device When a disk is removed, bdi_unregister gets called to stop further writeback and wait for associated delayed work to complete. However, wb_inode_writeback_end() may schedule bandwidth estimation dwork after this has completed, which can result in the timer attempting to access the just freed bdi_writeback. Fix this by checking if the bdi_writeback is alive, similar to when scheduling writeback work. Since this requires wb->work_lock, and wb_inode_writeback_end() may get called from interrupt, switch wb->work_lock to an irqsafe lock.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2022-49995 records a High severity (CVSS 7.8) vulnerability in writeback: avoid use-after-free after removing device. 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.8. 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:6.0:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.0:rc2:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | 5.15 | Not reported |
| Linux/Linuxgeneric | >=45a2966fd64147518dc5bca25f447bd0fb5359ac <f96b9f7c1676923bce871e728bb49c0dfa5013cc || >=45a2966fd64147518dc5bca25f447bd0fb5359ac <9a6c710f3bc10bc9cc23e1c080b53245b7f9d5b7 || >=45a2966fd64147518dc5bca25f447bd0fb5359ac <f87904c075515f3e1d8f4a7115869d3b914674fd | f96b9f7c1676923bce871e728bb49c0dfa5013cc, 9a6c710f3bc10bc9cc23e1c080b53245b7f9d5b7, f87904c075515f3e1d8f4a7115869d3b914674fd |
Published upstream
Jun 18, 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 4, 2026
In the Linux kernel, the following vulnerability has been resolved: writeback: avoid use-after-free after removing device When a disk is removed, bdi_unregister gets called to stop further writeback and wait for associated delayed work to complete. However, wb_inode_writeback_end() may schedule bandwidth estimation dwork after this has completed, which can result in the timer attempting to access the just freed bdi_writeback. Fix this by checking if the bdi_writeback is alive, similar to when scheduling writeback work. Since this requires wb->work_lock, and wb_inode_writeback_end() may get called from interrupt, switch wb->work_lock to an irqsafe lock.
Quoted source text, attributed separately from HOL analysis.