CVE-2023-53782 — dccp: Fix out of bounds access in DCCP error handler
In the Linux kernel, the following vulnerability has been resolved: dccp: Fix out of bounds access in DCCP error handler There was a previous attempt to fix an out-of-bounds access in the DCCP error handlers, but that fix assumed that the error handlers only want to access the first 8 bytes of the DCCP header. Actually, they also look at the DCCP sequence number, which is stored beyond 8 bytes, so an explicit pskb_may_pull() is required.
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 ba93cf7d2118774c0b2dcfccc8ae999427815caaversion 4.9≥ 4.8.10 and < 4.9≥ 4.4.34 and < 4.5≥ 3.16.42 and < 3.17≥ 3.12.68 and < 3.13≥ 3.10.105 and < 3.11≥ 3.2.87 and < 3.3 and 20 moreversion 84d9c612bb7a9e44c6bf286bedfbe72a6d2d71d4version 99131760a8851e6e5b2c9b24d0a68a3068923a08version 968953df833c61fce5adcc0612efeaced24e5719version bfe7d1dee859cad6802f8e21a0a863f408114612version bd380617d5d161ea2bbe7a8073b3ca7bca0381e5version 4ca7e66fcce02459fa6961979f9fe30ae1098cf0≥ 6706a97fec963d6cb3f7fc2978ec1427b4651214 and < 3533e10272555c422a7d51ebc0ce8c483429f7f2version a2df29ed840f90e459a3f8ff029b216be3912731version 46b1ffd4738a3ee04b2e8f5a4b8cfc39e9c722a2version dbf1719c65fb0368a94d15767c669e47e295a073version 261def571d19d3b4e2228643c5c0ac89f5e10d15version 96106a207ae972d8f9e4815e84c159f29e4bbee7≥ 6706a97fec963d6cb3f7fc2978ec1427b4651214 and < 977ad86c2a1bcaf58f01ab98df5cc145083c489c≥ 6706a97fec963d6cb3f7fc2978ec1427b4651214 and < ec620c34f5fa5d055f9f6136a387755db6157712≥ 6706a97fec963d6cb3f7fc2978ec1427b4651214 and < d8171411a661253e6271fa10b65b46daf1b6471c≥ 6706a97fec963d6cb3f7fc2978ec1427b4651214 and < f8a7f10a1dccf9868ff09342a73dce27501b86df≥ 6706a97fec963d6cb3f7fc2978ec1427b4651214 and < 6ecf09699eb1554299aa1e7fd13e9e80f656c2f9≥ 6706a97fec963d6cb3f7fc2978ec1427b4651214 and < 4b8a938e329ae4eb54b73b0c87b5170607b038a8≥ 6706a97fec963d6cb3f7fc2978ec1427b4651214 and < 7a7dd70cb954d3efa706a429687ded88c02496fa≥ 6706a97fec963d6cb3f7fc2978ec1427b4651214 and < 177212bf6dc1ff2d13d0409cddc5c9e81feec63d |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.24%
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
9 on the record
- git.kernel.org/stable/c/177212bf6dc1ff2d13d0409cddc5c9e81feec63d
- git.kernel.org/stable/c/d8171411a661253e6271fa10b65b46daf1b6471c
- git.kernel.org/stable/c/3533e10272555c422a7d51ebc0ce8c483429f7f2
- git.kernel.org/stable/c/977ad86c2a1bcaf58f01ab98df5cc145083c489c
- git.kernel.org/stable/c/6ecf09699eb1554299aa1e7fd13e9e80f656c2f9
- git.kernel.org/stable/c/f8a7f10a1dccf9868ff09342a73dce27501b86df
- git.kernel.org/stable/c/4b8a938e329ae4eb54b73b0c87b5170607b038a8
- git.kernel.org/stable/c/7a7dd70cb954d3efa706a429687ded88c02496fa
- git.kernel.org/stable/c/ec620c34f5fa5d055f9f6136a387755db6157712
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 13h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 13h
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 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-53782 is "dccp: Fix out of bounds access in DCCP error handler", 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.24% 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.