CVE-2023-52759

linux: In the Linux kernel, the following vulnerability has been resolved: gfs2: ignore negated quota changes When lots of...

CVE-2023-52759 is fixed in 22 products on 1 platform, first by CVE-2023-52759, released May 21, 2024. It is not reported as exploited. Patch Radar priority: Routine.

Routine
CVSS
n/a
No vendor severity
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
n/a

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.

Where it's fixed

ProductFixed inFixReleased
Linux
dtb-aarch64 · opensuse-leap 15.6 6.4.0-150600.23.14.1 SUSE-SU-2024:2571-1 Jul 22, 2024
kernel-64kb · opensuse-leap 15.6 6.4.0-150600.23.14.1 SUSE-SU-2024:2571-1 Jul 22, 2024
kernel-64kb · sles 15.6 6.4.0-150600.23.14.1 SUSE-SU-2024:2571-1 Jul 22, 2024
kernel-azure · opensuse-leap 15.6 6.4.0-150600.8.8.2 SUSE-SU-2024:2896-1 Aug 13, 2024
kernel-azure · sles 15.6 6.4.0-150600.8.8.2 SUSE-SU-2024:2896-1 Aug 13, 2024
kernel-debug · opensuse-leap 15.6 6.4.0-150600.23.14.2 SUSE-SU-2024:2571-1 Jul 22, 2024
kernel-default · opensuse-leap 15.6 6.4.0-150600.23.14.2 SUSE-SU-2024:2571-1 Jul 22, 2024
kernel-default · sles 15.6 6.4.0-150600.23.14.2 SUSE-SU-2024:2571-1 Jul 22, 2024
kernel-default-base · opensuse-leap 15.6 6.4.0-150600.23.14.2.150600.12.4.3 SUSE-SU-2024:2571-1 Jul 22, 2024
kernel-default-base · sles 15.6 6.4.0-150600.23.14.2.150600.12.4.3 SUSE-SU-2024:2571-1 Jul 22, 2024
kernel-docs · opensuse-leap 15.6 6.4.0-150600.23.14.2 SUSE-SU-2024:2571-1 Jul 22, 2024
kernel-docs · sles 15.6 6.4.0-150600.23.14.2 SUSE-SU-2024:2571-1 Jul 22, 2024
kernel-kvmsmall · opensuse-leap 15.6 6.4.0-150600.23.14.2 SUSE-SU-2024:2571-1 Jul 22, 2024
kernel-livepatch-SLE15-SP6-RT_Update_1 · sles 15.6 1-150600.1.5.1 SUSE-SU-2024:2973-1 Aug 20, 2024
kernel-livepatch-SLE15-SP6_Update_2 · sles 15.6 1-150600.13.3.2 SUSE-SU-2024:2571-1 Jul 22, 2024
kernel-obs-build · opensuse-leap 15.6 6.4.0-150600.23.14.2 SUSE-SU-2024:2571-1 Jul 22, 2024
kernel-obs-build · sles 15.6 6.4.0-150600.23.14.2 SUSE-SU-2024:2571-1 Jul 22, 2024
kernel-obs-qa · opensuse-leap 15.6 6.4.0-150600.23.14.2 SUSE-SU-2024:2571-1 Jul 22, 2024
kernel-rt · opensuse-leap 15.6 6.4.0-150600.10.5.1 SUSE-SU-2024:2973-1 Aug 20, 2024
kernel-rt_debug · opensuse-leap 15.6 6.4.0-150600.10.5.1 SUSE-SU-2024:2973-1 Aug 20, 2024
kernel-source · opensuse-leap 15.6 6.4.0-150600.23.14.2 SUSE-SU-2024:2571-1 Jul 22, 2024
kernel-source · sles 15.6 6.4.0-150600.23.14.2 SUSE-SU-2024:2571-1 Jul 22, 2024
kernel-source-azure · opensuse-leap 15.6 6.4.0-150600.8.8.2 SUSE-SU-2024:2896-1 Aug 13, 2024
kernel-source-azure · sles 15.6 6.4.0-150600.8.8.2 SUSE-SU-2024:2896-1 Aug 13, 2024
kernel-source-rt · opensuse-leap 15.6 6.4.0-150600.10.5.1 SUSE-SU-2024:2973-1 Aug 20, 2024
kernel-syms · opensuse-leap 15.6 6.4.0-150600.23.14.2 SUSE-SU-2024:2571-1 Jul 22, 2024
kernel-syms · sles 15.6 6.4.0-150600.23.14.2 SUSE-SU-2024:2571-1 Jul 22, 2024
kernel-syms-azure · opensuse-leap 15.6 6.4.0-150600.8.8.1 SUSE-SU-2024:2896-1 Aug 13, 2024
kernel-syms-azure · sles 15.6 6.4.0-150600.8.8.1 SUSE-SU-2024:2896-1 Aug 13, 2024
kernel-syms-rt · opensuse-leap 15.6 6.4.0-150600.10.5.1 SUSE-SU-2024:2973-1 Aug 20, 2024
kernel-zfcpdump · opensuse-leap 15.6 6.4.0-150600.23.14.2 SUSE-SU-2024:2571-1 Jul 22, 2024
kernel-zfcpdump · sles 15.6 6.4.0-150600.23.14.2 SUSE-SU-2024:2571-1 Jul 22, 2024
linux · Debian 11.6 (bullseye) 5.10.205-1 CVE-2023-52759 May 21, 2024
linux · Debian 12.15 (bookworm) 6.1.64-1 CVE-2023-52759 May 21, 2024
linux · Debian 13.5 (trixie) 6.6.8-1 CVE-2023-52759 May 21, 2024

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.