First published: Sun May 19 2024(Updated: )
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).
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Kernel | <4.19.312 | |
Linux Kernel | >=4.20<5.4.274 | |
Linux Kernel | >=5.5<5.10.215 | |
Linux Kernel | >=5.11<5.15.155 | |
Linux Kernel | >=5.16<6.1.86 | |
Linux Kernel | >=6.2<6.6.27 | |
Linux Kernel | >=6.7<6.8.6 | |
Debian Linux | =10.0 | |
debian/linux | 5.10.223-1 5.10.234-1 6.1.129-1 6.1.135-1 6.12.25-1 6.12.27-1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2023-52699 is classified as a vulnerability in the Linux kernel affecting the SysV filesystem.
To fix CVE-2023-52699, you should update your Linux kernel to the patched versions 5.10.223-1, 5.10.226-1, 6.1.119-1, 6.1.123-1, 6.12.10-1, or 6.12.11-1.
CVE-2023-52699 addresses an issue where sb_bread() can be called while holding pointers_lock, potentially causing sleep in atomic context.
Affected software versions for CVE-2023-52699 include certain prior releases of the Linux kernel before the aforementioned patched versions.
While not designated as critical, CVE-2023-52699 poses potential risks to system stability and performance due to its nature.