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: <176976672483.101188.14038361815799165327.b4-ty@kernel.org>
Date: Fri, 30 Jan 2026 10:52:04 +0100
From: Carlos Maiolino <cem@...nel.org>
To: Raphael Pinsonneault-Thibeault <rpthibeault@...il.com>
Cc: chandanbabu@...nel.org, djwong@...nel.org, bfoster@...hat.com, 
 linux-xfs@...r.kernel.org, linux-kernel@...r.kernel.org, 
 syzbot+9f6d080dece587cfdd4c@...kaller.appspotmail.com, 
 Christoph Hellwig <hch@....de>
Subject: Re: [PATCH v6] xfs: validate log record version against superblock
 log version

On Thu, 29 Jan 2026 13:50:21 -0500, Raphael Pinsonneault-Thibeault wrote:
> Syzbot creates a fuzzed record where xfs_has_logv2() but the
> xlog_rec_header h_version != XLOG_VERSION_2. This causes a
> KASAN: slab-out-of-bounds read in xlog_do_recovery_pass() ->
> xlog_recover_process() -> xlog_cksum().
> 
> Fix by adding a check to xlog_valid_rec_header() to abort journal
> recovery if the xlog_rec_header h_version does not match the super
> block log version.
> 
> [...]

Applied to for-next, thanks!

[1/1] xfs: validate log record version against superblock log version
      commit: 44b9553c3dd043f14903d8ae5d4e7a9797c6d92e

Best regards,
-- 
Carlos Maiolino <cem@...nel.org>


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ