From: Sasha Levin <sashal@kernel.org>
To: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Cc: Joel Granados <j.granados@samsung.com>,
kernel test robot <oliver.sang@intel.com>,
Luis Chamberlain <mcgrof@kernel.org>,
Sasha Levin <sashal@kernel.org>,
keescook@chromium.org, linux-fsdevel@vger.kernel.org
Subject: [PATCH AUTOSEL 6.7 09/21] sysctl: Fix out of bounds access for empty sysctl registers
Date: Mon, 15 Jan 2024 20:03:46 -0500 [thread overview]
Message-ID: <20240116010422.217925-9-sashal@kernel.org> (raw)
In-Reply-To: <20240116010422.217925-1-sashal@kernel.org>
From: Joel Granados <j.granados@samsung.com>
[ Upstream commit 315552310c7de92baea4e570967066569937a843 ]
When registering tables to the sysctl subsystem there is a check to see
if header is a permanently empty directory (used for mounts). This check
evaluates the first element of the ctl_table. This results in an out of
bounds evaluation when registering empty directories.
The function register_sysctl_mount_point now passes a ctl_table of size
1 instead of size 0. It now relies solely on the type to identify
a permanently empty register.
Make sure that the ctl_table has at least one element before testing for
permanent emptiness.
Signed-off-by: Joel Granados <j.granados@samsung.com>
Reported-by: kernel test robot <oliver.sang@intel.com>
Closes: https://lore.kernel.org/oe-lkp/202311201431.57aae8f3-oliver.sang@intel.com
Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
---
fs/proc/proc_sysctl.c | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/fs/proc/proc_sysctl.c b/fs/proc/proc_sysctl.c
index 8064ea76f80b..84abf98340a0 100644
--- a/fs/proc/proc_sysctl.c
+++ b/fs/proc/proc_sysctl.c
@@ -44,7 +44,7 @@ static struct ctl_table sysctl_mount_point[] = {
*/
struct ctl_table_header *register_sysctl_mount_point(const char *path)
{
- return register_sysctl_sz(path, sysctl_mount_point, 0);
+ return register_sysctl(path, sysctl_mount_point);
}
EXPORT_SYMBOL(register_sysctl_mount_point);
@@ -233,7 +233,8 @@ static int insert_header(struct ctl_dir *dir, struct ctl_table_header *header)
return -EROFS;
/* Am I creating a permanently empty directory? */
- if (sysctl_is_perm_empty_ctl_table(header->ctl_table)) {
+ if (header->ctl_table_size > 0 &&
+ sysctl_is_perm_empty_ctl_table(header->ctl_table)) {
if (!RB_EMPTY_ROOT(&dir->root))
return -EINVAL;
sysctl_set_perm_empty_ctl_header(dir_h);
@@ -1213,6 +1214,10 @@ static bool get_links(struct ctl_dir *dir,
struct ctl_table_header *tmp_head;
struct ctl_table *entry, *link;
+ if (header->ctl_table_size == 0 ||
+ sysctl_is_perm_empty_ctl_table(header->ctl_table))
+ return true;
+
/* Are there links available for every entry in table? */
list_for_each_table_entry(entry, header) {
const char *procname = entry->procname;
--
2.43.0
next prev parent reply other threads:[~2024-01-16 1:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 1:03 [PATCH AUTOSEL 6.7 01/21] s390/boot: always align vmalloc area on segment boundary Sasha Levin
2024-01-16 1:03 ` [PATCH AUTOSEL 6.7 02/21] arch: consolidate arch_irq_work_raise prototypes Sasha Levin
2024-01-16 1:03 ` [PATCH AUTOSEL 6.7 03/21] arch: fix asm-offsets.c building with -Wmissing-prototypes Sasha Levin
2024-01-16 1:03 ` [PATCH AUTOSEL 6.7 04/21] s390/vfio-ap: fix sysfs status attribute for AP queue devices Sasha Levin
2024-01-16 1:03 ` [PATCH AUTOSEL 6.7 05/21] Hexagon: Make pfn accessors statics inlines Sasha Levin
2024-01-16 1:03 ` [PATCH AUTOSEL 6.7 06/21] s390/ptrace: handle setting of fpc register correctly Sasha Levin
2024-01-16 1:03 ` [PATCH AUTOSEL 6.7 07/21] KVM: s390: fix setting of fpc register Sasha Levin
2024-01-16 1:03 ` [PATCH AUTOSEL 6.7 08/21] arm64: Fix circular header dependency Sasha Levin
2024-01-16 1:03 ` Sasha Levin [this message]
2024-01-16 1:03 ` [PATCH AUTOSEL 6.7 10/21] SUNRPC: Fix a suspicious RCU usage warning Sasha Levin
2024-01-16 1:03 ` [PATCH AUTOSEL 6.7 11/21] ext4: enable dioread_nolock as default for bs < ps case Sasha Levin
2024-01-16 1:03 ` [PATCH AUTOSEL 6.7 12/21] ext4: treat end of range as exclusive in ext4_zero_range() Sasha Levin
2024-01-16 1:03 ` [PATCH AUTOSEL 6.7 13/21] smb: client: Fix minor whitespace errors and warnings Sasha Levin
2024-01-16 1:03 ` [PATCH AUTOSEL 6.7 14/21] smb: client: fix renaming of reparse points Sasha Levin
2024-01-16 1:03 ` [PATCH AUTOSEL 6.7 15/21] smb: client: fix hardlinking " Sasha Levin
2024-01-16 1:03 ` [PATCH AUTOSEL 6.7 16/21] cifs: fix in logging in cifs_chan_update_iface Sasha Levin
2024-01-16 1:03 ` [PATCH AUTOSEL 6.7 17/21] ecryptfs: Reject casefold directory inodes Sasha Levin
2024-01-16 1:03 ` [PATCH AUTOSEL 6.7 18/21] ext4: fix inconsistent between segment fstrim and full fstrim Sasha Levin
2024-01-16 1:03 ` [PATCH AUTOSEL 6.7 19/21] ext4: unify the type of flexbg_size to unsigned int Sasha Levin
2024-01-16 1:03 ` [PATCH AUTOSEL 6.7 20/21] ext4: remove unnecessary check from alloc_flex_gd() Sasha Levin
2024-01-16 1:03 ` [PATCH AUTOSEL 6.7 21/21] ext4: avoid online resizing failures due to oversized flex bg Sasha Levin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240116010422.217925-9-sashal@kernel.org \
--to=sashal@kernel.org \
--cc=j.granados@samsung.com \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=oliver.sang@intel.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox