CVE-2023-53716 — net: fix skb leak in __skb_tstamp_tx()
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
version 30290f210ba7426ff7592fe2eb4114b1b5bad219≥ 6.3.2 and < 6.3.5≥ 6.1.28 and < 6.1.31≥ 5.15.111 and < 5.15.114≥ 5.10.180 and < 5.10.181≥ 5.4.243 and < 5.4.244≥ 4.19.283 and < 4.19.284≥ 4.14.315 and < 4.14.316 and 9 more≥ 6.2.15 and < 6.3≥ 281072fb2a7294cde7acbf5375b879f40a8001b7 and < 82501f1ead557cbee1c2467654ec109a80334d22≥ 50749f2dd6854a41830996ad302aef2ffaf011d8 and < 8a02fb71d7192ff1a9a47c9d937624966c6e09af≥ 426384dd4980040651536fef5feac4dcc4d7ee4e and < f4d928c00254cfc9dd0ee7076f4a59bceec675f4≥ cb52e7f24c1d01a536a847dff0d1d95889cc3b5c and < cc18b4685910d5d9de8314bae9c55790701b1811≥ 43e4197dd5f6b474a8b16f8b6a42cd45cf4f9d1a and < e06841a2abf9c82735cee39e88b1d79464088840≥ 230a5ed7d813fb516de81d23f09d7506753e41e9 and < a594382ec6d0cc8cff5a8bc7e61b54e3858fb243≥ 602fa8af44fd55a58f9e94eb673e8adad2c6cc46 and < 58766252f6b2c0487cda6976a53d2bb03ae28e2a≥ 1f69c086b20e27763af28145981435423f088268 and < 779332447108545ef04682ea29af5f85c0202aee |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.21%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Deferred
- Record created in this database
- 2025
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
8 on the record
- git.kernel.org/stable/c/cc18b4685910d5d9de8314bae9c55790701b1811
- git.kernel.org/stable/c/a594382ec6d0cc8cff5a8bc7e61b54e3858fb243
- git.kernel.org/stable/c/82501f1ead557cbee1c2467654ec109a80334d22
- git.kernel.org/stable/c/779332447108545ef04682ea29af5f85c0202aee
- git.kernel.org/stable/c/f4d928c00254cfc9dd0ee7076f4a59bceec675f4
- git.kernel.org/stable/c/58766252f6b2c0487cda6976a53d2bb03ae28e2a
- git.kernel.org/stable/c/e06841a2abf9c82735cee39e88b1d79464088840
- git.kernel.org/stable/c/8a02fb71d7192ff1a9a47c9d937624966c6e09af
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 9h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 9h
- Unknown CVE-2026-98428 ALSA: usb: 6fire: Avoid embedded URBs 1d
- Unknown CVE-2026-98431 RDMA/uverbs: Fix mmap_lock/disassociation_lock circular dependency 1d
- Unknown CVE-2026-98430 RDMA/efa: Keep admin queues alive while IRQ is registered 1d
- Unknown CVE-2026-98429 RDMA/efa: Keep EQ resources alive while IRQ is registered 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2023-53716 is "net: fix skb leak in __skb_tstamp_tx()", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.21% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.