Menu

Star on GitHub · 3.2k

CVE-2023-53716

In the Linux kernel, the following vulnerability has been resolved: net: fix skb leak in __skb_tstamp_tx() Commit 50749f2dd685 ("tcp/udp: Fix memleaks of sk and zerocopy skbs with TX timestamp.")…

Published Oct 22, 2025EPSS 0.21%

Overview

CVE-2023-53716 is a known-severity vulnerability. It was published on October 22, 2025.

Technical description

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

net: fix skb leak in __skb_tstamp_tx()

Commit 50749f2dd685 ("tcp/udp: Fix memleaks of sk and zerocopy skbs with

TX timestamp.") added a call to skb_orphan_frags_rx() to fix leaks with

zerocopy skbs. But it ended up adding a leak of its own. When

skb_orphan_frags_rx() fails, the function just returns, leaking the skb

it just cloned. Free it before returning.

This bug was discovered and resolved using Coverity Static Analysis

Security Testing (SAST) by Synopsys, Inc.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2023-53716?

CVE-2023-53716 is a known-severity vulnerability. It was published on October 22, 2025.

How severe is CVE-2023-53716?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2023-53716?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2023-53716?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2023-53716 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.