CVE-2023-53782

dccp: Fix out of bounds access in DCCP error handler

N/A
Published: December 9, 2025 at 12:00 AM UTC
Updated: June 17, 2026 at 06:46 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 3.10.105v ≥ 3.12.68v ≥ 3.16.42v ≥ 3.2.87v ≥ 4.4.34v ≥ 4.8.103.10.105 ≤ v < 3.113.12.68 ≤ v < 3.133.16.42 ≤ v < 3.173.2.87 ≤ v < 3.34.4.34 ≤ v < 4.54.8.10 ≤ v < 4.94.9 ≤ v < 4.14.3264.9 ≤ v < 4.19.2954.9 ≤ v < 5.10.1954.9 ≤ v < 5.15.1324.9 ≤ v < 5.4.2574.9 ≤ v < 6.1.534.9 ≤ v < 6.4.164.9 ≤ v < 6.5.34.9 ≤ v < 6.6261def571d19d3b4e2228643c5c0ac89f5e10d153.10.1053.12.683.16.423.2.874.4.344.8.104.946b1ffd4738a3ee04b2e8f5a4b8cfc39e9c722a24ca7e66fcce02459fa6961979f9fe30ae1098cf06706a97fec963d6cb3f7fc2978ec1427b465121484d9c612bb7a9e44c6bf286bedfbe72a6d2d71d496106a207ae972d8f9e4815e84c159f29e4bbee7968953df833c61fce5adcc0612efeaced24e571999131760a8851e6e5b2c9b24d0a68a3068923a08a2df29ed840f90e459a3f8ff029b216be3912731ba93cf7d2118774c0b2dcfccc8ae999427815caabd380617d5d161ea2bbe7a8073b3ca7bca0381e5bfe7d1dee859cad6802f8e21a0a863f408114612dbf1719c65fb0368a94d15767c669e47e295a073
Vendor states this is fixed in 177212bf6dc1ff2d13d0409cddc5c9e81feec63d (fixed)
Vendor states this is fixed in 3533e10272555c422a7d51ebc0ce8c483429f7f2 (fixed)
Vendor states this is fixed in 4b8a938e329ae4eb54b73b0c87b5170607b038a8 (fixed)
Vendor states this is fixed in 6ecf09699eb1554299aa1e7fd13e9e80f656c2f9 (fixed)
Vendor states this is fixed in 7a7dd70cb954d3efa706a429687ded88c02496fa (fixed)
Vendor states this is fixed in 977ad86c2a1bcaf58f01ab98df5cc145083c489c (fixed)
Vendor states this is fixed in d8171411a661253e6271fa10b65b46daf1b6471c (fixed)
Vendor states this is fixed in ec620c34f5fa5d055f9f6136a387755db6157712 (fixed)
Vendor states this is fixed in f8a7f10a1dccf9868ff09342a73dce27501b86df (fixed)
Affected range stops below 3.11, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.13, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.17, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.3, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 4.14.326 (unaffected)
Vendor states this is fixed in 4.19.295 (unaffected)
Affected range stops below 4.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 4.9 (unaffected)
Vendor states this is fixed in 5.10.195 (unaffected)
Vendor states this is fixed in 5.15.132 (unaffected)
Vendor states this is fixed in 5.4.257 (unaffected)
Vendor states this is fixed in 6.1.53 (unaffected)
Vendor states this is fixed in 6.4.16 (unaffected)
Vendor states this is fixed in 6.5.3 (unaffected)
Vendor states this is fixed in 6.6 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card