Review reviewHigh

CVE-2026-53381

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: virtiofs: fix UAF on submount umount iput() called from fuse_release_end() can Oops if the super block has already been destroyed. Normally this is prevented by waiting for num_waiting to go down to zero before commencing with super block shutdown. This only works, however, for the last submount instance, as the wait counter is per connection, not per superblock. Revert to using synchronous release requests for the auto_submounts case, which is virtiofs only at this time.

CVSS
7.8
EPSS
0.14%
3.98% percentile
CISA KEV
Not listed
Published
2026.07.19
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

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

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: virtiofs: fix UAF on submount umount iput() called from fuse_release_end() can Oops if the super block has already been destroyed. Normally this is prevented by waiting for num_waiting to go down to zero before commencing with super block shutdown. This only works, however, for the last submount instance, as the wait counter is per connection, not per superblock. Revert to using synchronous release requests for the auto_submounts case, which is virtiofs only at this time.

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 548e1f2bac1d4df91a6138f26bb4ab00323fd948 < 607a1d4c42f649e6197567c0448fd9ebb316cd42, >= cfd1aa3e2b71f3327cb373c45a897c9028c62b35 < 1cc0e3a0c6499aaaa2f21a4fcbba388486afb25e, >= 83b375c6efef69b1066ad2d79601221e7892745a < 0b809199ff87c44487e516a725dd4be2185712ce, >= bfd17b6138df0122a95989457d8e18ce0b86165e < 2181a09ba980f142650fb053666350ead4471cfe, >= b26923512dbe57ae4917bafd31396d22a9d1691a < 97c4691653d145dcc699eca5d3aba3219a520f1f, >= 26e5c67deb2e1f42a951f022fdf5b9f7eb747b01 < 2abfd3ffbd9452f72535d96ff3982b3ab1f8f2f9, >= 26e5c67deb2e1f42a951f022fdf5b9f7eb747b01 < 39a2b95e008665c14f84e50ed411d898df7cd11b, >= 26e5c67deb2e1f42a951f022fdf5b9f7eb747b01 < e09412a714bcd49375198427bb4aa005037a9d6f, >= 26e5c67deb2e1f42a951f022fdf5b9f7eb747b01 < 06b41351779e9289e8785694ade9042ae85e41ea, >= f19a1390af448d9e193c08e28ea5f727bf3c3049, >= 5.10.246 < 5.10.260, >= 5.15.196 < 5.15.211, >= 6.1.158 < 6.1.177, >= 6.6.115 < 6.6.144, >= 6.12.54 < 6.12.95, >= 6.17.4 < 6.18, >= 6.18, >= 6.17.4 < 6.18.37, >= 6.19 < 7.0.14, >= 7.1 < 7.1.2
Fixed versions
5.10.260, 5.15.211, 6.1.177, 6.6.144, 6.12.95, 6.18.37, 7.0.14, 7.1.2

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