linux-ext4 - K3.18-lts : ext4/namei.c: hash used un-initialized

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>] [day] [month] [year] [list]

Message-ID: <CAMf7+LitG79FTMdsyAO_xLMGpaZgM02LkEaRJ1EZpu-W+SbU2Q@mail.gmail.com>
Date:	Fri, 10 Jun 2016 12:06:04 +0530
From:	pavi1729 <pavitra1729@...il.com>
To:	linux-ext4@...r.kernel.org
Subject: K3.18-lts : ext4/namei.c: hash used un-initialized

Hi,

LINK: http://lxr.free-electrons.com/source/fs/ext4/namei.c?v=3.18#L664

static struct dx_frame *
664 dx_probe(const struct qstr *d_name, struct inode *dir,
665          struct dx_hash_info *hinfo, struct dx_frame *frame_in)
666 {
...
...
690         if (d_name)
691                 ext4fs_dirhash(d_name->name, d_name->len, hinfo);
692         hash = hinfo->hash;

Wont 'hash' abve be un-initialized if 'd_name' is NULL OR is 'd_name'
guaranteed to be not NULL
in this call.

Thanks,
Pavi
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html