linux-kernel - Re: [PATCH] Bluetooth: btrtl: Prevent potential NULL dereference

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: 
 <174362823399.1678044.12965511758413449194.git-patchwork-notify@kernel.org>
Date: Wed, 02 Apr 2025 21:10:33 +0000
From: patchwork-bot+bluetooth@...nel.org
To: Dan Carpenter <dan.carpenter@...aro.org>
Cc: martin.blumenstingl@...glemail.com, marcel@...tmann.org,
 luiz.dentz@...il.com, jeremy@...ine.org, hdegoede@...hat.com,
 linux-bluetooth@...r.kernel.org, linux-kernel@...r.kernel.org,
 kernel-janitors@...r.kernel.org
Subject: Re: [PATCH] Bluetooth: btrtl: Prevent potential NULL dereference

Hello:

This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@...el.com>:

On Wed, 2 Apr 2025 14:01:41 +0300 you wrote:
> The btrtl_initialize() function checks that rtl_load_file() either
> had an error or it loaded a zero length file.  However, if it loaded
> a zero length file then the error code is not set correctly.  It
> results in an error pointer vs NULL bug, followed by a NULL pointer
> dereference.  This was detected by Smatch:
> 
> drivers/bluetooth/btrtl.c:592 btrtl_initialize() warn: passing zero to 'ERR_PTR'
> 
> [...]

Here is the summary with links:
  - Bluetooth: btrtl: Prevent potential NULL dereference
    https://git.kernel.org/bluetooth/bluetooth-next/c/113f1345ce0c

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html