Answer in brief
CVE-2023-52699 records a Medium severity (CVSS 5.3) vulnerability in sysv: don't call sb_bread() with pointers_lock held. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (generic), Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (generic) and additional mapped packages. 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 5.3. 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), Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (generic), Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <13b33feb2ebddc2b1aa607f553566b18a4af1d76 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1b4fe801b5bedec2b622ddb18e5c9bf26c63d79f || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <674c1c4229e743070e09db63a23442950ff000d1 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <fd203d2c671bdee9ab77090ff394d3b71b627927 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <53cb1e52c9db618c08335984d1ca80db220ccf09 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <89e8524135a3902e7563a5a59b7b5ec1bf4904ac || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a69224223746ab96d43e5db9d22d136827b7e2d3 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f123dc86388cb669c3d6322702dc441abc35c31e | 13b33feb2ebddc2b1aa607f553566b18a4af1d76, 1b4fe801b5bedec2b622ddb18e5c9bf26c63d79f, 674c1c4229e743070e09db63a23442950ff000d1, fd203d2c671bdee9ab77090ff394d3b71b627927, 53cb1e52c9db618c08335984d1ca80db220ccf09, 89e8524135a3902e7563a5a59b7b5ec1bf4904ac, a69224223746ab96d43e5db9d22d136827b7e2d3, f123dc86388cb669c3d6322702dc441abc35c31e |
| Linux/Linuxgeneric | 2.6.12 | Not reported |
| Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFPgeneric | >=V3.1.0 <V3.1.5 | V3.1.5 |
| Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFPgeneric | >=V3.1.0 <V3.1.5 | V3.1.5 |
| Siemens/SIPLUS S7-1500 CPU 1518-4 PN/DP MFPgeneric | >=V3.1.0 <V3.1.5 | V3.1.5 |
Published upstream
May 19, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 15, 2026
In the Linux kernel, the following vulnerability has been resolved: sysv: don't call sb_bread() with pointers_lock held syzbot is reporting sleep in atomic context in SysV filesystem [1], for sb_bread() is called with rw_spinlock held. A "write_lock(&pointers_lock) => read_lock(&pointers_lock) deadlock" bug and a "sb_bread() with write_lock(&pointers_lock)" bug were introduced by "Replace BKL for chain locking with sysvfs-private rwlock" in Linux 2.5.12. Then, "[PATCH] err1-40: sysvfs locking fix" in Linux 2.6.8 fixed the former bug by moving pointers_lock lock to the callers, but instead introduced a "sb_bread() with read_lock(&pointers_lock)" bug (which made this problem easier to hit). Al Viro suggested that why not to do like get_branch()/get_block()/ find_shared() in Minix filesystem does. And doing like that is almost a revert of "[PATCH] err1-40: sysvfs locking fix" except that get_branch() from with find_shared() is called without write_lock(&pointers_lock).
Quoted source text, attributed separately from HOL analysis.