LiveActive security incident?Get immediate response
CVE Record

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

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2024-35908 is a Linux kernel bug in the TLS receive path. When a receive-side lock fails, the kernel can return without releasing a psock reference, causing a resource leak. The public sources do not provide CVSS, confirmed business impact, or active exploitation evidence.

Executive priority

Treat this as a kernel maintenance item with uncertain severity. Patch through normal kernel update channels, with higher priority for network-facing Linux systems or environments that rely on kernel TLS.

Technical view

The fix changes tls_sw_recvmsg so the psock reference is acquired only after tls_rx_reader_lock succeeds. Previously, a failed lock path could leak the reference. The CVE record identifies Linux kernel versions and stable commits, but the provided data does not establish exploitability, privilege requirements, or precise downstream package status.

Likely exposure

Exposure is likely limited to Linux systems running affected kernels where kernel TLS software receive handling is present and reachable. Distribution kernels may be patched through backports, so package advisory status matters more than raw upstream version alone.

Exploitation context

The source bundle marks KEV as false and cites no active exploitation. The available technical evidence describes a reference leak bug and stable kernel fixes, not a public exploit or weaponized attack pattern.

Researcher notes

Evidence is narrow: the public description only confirms a psock reference leak in tls_sw_recvmsg on a failed tls_rx_reader_lock path. No CVSS, CWE, exploit conditions, or attack prerequisites are provided in the bundle.

Mitigation direction

  • Check Linux vendor advisories for CVE-2024-35908 coverage.
  • Apply kernel updates containing the referenced stable fixes.
  • Confirm backported fixes for distribution or cloud-provider kernels.
  • Prioritize systems using kernel TLS or exposed network services.
  • Monitor vendor guidance for revised severity or impact details.

Validation and detection

  • Inventory Linux kernel versions across affected assets.
  • Map installed kernels to vendor CVE advisories or changelogs.
  • Verify the relevant stable fix is present or backported.
  • Review exposure of workloads using kernel TLS features.
  • Document exceptions where patch status cannot be confirmed.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-35908 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux4cbc325ed6b4dce4910be06d9d6940a8b919c59b, 4cbc325ed6b4dce4910be06d9d6940a8b919c59b, 4cbc325ed6b4dce4910be06d9d6940a8b919c59b, 4cbc325ed6b4dce4910be06d9d6940a8b919c59bunaffected
LinuxLinux6.0, 0, 6.1.85, 6.6.26, 6.8.5, 6.9affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.