LiveActive security incident?Get immediate response
CVE Record

CVE-2023-54218: net: Fix load-tearing on sk->sk_stamp in sock_recv_cmsgs().

In the Linux kernel, the following vulnerability has been resolved: net: Fix load-tearing on sk->sk_stamp in sock_recv_cmsgs(). KCSAN found a data race in sock_recv_cmsgs() where the read access to sk->sk_stamp needs READ_ONCE(). BUG: KCSAN: data-race in packet_recvmsg / packet_recvmsg write (marked) to 0xffff88803c81f258 of 8 bytes by task 19171 on cpu 0: sock_write_timestamp include/net/sock.h:2670 [inline] sock_recv_cmsgs include/net/sock.h:2722 [inline] packet_recvmsg+0xb97/0xd00 net/packet/af_packet.c:3489 sock_recvmsg_nosec net/socket.c:1019 [inline] sock_recvmsg+0x11a/0x130 net/socket.c:1040 sock_read_iter+0x176/0x220 net/socket.c:1118 call_read_iter include/linux/fs.h:1845 [inline] new_sync_read fs/read_write.c:389 [inline] vfs_read+0x5e0/0x630 fs/read_write.c:470 ksys_read+0x163/0x1a0 fs/read_write.c:613 __do_sys_read fs/read_write.c:623 [inline] __se_sys_read fs/read_write.c:621 [inline] __x64_sys_read+0x41/0x50 fs/read_write.c:621 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3b/0x90 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x72/0xdc read to 0xffff88803c81f258 of 8 bytes by task 19183 on cpu 1: sock_recv_cmsgs include/net/sock.h:2721 [inline] packet_recvmsg+0xb64/0xd00 net/packet/af_packet.c:3489 sock_recvmsg_nosec net/socket.c:1019 [inline] sock_recvmsg+0x11a/0x130 net/socket.c:1040 sock_read_iter+0x176/0x220 net/socket.c:1118 call_read_iter include/linux/fs.h:1845 [inline] new_sync_read fs/read_write.c:389 [inline] vfs_read+0x5e0/0x630 fs/read_write.c:470 ksys_read+0x163/0x1a0 fs/read_write.c:613 __do_sys_read fs/read_write.c:623 [inline] __se_sys_read fs/read_write.c:621 [inline] __x64_sys_read+0x41/0x50 fs/read_write.c:621 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3b/0x90 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x72/0xdc value changed: 0xffffffffc4653600 -> 0x0000000000000000 Reported by Kernel Concurrency Sanitizer on: CPU: 1 PID: 19183 Comm: syz-executor.5 Not tainted 6.3.0-rc7-02330-gca6270c12e20 #2 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014

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-54218 is a Linux kernel networking bug where concurrent socket reads can observe a torn timestamp value. The public record does not provide a CVSS score, concrete security impact, or evidence of exploitation. Treat it as a kernel reliability and correctness issue until vendor advisories clarify practical impact.

Executive priority

Monitor and remediate through standard kernel patch cycles unless your vendor assigns higher severity. Escalate prioritization for shared or multi-tenant Linux environments once affected package mapping confirms exposure. There is no source-supported evidence of active exploitation in the supplied bundle.

Technical view

The issue is a KCSAN-reported data race/load-tearing read of sk->sk_stamp in sock_recv_cmsgs(), reached through packet_recvmsg and socket read paths. The upstream fix uses READ_ONCE() to make the timestamp read atomic from the kernel concurrency perspective. Stable kernel commit references are provided for multiple maintained branches.

Likely exposure

Exposure is limited to Linux systems running affected kernel versions or downstream builds that have not backported the stable fix. The bundle lists Linux versions including 4.12, 4.14.316, 4.19.284, 5.4.244, 5.10.181, 5.15.113, 6.1.30, 6.3.4, and 6.4 as affected.

Exploitation context

The supplied sources show a sanitizer-discovered race from syzkaller-style testing, not a public exploit. KEV is false, and no cited source claims active exploitation. The record does not state attacker prerequisites, privilege requirements, or a demonstrated impact such as crash, privilege escalation, or information disclosure.

Researcher notes

The record is unusually sparse: no CVSS, CWE, attack vector, or impact statement is provided. Analysis should stay close to the kernel commit message: a load-tearing data race on sk->sk_stamp in sock_recv_cmsgs(). Avoid deriving exploitability from the KCSAN trace alone.

Mitigation direction

  • Check Linux distribution advisories for CVE-2023-54218 backport status.
  • Update affected kernels to vendor-supported builds containing the upstream stable fix.
  • Prioritize hosts running untrusted local workloads after vendor confirms applicability.
  • Track CVE and kernel stable references for branch-specific fix mapping.
  • Do not assume source version numbers reflect distro package exposure.

Validation and detection

  • Inventory kernel versions across Linux servers and container hosts.
  • Compare each kernel package changelog against CVE-2023-54218 or listed commit IDs.
  • Confirm vendor kernels include the READ_ONCE() sk_stamp fix.
  • Check vulnerability scanner findings against distro backport documentation.
  • Record exceptions where no vendor fix or affected-package mapping exists.
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-54218 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
LinuxLinux6c7c98bad4883a4a8710c96b2b44de482865eb6e, 6c7c98bad4883a4a8710c96b2b44de482865eb6e, 6c7c98bad4883a4a8710c96b2b44de482865eb6e, 6c7c98bad4883a4a8710c96b2b44de482865eb6e, 6c7c98bad4883a4a8710c96b2b44de482865eb6e, 6c7c98bad4883a4a8710c96b2b44de482865eb6e, 6c7c98bad4883a4a8710c96b2b44de482865eb6e, 6c7c98bad4883a4a8710c96b2b44de482865eb6eunaffected
LinuxLinux4.12, 0, 4.14.316, 4.19.284, 5.4.244, 5.10.181, 5.15.113, 6.1.30, 6.3.4, 6.4affected
Weakness

CWE details

No CWE listed

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