0.0
NA
CVE-2023-52759
Here is a title for the vulnerability: "Red Hat GFS2 Quota Denial of Service (DoS)"
Description
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
INFO
Published Date :
May 21, 2024, 4:15 p.m.
Last Modified :
Dec. 19, 2024, 11:15 a.m.
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Remotely Exploitable :
No
Impact Score :
Exploitability Score :
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2023-52759 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2023-52759 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Rejected by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Dec. 19, 2024
Action Type Old Value New Value -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Dec. 19, 2024
Action Type Old Value New Value Changed Description In the Linux kernel, the following vulnerability has been resolved: gfs2: ignore negated quota changes When lots of quota changes are made, there may be cases in which an inode's quota information is increased and then decreased, such as when blocks are added to a file, then deleted from it. If the timing is right, function do_qc can add pending quota changes to a transaction, then later, another call to do_qc can negate those changes, resulting in a net gain of 0. The quota_change information is recorded in the qc buffer (and qd element of the inode as well). The buffer is added to the transaction by the first call to do_qc, but a subsequent call changes the value from non-zero back to zero. At that point it's too late to remove the buffer_head from the transaction. Later, when the quota sync code is called, the zero-change qd element is discovered and flagged as an assert warning. If the fs is mounted with errors=panic, the kernel will panic. This is usually seen when files are truncated and the quota changes are negated by punch_hole/truncate which uses gfs2_quota_hold and gfs2_quota_unhold rather than block allocations that use gfs2_quota_lock and gfs2_quota_unlock which automatically do quota sync. This patch solves the problem by adding a check to qd_check_sync such that net-zero quota changes already added to the transaction are no longer deemed necessary to be synced, and skipped. In this case references are taken for the qd and the slot from do_qc so those need to be put. The normal sequence of events for a normal non-zero quota change is as follows: gfs2_quota_change do_qc qd_hold slot_hold Later, when the changes are to be synced: gfs2_quota_sync qd_fish qd_check_sync gets qd ref via lockref_get_not_dead do_sync do_qc(QC_SYNC) qd_put lockref_put_or_lock qd_unlock qd_put lockref_put_or_lock In the net-zero change case, we add a check to qd_check_sync so it puts the qd and slot references acquired in gfs2_quota_change and skip the unneeded sync. Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. Removed Reference kernel.org: https://git.kernel.org/stable/c/119565e566f91ff3588ffcd5812f0c8061586c6b Removed Reference kernel.org: https://git.kernel.org/stable/c/1c28dace66015b675a343b89b0c87abbfda05ff4 Removed Reference kernel.org: https://git.kernel.org/stable/c/212f112fe5e90e98eb8d48585682880dae139f4c Removed Reference kernel.org: https://git.kernel.org/stable/c/2a054b87a1b799b391e578597a42ee6e57a987ae Removed Reference kernel.org: https://git.kernel.org/stable/c/2bb42a27a92ff3984c9fa5fbe128eced3ea693f2 Removed Reference kernel.org: https://git.kernel.org/stable/c/4c6a08125f2249531ec01783a5f4317d7342add5 Removed Reference kernel.org: https://git.kernel.org/stable/c/50e33567bc4a1c4ed79a1d289fe93c9a26491848 Removed Reference kernel.org: https://git.kernel.org/stable/c/53fc16c1ad84f5467ec24341670b63aa759335d3 Removed Reference kernel.org: https://git.kernel.org/stable/c/5bfda356e903633d16ae1bac1ee38364e12628a3 Removed Reference kernel.org: https://git.kernel.org/stable/c/b4deec69fe32b58dc5fb4ace52456ece85b75561 Removed Reference CVE: https://git.kernel.org/stable/c/119565e566f91ff3588ffcd5812f0c8061586c6b Removed Reference CVE: https://git.kernel.org/stable/c/1c28dace66015b675a343b89b0c87abbfda05ff4 Removed Reference CVE: https://git.kernel.org/stable/c/212f112fe5e90e98eb8d48585682880dae139f4c Removed Reference CVE: https://git.kernel.org/stable/c/2a054b87a1b799b391e578597a42ee6e57a987ae Removed Reference CVE: https://git.kernel.org/stable/c/2bb42a27a92ff3984c9fa5fbe128eced3ea693f2 Removed Reference CVE: https://git.kernel.org/stable/c/4c6a08125f2249531ec01783a5f4317d7342add5 Removed Reference CVE: https://git.kernel.org/stable/c/53fc16c1ad84f5467ec24341670b63aa759335d3 Removed Reference CVE: https://git.kernel.org/stable/c/5bfda356e903633d16ae1bac1ee38364e12628a3 Removed Reference CVE: https://git.kernel.org/stable/c/b4deec69fe32b58dc5fb4ace52456ece85b75561 -
CVE Modified by af854a3a-2127-422b-91ae-364da2661108
Nov. 21, 2024
Action Type Old Value New Value Added Reference https://git.kernel.org/stable/c/119565e566f91ff3588ffcd5812f0c8061586c6b Added Reference https://git.kernel.org/stable/c/1c28dace66015b675a343b89b0c87abbfda05ff4 Added Reference https://git.kernel.org/stable/c/212f112fe5e90e98eb8d48585682880dae139f4c Added Reference https://git.kernel.org/stable/c/2a054b87a1b799b391e578597a42ee6e57a987ae Added Reference https://git.kernel.org/stable/c/2bb42a27a92ff3984c9fa5fbe128eced3ea693f2 Added Reference https://git.kernel.org/stable/c/4c6a08125f2249531ec01783a5f4317d7342add5 Added Reference https://git.kernel.org/stable/c/53fc16c1ad84f5467ec24341670b63aa759335d3 Added Reference https://git.kernel.org/stable/c/5bfda356e903633d16ae1bac1ee38364e12628a3 Added Reference https://git.kernel.org/stable/c/b4deec69fe32b58dc5fb4ace52456ece85b75561 -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Oct. 17, 2024
Action Type Old Value New Value Added Reference kernel.org https://git.kernel.org/stable/c/50e33567bc4a1c4ed79a1d289fe93c9a26491848 [No types assigned] -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
May. 29, 2024
Action Type Old Value New Value -
CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
May. 21, 2024
Action Type Old Value New Value Added Description In the Linux kernel, the following vulnerability has been resolved: gfs2: ignore negated quota changes When lots of quota changes are made, there may be cases in which an inode's quota information is increased and then decreased, such as when blocks are added to a file, then deleted from it. If the timing is right, function do_qc can add pending quota changes to a transaction, then later, another call to do_qc can negate those changes, resulting in a net gain of 0. The quota_change information is recorded in the qc buffer (and qd element of the inode as well). The buffer is added to the transaction by the first call to do_qc, but a subsequent call changes the value from non-zero back to zero. At that point it's too late to remove the buffer_head from the transaction. Later, when the quota sync code is called, the zero-change qd element is discovered and flagged as an assert warning. If the fs is mounted with errors=panic, the kernel will panic. This is usually seen when files are truncated and the quota changes are negated by punch_hole/truncate which uses gfs2_quota_hold and gfs2_quota_unhold rather than block allocations that use gfs2_quota_lock and gfs2_quota_unlock which automatically do quota sync. This patch solves the problem by adding a check to qd_check_sync such that net-zero quota changes already added to the transaction are no longer deemed necessary to be synced, and skipped. In this case references are taken for the qd and the slot from do_qc so those need to be put. The normal sequence of events for a normal non-zero quota change is as follows: gfs2_quota_change do_qc qd_hold slot_hold Later, when the changes are to be synced: gfs2_quota_sync qd_fish qd_check_sync gets qd ref via lockref_get_not_dead do_sync do_qc(QC_SYNC) qd_put lockref_put_or_lock qd_unlock qd_put lockref_put_or_lock In the net-zero change case, we add a check to qd_check_sync so it puts the qd and slot references acquired in gfs2_quota_change and skip the unneeded sync. Added Reference kernel.org https://git.kernel.org/stable/c/1c28dace66015b675a343b89b0c87abbfda05ff4 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/b4deec69fe32b58dc5fb4ace52456ece85b75561 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/2bb42a27a92ff3984c9fa5fbe128eced3ea693f2 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/2a054b87a1b799b391e578597a42ee6e57a987ae [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/5bfda356e903633d16ae1bac1ee38364e12628a3 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/53fc16c1ad84f5467ec24341670b63aa759335d3 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/212f112fe5e90e98eb8d48585682880dae139f4c [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/119565e566f91ff3588ffcd5812f0c8061586c6b [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/4c6a08125f2249531ec01783a5f4317d7342add5 [No types assigned]
EPSS is a daily estimate of the probability of exploitation activity
being observed over the next 30 days. Following chart shows the EPSS
score history of the vulnerability.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2023-52759 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2023-52759
weaknesses.