[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025123036-CVE-2023-54313-f889@gregkh>
Date: Tue, 30 Dec 2025 13:24:06 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-54313: ovl: fix null pointer dereference in ovl_get_acl_rcu()
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ovl: fix null pointer dereference in ovl_get_acl_rcu()
Following process:
P1 P2
path_openat
link_path_walk
may_lookup
inode_permission(rcu)
ovl_permission
acl_permission_check
check_acl
get_cached_acl_rcu
ovl_get_inode_acl
realinode = ovl_inode_real(ovl_inode)
drop_cache
__dentry_kill(ovl_dentry)
iput(ovl_inode)
ovl_destroy_inode(ovl_inode)
dput(oi->__upperdentry)
dentry_kill(upperdentry)
dentry_unlink_inode
upperdentry->d_inode = NULL
ovl_inode_upper
upperdentry = ovl_i_dentry_upper(ovl_inode)
d_inode(upperdentry) // returns NULL
IS_POSIXACL(realinode) // NULL pointer dereference
, will trigger an null pointer dereference at realinode:
[ 205.472797] BUG: kernel NULL pointer dereference, address:
0000000000000028
[ 205.476701] CPU: 2 PID: 2713 Comm: ls Not tainted
6.3.0-12064-g2edfa098e750-dirty #1216
[ 205.478754] RIP: 0010:do_ovl_get_acl+0x5d/0x300
[ 205.489584] Call Trace:
[ 205.489812] <TASK>
[ 205.490014] ovl_get_inode_acl+0x26/0x30
[ 205.490466] get_cached_acl_rcu+0x61/0xa0
[ 205.490908] generic_permission+0x1bf/0x4e0
[ 205.491447] ovl_permission+0x79/0x1b0
[ 205.491917] inode_permission+0x15e/0x2c0
[ 205.492425] link_path_walk+0x115/0x550
[ 205.493311] path_lookupat.isra.0+0xb2/0x200
[ 205.493803] filename_lookup+0xda/0x240
[ 205.495747] vfs_fstatat+0x7b/0xb0
Fetch a reproducer in [Link].
Use the helper ovl_i_path_realinode() to get realinode and then do
non-nullptr checking.
The Linux kernel CVE team has assigned CVE-2023-54313 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.15 with commit 332f606b32b6291a944c8cf23b91f53a6e676525 and fixed in 5.15.121 with commit d97481c7b2739a704848bb3c01f224dc71bdf78e
Issue introduced in 5.15 with commit 332f606b32b6291a944c8cf23b91f53a6e676525 and fixed in 6.1.40 with commit c4a5fb1ae5d3f02d3227afde2b9339994389463d
Issue introduced in 5.15 with commit 332f606b32b6291a944c8cf23b91f53a6e676525 and fixed in 6.4.4 with commit d536af163c53ce9f9bcfe87d2e9946f06f1a7ea4
Issue introduced in 5.15 with commit 332f606b32b6291a944c8cf23b91f53a6e676525 and fixed in 6.5 with commit f4e19e595cc2e76a8a58413eb19d3d9c51328b53
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-54313
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/overlayfs/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/d97481c7b2739a704848bb3c01f224dc71bdf78e
https://git.kernel.org/stable/c/c4a5fb1ae5d3f02d3227afde2b9339994389463d
https://git.kernel.org/stable/c/d536af163c53ce9f9bcfe87d2e9946f06f1a7ea4
https://git.kernel.org/stable/c/f4e19e595cc2e76a8a58413eb19d3d9c51328b53
Powered by blists - more mailing lists