CVE-2024-41049

In the Linux kernel, the following vulnerability has been resolved:

filelock: fix potential use-after-free in posix_lock_inode

Light Hsieh reported a KASAN UAF warning in trace_posix_lock_inode(). The request pointer had been changed earlier to point to a lock entry that was added to the inodes list. However, before the tracepoint could fire, another task raced in and freed that lock.

Fix this by moving the tracepoint inside the spinlock, which should ensure that this doesnt happen.

Weakness

The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory “belongs” to the code that operates on the new pointer.

Affected Software

Potential Mitigations

References

• https://git.kernel.org/stable/c/02a8964260756c70b20393ad4006948510ac9967
• https://git.kernel.org/stable/c/116599f6a26906cf33f67975c59f0692ecf7e9b2
• https://git.kernel.org/stable/c/1b3ec4f7c03d4b07bad70697d7e2f4088d2cfe92
• https://git.kernel.org/stable/c/1cbbb3d9475c403ebedc327490c7c2b991398197
• https://git.kernel.org/stable/c/432b06b69d1d354a171f7499141116536579eb6a
• https://git.kernel.org/stable/c/5cb36e35bc10ea334810937990c2b9023dacb1b0
• https://git.kernel.org/stable/c/7d4c14f4b511fd4c0dc788084ae59b4656ace58b
• https://git.kernel.org/stable/c/02a8964260756c70b20393ad4006948510ac9967
• https://git.kernel.org/stable/c/116599f6a26906cf33f67975c59f0692ecf7e9b2
• https://git.kernel.org/stable/c/1b3ec4f7c03d4b07bad70697d7e2f4088d2cfe92
• https://git.kernel.org/stable/c/1cbbb3d9475c403ebedc327490c7c2b991398197
• https://git.kernel.org/stable/c/432b06b69d1d354a171f7499141116536579eb6a
• https://git.kernel.org/stable/c/5cb36e35bc10ea334810937990c2b9023dacb1b0
• https://git.kernel.org/stable/c/7d4c14f4b511fd4c0dc788084ae59b4656ace58b