CVE-2023-52699

What it is

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).

At a glance

Exploitability

Can be exploited over the network without logging in. Limited direct impact.

Exploit odds

1.0% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2024-05-19 11:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-15 01:17 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 1.0% in the next 30 days (EPSS).
• Severity: 5.3 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2024-05-19 11:15 UTC

Last modified

2026-10-15 01:17 UTC

Exploit probability

1.0% · EPSS, next 30 days

Weakness

CWE-667

Record status

Modified

Affected

• Linux Kernel < 4.19.312
• Linux Kernel < 5.4.274
• Linux Kernel < 5.10.215
• Linux Kernel < 5.15.155
• Linux Kernel < 6.1.86
• Linux Kernel < 6.6.27
• Linux Kernel < 6.8.6
• Debian Linux 10.0

Attack profile CVSS 3.1 · 5.3

Attack vector

Network

Complexity

Low

Privileges needed

None

User interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

Low

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-52699.md and follow it. Check whether this project is affected by CVE-2023-52699. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge