The vulnerability in the Linux kernel's fuse-uring component arises from improper synchronization when accessing the queue->stopped flag. While most readers check this flag under a lock, fuse_uring_commit_fetch() did not, and fuse_uring_abort_end_requests() also failed to set it under lock. This race condition could cause a 'struct fuse_req' to be freed by one thread while another thread is performing teardown, potentially leading to memory corruption or instability. The issue has been resolved by enforcing locking when setting and reading queue->stopped.

The vulnerability could lead to use-after-free conditions in the kernel, potentially causing system instability or crashes. No confirmed exploits in the wild are reported. The impact is limited to kernel memory management within fuse-uring operations.

A fix has been implemented in the Linux kernel to address this race condition by properly locking access to queue->stopped. Users should apply the official kernel updates that include this fix. Patch status is not explicitly confirmed in the provided data; users should consult the Linux kernel vendor advisory or distribution security updates for the official patch and remediation guidance.