linux-kernel - [BUG] jfs: possible uninitialized-variable access in xtSplitUp()

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <6b3b3a56-b77c-aff7-c9f1-94a99d4929d2@gmail.com>
Date:   Sat, 31 Jul 2021 14:31:02 +0800
From:   Li Tuo <islituo@...il.com>
To:     shaggy@...nel.org
Cc:     jfs-discussion@...ts.sourceforge.net, linux-kernel@...r.kernel.org,
        baijiaju1990@...il.com
Subject: [BUG] jfs: possible uninitialized-variable access in xtSplitUp()

Hello,

Our static analysis tool finds a possible uninitialized-variable access 
in the jfs driver in Linux 5.14.0-rc3:

At the beginning of the function xtSplitUp(), the variable rbn is not 
initialized.
If sp->header.flag & BT_ROOT is true,
780:    rc = (sp->header.flag & BT_ROOT) ? xtSplitRoot(tid, ip, split, 
&rmp) : xtSplitPage(tid, ip, split, &rmp, &rbn);

the varialbe rbn will remain uninitialized.
However, it is accessed through:
814:    rcbn = rbn;

I am not quite sure whether this possible uninitialized-variable access 
is real and how to fix it if it is real.
Any feedback would be appreciated, thanks!

Reported-by: TOTE Robot <oslab@...nghua.edu.cn>

Best wishes,
Tuo Li