virtiofs: fix UAF on submount umount
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 26e5c67deb2e1f42a951f022fdf5b9f7eb747b01 · < 2abfd3ffbd9452f72535d96ff3982b3ab1f8f2f9| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s virtiofs handling can hit a use-after-free when unmounting a submount after its superblock has been destroyed. This can cause a kernel Oops. The input does not specify how an attacker could trigger it or whether network access, authentication, or user interaction is required.
Engineers running Linux kernels with virtiofs should check their versions; affected versions are not specified.