Kernel warning via socket-family race
Published Dec 9, 2025 · Updated May 11, 2026
Race condition in affected Linux kernel branches allows local users to trigger a kernel warning through concurrent socket-family changes. sk_mc_loop() repeatedly read sk->sk_family while IPV6_ADDRFORM could change that field concurrently, letting one call observe inconsistent address families until a single READ_ONCE() access was introduced. Reaching the warning requires local socket operations, IPv6 support, and the affected networking path; the upstream record documents a WARN_ON_ONCE, not privilege escalation or memory corruption.
Summary
What happened
Race condition in affected Linux kernel branches allows local users to trigger a kernel warning through concurrent socket-family changes. sk_mc_loop() repeatedly read sk->sk_family while IPV6_ADDRFORM could change that field concurrently, letting one call observe inconsistent address families until a single READ_ONCE() access was introduced. Reaching the warning requires local socket operations, IPv6 support, and the affected networking path; the upstream record documents a WARN_ON_ONCE, not privilege escalation or memory corruption.
The record
- CVE
- CVE-2023-53831
- Published
- Dec 9, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Dec 9, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record 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=2.6.33
- Affected versionversion=7ad6848c7e81a603605fad3f3575841aab004eea <41f10a4d78fe69d685a3172e6884297f233dcf95
- Affected versionversion=7ad6848c7e81a603605fad3f3575841aab004eea <7586a66b9c4f1b8a825ea1dfa3a91aad5cc7b89b
- Affected versionversion=7ad6848c7e81a603605fad3f3575841aab004eea <895dc4c47171a20035cdaa8d74c1c1e97f2fc974
- Affected versionversion=7ad6848c7e81a603605fad3f3575841aab004eea <9036b6342fcdab190d6edce3dd447859c1de90fc
- Affected versionversion=7ad6848c7e81a603605fad3f3575841aab004eea <a3e0fdf71bbe031de845e8e08ed7fba49f9c702c
- Affected versionversion=7ad6848c7e81a603605fad3f3575841aab004eea <b1f5b890b89cb38a6c0bac91984d56cd69808e8c
- Affected versionversion=7ad6848c7e81a603605fad3f3575841aab004eea <e918d0211ffbaf039447334c3460cafee1ce0157
- Affected versionversion=7ad6848c7e81a603605fad3f3575841aab004eea <ed4e0adfa407ab65dd73b8862ebf2f308a0349d2
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