Inconsistent socket timestamps via unsynchronized sk_stamp read
Published Dec 30, 2025 · Updated Dec 30, 2025
A data race in Linux kernel socket timestamp handling allows local users to receive an inconsistent value through packet_recvmsg. sock_recv_cmsgs reads sk->sk_stamp directly while another execution context can write it, permitting load tearing instead of an atomic READ_ONCE access. Triggering requires concurrent packet-socket receive paths and socket timestamp access; the published record reports inconsistent timestamp data, not privilege escalation or code execution.
Summary
What happened
A data race in Linux kernel socket timestamp handling allows local users to receive an inconsistent value through packet_recvmsg. sock_recv_cmsgs reads sk->sk_stamp directly while another execution context can write it, permitting load tearing instead of an atomic READ_ONCE access. Triggering requires concurrent packet-socket receive paths and socket timestamp access; the published record reports inconsistent timestamp data, not privilege escalation or code execution.
The record
- CVE
- CVE-2023-54218
- Published
- Dec 30, 2025
- Updated
- Dec 30, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Dec 30, 2025CVE publishedPublication date reported by the CVE source.
- Dec 30, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.12
- Affected versionversion=6c7c98bad4883a4a8710c96b2b44de482865eb6e <564c3150ad357d571a0de7d8b644aa1f7e6e21b7
- Affected versionversion=6c7c98bad4883a4a8710c96b2b44de482865eb6e <7145f2309d649ad6273b9f66448321b9b4c523c8
- Affected versionversion=6c7c98bad4883a4a8710c96b2b44de482865eb6e <8319220054e5ea5f506d8d4c4b5e234f668ffc3b
- Affected versionversion=6c7c98bad4883a4a8710c96b2b44de482865eb6e <d06f67b2b8dcd00d995c468428b6bccebc5762d8
- Affected versionversion=6c7c98bad4883a4a8710c96b2b44de482865eb6e <d7343f8de019ebb55b2b6ef79b971f6ceb361a99
- Affected versionversion=6c7c98bad4883a4a8710c96b2b44de482865eb6e <de260d1e02cde39d317066835ee6e5234fc9f5a8
- Affected versionversion=6c7c98bad4883a4a8710c96b2b44de482865eb6e <dfd9248c071a3710c24365897459538551cb7167
- Affected versionversion=6c7c98bad4883a4a8710c96b2b44de482865eb6e <fd28692fa182d25e8d26bc1db506648839fde245
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo