LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53839: dccp: fix data-race around dp->dccps_mss_cache

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2023-53839 is a Linux kernel race-condition fix in the DCCP networking code. The public bundle does not provide CVSS, demonstrated impact, or exploitation evidence. Treat it as a kernel hygiene and stability risk until your distribution classifies it.

Executive priority

Handle through normal kernel patch governance unless your environment uses DCCP or runs exposed custom kernels. Escalate if a vendor later assigns high severity, publishes stronger impact details, or confirms exploitability.

Technical view

The issue is a data race around dp->dccps_mss_cache. dccp_sendmsg() and do_dccp_getsockopt() read the cache before socket locking. The fix adds READ_ONCE()/WRITE_ONCE() handling and rechecks dccps_mss_cache after locking in dccp_sendmsg().

Likely exposure

Exposure is limited to Linux systems running affected kernel versions with DCCP code present or enabled. The bundle lists Linux as affected but does not confirm distribution package status, reachable attack surface, or whether common configurations expose this path.

Exploitation context

No active exploitation is supported by the supplied sources. The CVE is not marked KEV, and the bundle provides no public exploit, proof of concept, privilege requirement, or attack vector details.

Researcher notes

The source evidence is narrow: it documents a race fix, affected Linux kernel records, and stable commits. It does not establish exploitability, crash behavior, privilege boundaries, or security impact beyond the race condition itself.

Mitigation direction

  • Check your Linux distribution advisory for patched kernel packages.
  • Prioritize kernel updates where DCCP is enabled or used.
  • If patching is delayed, review vendor guidance for DCCP exposure reduction.
  • Track the referenced stable kernel commits in your kernel baseline.

Validation and detection

  • Inventory Linux kernel versions across servers and appliances.
  • Confirm whether DCCP support is built, loaded, or intentionally required.
  • Map installed kernels against vendor-fixed packages or stable commits.
  • Verify no unsupported kernel branches remain in production.
Prepared
Confidence
medium
Sources
10

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-53839 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
9Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux7c657876b63cb1d8a2ec06f8fc6c37bb8412e66c, 7c657876b63cb1d8a2ec06f8fc6c37bb8412e66c, 7c657876b63cb1d8a2ec06f8fc6c37bb8412e66c, 7c657876b63cb1d8a2ec06f8fc6c37bb8412e66c, 7c657876b63cb1d8a2ec06f8fc6c37bb8412e66c, 7c657876b63cb1d8a2ec06f8fc6c37bb8412e66c, 7c657876b63cb1d8a2ec06f8fc6c37bb8412e66c, 7c657876b63cb1d8a2ec06f8fc6c37bb8412e66cunaffected
LinuxLinux2.6.14, 0, 4.14.323, 4.19.292, 5.4.254, 5.10.191, 5.15.127, 6.1.46, 6.4.11, 6.5affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.