CVE-2023-53987: ping: Fix potentail NULL deref for /proc/net/icmp.
In the Linux kernel, the following vulnerability has been resolved:
ping: Fix potentail NULL deref for /proc/net/icmp.
After commit dbca1596bbb0 ("ping: convert to RCU lookups, get rid
of rwlock"), we use RCU for ping sockets, but we should use spinlock
for /proc/net/icmp to avoid a potential NULL deref mentioned in
the previous patch.
Let's go back to using spinlock there.
Note we can convert ping sockets to use hlist instead of hlist_nulls
because we do not use SLAB_TYPESAFE_BY_RCU for ping sockets.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel bug in ICMP ping socket handling. Reading /proc/net/icmp could hit a NULL pointer condition after an earlier RCU-related change. The public record does not provide a CVSS score, confirmed impact, or evidence of exploitation.
Executive priority
Treat as a routine kernel maintenance issue unless your environment has high-risk shared Linux hosts. There is no sourced evidence of active exploitation or critical impact, but kernel NULL dereference bugs can affect availability.
Technical view
The kernel fix restores spinlock use for /proc/net/icmp while ping sockets use RCU lookup, addressing a potential NULL dereference introduced after commit dbca1596bbb0. Sources describe the issue as resolved in Linux stable commits, but provide limited affected-version and impact detail.
Likely exposure
Exposure is limited to Linux systems running affected kernel versions. The bundle lists Linux kernel version entries including 6.0, 6.1.24, 6.2.11, and 6.3, but version semantics are incomplete.
Exploitation context
No active exploitation is supported by the provided sources. KEV status is false, and the bundle does not describe public exploit code, attacker prerequisites, or real-world abuse.
Researcher notes
The record is sparse: no CVSS, CWE, exploitability analysis, or detailed affected range is provided. Analysis should stay anchored to the kernel commit message and downstream distribution advisories for version mapping.
Mitigation direction
Update affected Linux kernels using distribution or vendor-supported packages.
Review the referenced Linux stable commits for the applicable fixed kernel line.
Check vendor advisories for exact affected and fixed versions.
Prioritize multi-user, container-host, and externally managed Linux systems.
Validation and detection
Inventory Linux kernel versions across servers and container hosts.
Compare installed kernels with vendor advisories and referenced stable fixes.
Check whether systems expose /proc/net/icmp to local users or containers.
Confirm updated systems booted into the fixed kernel.
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-53987 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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
4Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Dec 24, 2025, 10:55 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.