CVE-2023-52522
What it is
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().
At a glance
- Exploitability
- Can be exploited from the same network segment without logging in. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.3% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.3% in the next 30 days (EPSS).
- Severity: 8.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.3% · EPSS, next 30 days
- Record status
- Modified
Affected
- Linux Kernel < 5.4.258
- Linux Kernel < 5.10.198
- Linux Kernel < 5.15.135
- Linux Kernel < 6.1.57
- Linux Kernel < 6.5.7
- Linux Kernel 6.6
Attack profile CVSS 3.1 · 8.8
- Attack vector
- Adjacent network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2023-52522.md and follow it. Check whether this project is affected by CVE-2023-52522. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/147d89ee41434b97043c2dcb17a97dc151859baa
- https://git.kernel.org/stable/c/25563b581ba3a1f263a00e8c9a97f5e7363be6fd
- https://git.kernel.org/stable/c/2ea52a2fb8e87067e26bbab4efb8872639240eb0
- https://git.kernel.org/stable/c/95eabb075a5902f4c0834ab1fb12dc35730c05af
- https://git.kernel.org/stable/c/a75152d233370362eebedb2643592e7c883cc9fc
- https://git.kernel.org/stable/c/f82aac8162871e87027692b36af335a2375d4580
- https://git.kernel.org/stable/c/147d89ee41434b97043c2dcb17a97dc151859baa
- https://git.kernel.org/stable/c/25563b581ba3a1f263a00e8c9a97f5e7363be6fd
- https://git.kernel.org/stable/c/2ea52a2fb8e87067e26bbab4efb8872639240eb0
- https://git.kernel.org/stable/c/95eabb075a5902f4c0834ab1fb12dc35730c05af
References
- https://git.kernel.org/stable/c/147d89ee41434b97043c2dcb17a97dc151859baa
- https://git.kernel.org/stable/c/25563b581ba3a1f263a00e8c9a97f5e7363be6fd
- https://git.kernel.org/stable/c/2ea52a2fb8e87067e26bbab4efb8872639240eb0
- https://git.kernel.org/stable/c/95eabb075a5902f4c0834ab1fb12dc35730c05af
- https://git.kernel.org/stable/c/a75152d233370362eebedb2643592e7c883cc9fc
- https://git.kernel.org/stable/c/f82aac8162871e87027692b36af335a2375d4580
- https://git.kernel.org/stable/c/147d89ee41434b97043c2dcb17a97dc151859baa
- https://git.kernel.org/stable/c/25563b581ba3a1f263a00e8c9a97f5e7363be6fd
- https://git.kernel.org/stable/c/2ea52a2fb8e87067e26bbab4efb8872639240eb0
- https://git.kernel.org/stable/c/95eabb075a5902f4c0834ab1fb12dc35730c05af
- https://git.kernel.org/stable/c/a75152d233370362eebedb2643592e7c883cc9fc
- https://git.kernel.org/stable/c/f82aac8162871e87027692b36af335a2375d4580