CVE-2023-52699: sysv: don't call sb_bread() with pointers_lock held
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).
Security readout for executives and security teams
Plain-English summary
CVE-2023-52699 is a Linux kernel SysV filesystem bug that can put the kernel into an unsafe sleep while holding a spin lock. The documented impact is availability loss, not data theft or corruption. It matters most for systems running affected kernels with SysV filesystem functionality present or reachable.
Executive priority
Treat this as routine but time-bound kernel maintenance. It is not evidenced as exploited, and impact is availability only, but kernel denial-of-service bugs can affect business continuity on shared or exposed infrastructure.
Technical view
The SysV filesystem called sb_bread() while pointers_lock was held, creating a sleep-in-atomic-context condition. The issue traces to historical locking changes and was resolved by restructuring the locking path. CVSS is 5.3 with availability impact only. The bundle provides Linux stable commit references and Debian LTS advisories.
Likely exposure
Exposure is limited to Linux systems running affected kernel builds where SysV filesystem code is present. The source bundle lists Linux as affected and provides stable kernel fixes plus Debian LTS advisories, but it does not identify specific distributions beyond Debian references or confirm default reachability.
Exploitation context
The bundle does not show active exploitation. KEV is false, and the public description references syzbot detection rather than real-world attacks. The CVSS vector is network, unauthenticated, and no user interaction, but the sources do not describe a concrete exploitation path.
Researcher notes
The strongest evidence is the upstream Linux resolution text and stable commit references. The affected-version data in the bundle is sparse and includes kernel release identifiers without distribution mapping. Avoid assuming exploitability beyond the CVSS and source description.
Mitigation direction
Apply vendor kernel updates containing the referenced SysV filesystem fix.
For Debian LTS systems, review and apply the cited Debian security updates.
Prioritize internet-facing or multi-tenant Linux systems first.
Check vendor advisories for exact package names and reboot requirements.
Disable unused SysV filesystem support only if vendor-supported and operationally safe.
Validation and detection
Inventory Linux kernel versions across servers, appliances, and container hosts.
Check whether installed kernels include one of the referenced stable fixes.
Review Debian LTS advisory status for applicable Debian hosts.
Confirm patched kernels are booted, not merely installed.
Monitor kernel logs for filesystem or lockup warnings after update.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2023-52699 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.