---
id: CVE-2023-52522
title: |-
  In the Linux kernel, the following vulnerability has been resolved:

  net: fix possible store tearing in neigh_periodic_work()

  While looking at a related syzbot report involving neigh_periodic_work(),
  I found that I forgot to add an anno…
summary: |-
  In the Linux kernel, the following vulnerability has been resolved:

  net: fix possible store tearing in neigh_periodic_work()

  While looking at a related syzbot report involving neigh_periodic_work(),
  I found that I forgot to add an anno…
severity: high
cvss: 8.8
cvssVector: 'CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'
vendor: linux
product: linux_kernel
affected:
  - 'linux_kernel >= 2.6.37, < 5.4.258'
  - 'linux_kernel >= 5.5, < 5.10.198'
  - 'linux_kernel >= 5.11, < 5.15.135'
  - 'linux_kernel >= 5.16, < 6.1.57'
  - 'linux_kernel >= 6.2, < 6.5.7'
  - linux_kernel = 6.6
patched:
  - linux_kernel 6.5.7
published: '2024-03-02'
updated: '2026-08-04'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2023-52522'
references:
  - url: 'https://git.kernel.org/stable/c/147d89ee41434b97043c2dcb17a97dc151859baa'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/25563b581ba3a1f263a00e8c9a97f5e7363be6fd'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/2ea52a2fb8e87067e26bbab4efb8872639240eb0'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/95eabb075a5902f4c0834ab1fb12dc35730c05af'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/a75152d233370362eebedb2643592e7c883cc9fc'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/f82aac8162871e87027692b36af335a2375d4580'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/147d89ee41434b97043c2dcb17a97dc151859baa'
    label: af854a3a-2127-422b-91ae-364da2661108
  - url: 'https://git.kernel.org/stable/c/25563b581ba3a1f263a00e8c9a97f5e7363be6fd'
    label: af854a3a-2127-422b-91ae-364da2661108
  - url: 'https://git.kernel.org/stable/c/2ea52a2fb8e87067e26bbab4efb8872639240eb0'
    label: af854a3a-2127-422b-91ae-364da2661108
  - url: 'https://git.kernel.org/stable/c/95eabb075a5902f4c0834ab1fb12dc35730c05af'
    label: af854a3a-2127-422b-91ae-364da2661108
  - url: 'https://git.kernel.org/stable/c/a75152d233370362eebedb2643592e7c883cc9fc'
    label: af854a3a-2127-422b-91ae-364da2661108
  - url: 'https://git.kernel.org/stable/c/f82aac8162871e87027692b36af335a2375d4580'
    label: af854a3a-2127-422b-91ae-364da2661108
tags:
  - nvd
epss: 0.00332
epssPercentile: 0.23739
ingestedAt: '2026-08-05T05:58:02.151Z'
---

## Overview

In the Linux kernel, the following vulnerability has been resolved:

net: fix possible store tearing in neigh_periodic_work()

While looking at a related syzbot report involving neigh_periodic_work(),
I found that I forgot to add an annotation when deleting an
RCU protected item from a list.

Readers use rcu_deference(*np), we need to use either
rcu_assign_pointer() or WRITE_ONCE() on writer side
to prevent store tearing.

I use rcu_assign_pointer() to have lockdep support,
this was the choice made in neigh_flush_dev().

## Affected

- `linux_kernel >= 2.6.37, < 5.4.258`
- `linux_kernel >= 5.5, < 5.10.198`
- `linux_kernel >= 5.11, < 5.15.135`
- `linux_kernel >= 5.16, < 6.1.57`
- `linux_kernel >= 6.2, < 6.5.7`
- `linux_kernel = 6.6`

## Remediation

Upgrade past the affected range:

- `linux_kernel 6.5.7`