[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025100709-CVE-2023-53683-249f@gregkh>
Date: Tue, 7 Oct 2025 17:21:42 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-53683: fs: hfsplus: remove WARN_ON() from hfsplus_cat_{read,write}_inode()
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
fs: hfsplus: remove WARN_ON() from hfsplus_cat_{read,write}_inode()
syzbot is hitting WARN_ON() in hfsplus_cat_{read,write}_inode(), for
crafted filesystem image can contain bogus length. There conditions are
not kernel bugs that can justify kernel to panic.
The Linux kernel CVE team has assigned CVE-2023-53683 to this issue.
Affected and fixed versions
===========================
Fixed in 4.14.316 with commit 61af77acd039ffd221bf7adf0dc95d0a4d377505
Fixed in 4.19.284 with commit c074913b12db3632b11588b31bbfb0fa80a0a1c9
Fixed in 5.4.244 with commit a75d9211a07fed513c08c5d4861c4a36ac6a74fe
Fixed in 5.10.181 with commit c8daee66585897a4c90d937c91e762100237bff9
Fixed in 5.15.113 with commit 37cab61a52d6f42b2d961c51bcf369f09e235fb5
Fixed in 6.1.30 with commit 48960a503fcec76d3f72347b7e679dda08ca43be
Fixed in 6.3.4 with commit 3a9d68d84b2e41ba3f2a727b36f035fad6800492
Fixed in 6.4 with commit 81b21c0f0138ff5a499eafc3eb0578ad2a99622c
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2023-53683
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
fs/hfsplus/inode.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/61af77acd039ffd221bf7adf0dc95d0a4d377505
https://git.kernel.org/stable/c/c074913b12db3632b11588b31bbfb0fa80a0a1c9
https://git.kernel.org/stable/c/a75d9211a07fed513c08c5d4861c4a36ac6a74fe
https://git.kernel.org/stable/c/c8daee66585897a4c90d937c91e762100237bff9
https://git.kernel.org/stable/c/37cab61a52d6f42b2d961c51bcf369f09e235fb5
https://git.kernel.org/stable/c/48960a503fcec76d3f72347b7e679dda08ca43be
https://git.kernel.org/stable/c/3a9d68d84b2e41ba3f2a727b36f035fad6800492
https://git.kernel.org/stable/c/81b21c0f0138ff5a499eafc3eb0578ad2a99622c
Powered by blists - more mailing lists