VYPR
Unrated severityNVD Advisory· Published Dec 24, 2025· Updated Apr 15, 2026

CVE-2023-53987

CVE-2023-53987

Description

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.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

A NULL pointer dereference vulnerability in the Linux kernel's ping socket handling for /proc/net/icmp, fixed by reverting to spinlock from RCU.

Root

Cause

The vulnerability is a potential NULL pointer dereference in the Linux kernel's ping socket implementation when accessing /proc/net/icmp. After commit dbca1596bbb0 ("ping: convert to RCU lookups, get rid of rwlock"), the code used RCU for ping sockets, but the /proc/net/icmp handler still required spinlock synchronization. This mismatch could lead to a NULL dereference under certain conditions [1].

Exploitation

An attacker would need local access to the system and the ability to read /proc/net/icmp. The race condition occurs when the RCU-protected socket lookup returns a NULL pointer that is not properly checked before use. No special privileges beyond file read access are required to trigger the issue, but the attacker must be able to cause concurrent socket operations and file reads.

Impact

Successful exploitation could cause a kernel NULL pointer dereference, leading to a system crash (denial of service). The vulnerability does not appear to allow privilege escalation or arbitrary code execution based on the available information.

Mitigation

The fix was committed to the Linux kernel stable tree in commit 176cbb6da28f36506cc60a4bec4ab8df0c16713a, which reverts the synchronization method back to using spinlock for the /proc/net/icmp path. Users should apply the latest kernel updates from their distribution to resolve this issue [1].

AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

1

Patches

3

Vulnerability mechanics

Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.

References

3

News mentions

0

No linked articles in our index yet.