What is CVE-2023-52699?

CVE-2023-52699 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.3 out of 10, classified as a Improper Locking flaw (CWE-667). CVE-2023-52699 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2023-52699?

CVE-2023-52699 has a CVSS score of 5.3 out of 10, rated Medium severity. The vector string is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L.

Is there a patch available for CVE-2023-52699?

No patch is currently available for CVE-2023-52699. Monitor the NIST NVD and your Linux distribution's security advisories for updates.

Is CVE-2023-52699 actively exploited?

CVE-2023-52699 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is Improper Locking (CWE-667)?

The product does not properly acquire or release a lock, which can lead to unexpected behaviour. See MITRE CWE for full details: https://cwe.mitre.org/data/definitions/667.html

CVE-2023-52699

Medium

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

Package Linux Kernel

Published 2024-05-19

Last modified 2025-04-04

CVSS version 3.1

Patch available

Awaiting data

CVSS 3.1 score

5.3

out of 10

Medium

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

Low

Vector string

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Weakness type

CWE-667

CVE-2023-52699 is a Improper Locking vulnerability

What is Improper Locking?

The product does not properly acquire or release a lock, which can lead to unexpected behaviour. Learn more on MITRE CWE

References

The following references provide additional information about CVE-2023-52699 including vendor advisories, patch commits, exploit details, and third-party analysis. Links are sourced from the NIST NVD database.

Debian Security
https://lists.debian.org/debian-lts-announce/2024/06/msg00017.html

Mailing List Third Party Advisory
Debian Security
https://lists.debian.org/debian-lts-announce/2024/06/msg00020.html

Mailing List Third Party Advisory
Kernel patch commit
https://git.kernel.org/stable/c/13b33feb2ebddc2b1aa607f553566b18a4af1d76
Patch
Kernel patch commit
https://git.kernel.org/stable/c/1b4fe801b5bedec2b622ddb18e5c9bf26c63d79f
Patch
Kernel patch commit
https://git.kernel.org/stable/c/53cb1e52c9db618c08335984d1ca80db220ccf09
Patch

8 patch commits total View all on NVD

Details

CVE ID CVE-2023-52699

Severity Medium

CVSS score 5.3 / 10

CVSS version 3.1

Published 2024-05-19

Modified 2025-04-04

KEV No

Patch Awaiting data

Package linux

Frequently asked questions

What is CVE-2023-52699?

CVE-2023-52699 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.3 out of 10 , classified as an Improper Locking flaw (CWE-667) . CVE-2023-52699 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2023-52699?

CVE-2023-52699 has a CVSS score of 5.3 out of 10, rated Medium severity (CVSS 3.1). The vector string is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L.
Is there a patch available for CVE-2023-52699?

No patch is currently available for CVE-2023-52699. Monitor the NIST NVD and your Linux distribution's security advisories for updates.
Is CVE-2023-52699 actively exploited?

No — CVE-2023-52699 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.
What is Improper Locking (CWE-667)?

The product does not properly acquire or release a lock, which can lead to unexpected behaviour. View CWE-667 on MITRE CWE →