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-prev] [day] [month] [year] [list]
Message-Id: <165849767595.303416.2399065700843216204.b4-ty@mit.edu>
Date:   Fri, 22 Jul 2022 09:58:17 -0400
From:   "Theodore Ts'o" <tytso@....edu>
To:     linux-ext4@...r.kernel.org, Lukas Czerner <lczerner@...hat.com>
Cc:     "Theodore Ts'o" <tytso@....edu>,
        syzbot+15cd994e273307bf5cfa@...kaller.appspotmail.com,
        tadeusz.struk@...aro.org
Subject: Re: [PATCH] ext4: block range must be validated before use in ext4_mb_clear_bb()

On Thu, 14 Jul 2022 18:59:03 +0200, Lukas Czerner wrote:
> Block range to free is validated in ext4_free_blocks() using
> ext4_inode_block_valid() and then it's passed to ext4_mb_clear_bb().
> However in some situations on bigalloc file system the range might be
> adjusted after the validation in ext4_free_blocks() which can lead to
> troubles on corrupted file systems such as one found by syzkaller that
> resulted in the following BUG
> 
> [...]

Applied, thanks!

[1/1] ext4: block range must be validated before use in ext4_mb_clear_bb()
      commit: 91e204c46741b198693dd88bd7b03a5b5fe0ce17

Best regards,
-- 
Theodore Ts'o <tytso@....edu>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ