fuse: re-lock request before returning from fuse_ref_folio()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ c3021629a0d820247ee12b6c5192a1d5380e21c6 · < be353caffa8640f5e25fb3714ce8b0cef5e410e5| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
fuse: re-lock request before returning from fuse_ref_folio()
fuse_ref_folio() unlocks the request but does not re-lock it before returning. fuse_chan_abort() can end the request and the async end callback (eg fuse_writepage_free()) can free the args while the subsequent copy chain logic after fuse_ref_folio() accesses them, leading to use-after-free issues.
Fix this by locking the request in fuse_ref_folio() before returning.
From the CVE record · Linux
In the Linux kernel’s FUSE code, fuse_ref_folio() can return without re-locking a request. If fuse_chan_abort() ends that request and an asynchronous callback frees its arguments, subsequent code can access freed memory. The input does not specify attacker access requirements or user interaction.
Engineers running the Linux kernel should check whether their version includes the FUSE fix; affected versions are not specified.