fuse: fix missing barrier when checking io-uring readiness
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.18.51, 7.2.3
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: fuse: fix missing barrier when checking io-uring readiness fuse_block_alloc() reads fch->initialized and then fch->io_uring. fch->io_uring is set before fch->initialized, ordered by the smp_wmb() in fuse_chan_set_intialized(), but fuse_block_alloc() has no matching read barrier between the two loads. This may lead a CPU to observe fch->initialized=1 but fch->io_uring=0, and skip the check that blocks request allocation until the io-uring queues are ready. This can reintroduce the lock-order inversion deadlock that commit 3393ff964e0f prevents. Add an smp_rmb() barrier to pair with the smp_wmb() in fuse_chan_set_initialized() to prevent this.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 3393ff964e0fa5def66570c54a4612bf9df06b76 · fixed in 8974575898cd7a4c818088f102b2e7a0286d3302; From 3393ff964e0fa5def66570c54a4612bf9df06b76 · fixed in dd9c835709f4bb3e4256eea7573e4e6e18f956de; From 3393ff964e0fa5def66570c54a4612bf9df06b76 · fixed in edb310bc27f0ad83e7fd558a3caf1a94ca511654
- Linux Linux
6.14
- KernelLinux
From 6.14.0 · fixed in 6.18.51; From 6.19.0 · fixed in 7.2.3