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: <176770263471.676302.4742936561051912973.b4-ty@kernel.dk>
Date: Tue, 06 Jan 2026 05:30:34 -0700
From: Jens Axboe <axboe@...nel.dk>
To: Raphael Pinsonneault-Thibeault <rpthibeault@...il.com>
Cc: jack@...e.cz, syzbot+3ee481e21fd75e14c397@...kaller.appspotmail.com, 
 linux-block@...r.kernel.org, linux-kernel@...r.kernel.org, 
 linux-kernel-mentees@...ts.linux.dev, 
 Yongpeng Yang <yangyongpeng@...omi.com>
Subject: Re: [PATCH v2] loop: don't change loop device under exclusive
 opener in loop_set_status


On Wed, 17 Dec 2025 14:00:40 -0500, Raphael Pinsonneault-Thibeault wrote:
> loop_set_status() is allowed to change the loop device while there
> are other openers of the device, even exclusive ones.
> 
> In this case, it causes a KASAN: slab-out-of-bounds Read in
> ext4_search_dir(), since when looking for an entry in an inlined
> directory, e_value_offs is changed underneath the filesystem by
> loop_set_status().
> 
> [...]

Applied, thanks!

[1/1] loop: don't change loop device under exclusive opener in loop_set_status
      commit: 08e136ebd193eae7d5eff4c66d576c4a2dabdc3f

Best regards,
-- 
Jens Axboe




Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ