CVE-2023-53839
Description
In the Linux kernel, the following vulnerability has been resolved:
dccp: fix data-race around dp->dccps_mss_cache
dccp_sendmsg() reads dp->dccps_mss_cache before locking the socket. Same thing in do_dccp_getsockopt().
Add READ_ONCE()/WRITE_ONCE() annotations, and change dccp_sendmsg() to check again dccps_mss_cache after socket is locked.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Data race in Linux kernel DCCP's dp->dccps_mss_cache can cause incorrect MSS values, leading to potential denial of service.
Vulnerability
A data race exists in the Linux kernel's Datagram Congestion Control Protocol (DCCP) implementation around the dp->dccps_mss_cache variable. Both dccp_sendmsg() and do_dccp_getsockopt() read this cache without holding the socket lock, while other code paths may write to it concurrently. This lack of synchronization can result in the use of stale or inconsistent Maximum Segment Size (MSS) values.
Exploitation
The race is triggered when multiple threads access the same DCCP socket simultaneously. An attacker with the ability to send data or query socket options on a DCCP socket could cause a read of dccps_mss_cache to occur while another thread is updating it. No special privileges beyond network access are required, as the race can occur during normal socket operations.
Impact
An incorrect MSS value can lead to packet fragmentation errors, connection instability, or denial of service. The exact consequences depend on the timing of the race, but any deviation from the expected MSS may cause the kernel to generate malformed packets or fail to properly handle incoming data.
Mitigation
The fix introduces READ_ONCE() and WRITE_ONCE() annotations to ensure atomic reads and writes of the cache, and modifies dccp_sendmsg() to re-check the value after acquiring the socket lock. These patches have been applied to stable kernel branches [1][2][3]. Users should update to the latest stable kernel to eliminate the race.
AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
2Patches
8162fa1e3cfb62bdc7f272b3a67eebc7a92176d701c95ee64f239c9e1d98ba6ddc1c77487d1f38d313bdfa47e598fbd86Vulnerability mechanics
Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
8- git.kernel.org/stable/c/162fa1e3cfb62aa780d7c40c8cccb6c2f8bef7c1nvd
- git.kernel.org/stable/c/2bdc7f272b3a110a4e1fdee6c47c8d20f9b20817nvd
- git.kernel.org/stable/c/67eebc7a9217f999b779d46fba5312a716f0dc1dnvd
- git.kernel.org/stable/c/6d701c95ee6463abcbb6da543060d6e444554135nvd
- git.kernel.org/stable/c/a47e598fbd8617967e49d85c49c22f9fc642704cnvd
- git.kernel.org/stable/c/a6ddc1c774874dc704f96a99d015dc759627bba7nvd
- git.kernel.org/stable/c/d1f38d313bdfc52fb2f662e66d0c60dd1cfe2384nvd
- git.kernel.org/stable/c/f239c9e1d98b313435481b4926e8bdd06197e4d8nvd
News mentions
0No linked articles in our index yet.