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: <176734657056.18270.16280115441388515041.b4-ty@oss.qualcomm.com>
Date: Fri,  2 Jan 2026 10:36:13 +0100
From: Bartosz Golaszewski <bartosz.golaszewski@....qualcomm.com>
To: Linus Walleij <linusw@...nel.org>, Bartosz Golaszewski <brgl@...nel.org>,
        Bartosz Golaszewski <bartosz.golaszewski@....qualcomm.com>
Cc: linux-kernel@...r.kernel.org, linux-gpio@...r.kernel.org,
        Paweł Narewski <pawel.narewski@...ia.com>,
        Jakub Lewalski <jakub.lewalski@...ia.com>
Subject: Re: [PATCH v2] gpiolib: fix race condition for gdev->srcu


On Wed, 24 Dec 2025 09:26:40 +0100, Bartosz Golaszewski wrote:
> If two drivers were calling gpiochip_add_data_with_key(), one may be
> traversing the srcu-protected list in gpio_name_to_desc(), meanwhile
> other has just added its gdev in gpiodev_add_to_list_unlocked().
> This creates a non-mutexed and non-protected timeframe, when one
> instance is dereferencing and using &gdev->srcu, before the other
> has initialized it, resulting in crash:
> 
> [...]

Applied, thanks!

[1/1] gpiolib: fix race condition for gdev->srcu
      commit: a7ac22d53d0990152b108c3f4fe30df45fcb0181

Best regards,
-- 
Bartosz Golaszewski <bartosz.golaszewski@....qualcomm.com>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ