Review reviewHigh

CVE-2022-49995

Linux Linux, linux kernel

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...

CVSS
7.8
EPSS
0.21%
10.6% percentile
CISA KEV
Not listed
Published
2025.06.18
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.21%
Technical severityCVSS 7.8

Vulnerability overview

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...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 45a2966fd64147518dc5bca25f447bd0fb5359ac < f96b9f7c1676923bce871e728bb49c0dfa5013cc, >= 45a2966fd64147518dc5bca25f447bd0fb5359ac < 9a6c710f3bc10bc9cc23e1c080b53245b7f9d5b7, >= 45a2966fd64147518dc5bca25f447bd0fb5359ac < f87904c075515f3e1d8f4a7115869d3b914674fd, >= 5.15, >= 5.15 < 5.15.64, >= 5.16 < 5.19.6, 6.0
Fixed versions
5.15.64, 5.19.6

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-416