Answer in brief
CVE-2023-52522 records a High severity (CVSS 8.8) vulnerability in net: fix possible store tearing in neigh_periodic_work(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.6:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.6:rc2:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.6:rc3:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.6:rc4:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=767e97e1e0db0d0f3152cd2f3bd3403596aedbad <95eabb075a5902f4c0834ab1fb12dc35730c05af || >=767e97e1e0db0d0f3152cd2f3bd3403596aedbad <2ea52a2fb8e87067e26bbab4efb8872639240eb0 || >=767e97e1e0db0d0f3152cd2f3bd3403596aedbad <147d89ee41434b97043c2dcb17a97dc151859baa || >=767e97e1e0db0d0f3152cd2f3bd3403596aedbad <f82aac8162871e87027692b36af335a2375d4580 || >=767e97e1e0db0d0f3152cd2f3bd3403596aedbad <a75152d233370362eebedb2643592e7c883cc9fc || >=767e97e1e0db0d0f3152cd2f3bd3403596aedbad <25563b581ba3a1f263a00e8c9a97f5e7363be6fd | 95eabb075a5902f4c0834ab1fb12dc35730c05af, 2ea52a2fb8e87067e26bbab4efb8872639240eb0, 147d89ee41434b97043c2dcb17a97dc151859baa, f82aac8162871e87027692b36af335a2375d4580, a75152d233370362eebedb2643592e7c883cc9fc, 25563b581ba3a1f263a00e8c9a97f5e7363be6fd |
| Linux/Linuxgeneric | 2.6.37 | Not reported |
Published upstream
Mar 2, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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().
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2023-52522 records a High severity (CVSS 8.8) vulnerability in net: fix possible store tearing in neigh_periodic_work(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.6:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.6:rc2:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.6:rc3:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.6:rc4:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=767e97e1e0db0d0f3152cd2f3bd3403596aedbad <95eabb075a5902f4c0834ab1fb12dc35730c05af || >=767e97e1e0db0d0f3152cd2f3bd3403596aedbad <2ea52a2fb8e87067e26bbab4efb8872639240eb0 || >=767e97e1e0db0d0f3152cd2f3bd3403596aedbad <147d89ee41434b97043c2dcb17a97dc151859baa || >=767e97e1e0db0d0f3152cd2f3bd3403596aedbad <f82aac8162871e87027692b36af335a2375d4580 || >=767e97e1e0db0d0f3152cd2f3bd3403596aedbad <a75152d233370362eebedb2643592e7c883cc9fc || >=767e97e1e0db0d0f3152cd2f3bd3403596aedbad <25563b581ba3a1f263a00e8c9a97f5e7363be6fd | 95eabb075a5902f4c0834ab1fb12dc35730c05af, 2ea52a2fb8e87067e26bbab4efb8872639240eb0, 147d89ee41434b97043c2dcb17a97dc151859baa, f82aac8162871e87027692b36af335a2375d4580, a75152d233370362eebedb2643592e7c883cc9fc, 25563b581ba3a1f263a00e8c9a97f5e7363be6fd |
| Linux/Linuxgeneric | 2.6.37 | Not reported |
Published upstream
Mar 2, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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().
Quoted source text, attributed separately from HOL analysis.