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.
Does this matter?
Lower severity and a low EPSS score (0.21%). Track it; it rarely justifies an emergency change on its own.
Description
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 don't need it before.
- CVSS 3.1
- 5.5 MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- EPSS
- 0.21% probability · 12th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-401
- Affected
- linux/linux kernel
- Source
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
References
- https://git.kernel.org/stable/c/30fabe50a7ace3e9d57cf7f9288f33ea408491c8Patch
- https://git.kernel.org/stable/c/417e91e856099e9b8a42a2520e2255e6afe024bePatch
- https://git.kernel.org/stable/c/b565d294e3d5aa809566a4d819835da11997d8b3Patch
- https://git.kernel.org/stable/c/f1b7f14130d782433bc98c1e1e41ce6b4d4c3096Patch
- https://git.kernel.org/stable/c/30fabe50a7ace3e9d57cf7f9288f33ea408491c8Patch
- https://git.kernel.org/stable/c/417e91e856099e9b8a42a2520e2255e6afe024bePatch
- https://git.kernel.org/stable/c/b565d294e3d5aa809566a4d819835da11997d8b3Patch
- https://git.kernel.org/stable/c/f1b7f14130d782433bc98c1e1e41ce6b4d4c3096Patch
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.