CVE-2024-35908

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

tls: get psock ref after taking rxlock to avoid leak

At the start of tls_sw_recvmsg, we take a reference on the psock, and then call tls_rx_reader_lock. If that fails, we return directly without releasing the reference.

Instead of adding a new label, just take the reference after locking has succeeded, since we dont need it before.

Weakness

The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

Affected Software

Potential Mitigations

• Choose a language or tool that provides automatic memory management, or makes manual memory management less error-prone.
• For example, glibc in Linux provides protection against free of invalid pointers.
• When using Xcode to target OS X or iOS, enable automatic reference counting (ARC) [REF-391].
• To help correctly and consistently manage memory when programming in C++, consider using a smart pointer class such as std::auto_ptr (defined by ISO/IEC ISO/IEC 14882:2003), std::shared_ptr and std::unique_ptr (specified by an upcoming revision of the C++ standard, informally referred to as C++ 1x), or equivalent solutions such as Boost.

References

• https://git.kernel.org/stable/c/30fabe50a7ace3e9d57cf7f9288f33ea408491c8
• https://git.kernel.org/stable/c/417e91e856099e9b8a42a2520e2255e6afe024be
• https://git.kernel.org/stable/c/b565d294e3d5aa809566a4d819835da11997d8b3
• https://git.kernel.org/stable/c/f1b7f14130d782433bc98c1e1e41ce6b4d4c3096
• https://git.kernel.org/stable/c/30fabe50a7ace3e9d57cf7f9288f33ea408491c8
• https://git.kernel.org/stable/c/417e91e856099e9b8a42a2520e2255e6afe024be
• https://git.kernel.org/stable/c/b565d294e3d5aa809566a4d819835da11997d8b3
• https://git.kernel.org/stable/c/f1b7f14130d782433bc98c1e1e41ce6b4d4c3096