From:   Mark Brown <broonie@kernel.org>
To:     Ravulapati Vishnu Vardhan Rao <quic_visr@quicinc.com>
Cc:     Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
        Banajit Goswami <bgoswami@quicinc.com>,
        Liam Girdwood <lgirdwood@gmail.com>,
        Jaroslav Kysela <perex@perex.cz>,
        Takashi Iwai <tiwai@suse.com>,
        "moderated list:QCOM AUDIO (ASoC) DRIVERS" 
        <alsa-devel@alsa-project.org>,
        open list <linux-kernel@vger.kernel.org>
In-Reply-To: <20230304080702.609-1-quic_visr@quicinc.com>
References: <20230304080702.609-1-quic_visr@quicinc.com>
Subject: Re: [PATCH] ASoC: codecs: tx-macro: Fix for KASAN:
 slab-out-of-bounds
Message-Id: <167810674220.45838.12997652294866709663.b4-ty@kernel.org>
Date:   Mon, 06 Mar 2023 12:45:42 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Sat, 04 Mar 2023 13:37:02 +0530, Ravulapati Vishnu Vardhan Rao wrote:
> When we run syzkaller we get below Out of Bound.
>     "KASAN: slab-out-of-bounds Read in regcache_flat_read"
> 
>     Below is the backtrace of the issue:
> 
>     dump_backtrace+0x0/0x4c8
>     show_stack+0x34/0x44
>     dump_stack_lvl+0xd8/0x118
>     print_address_description+0x30/0x2d8
>     kasan_report+0x158/0x198
>     __asan_report_load4_noabort+0x44/0x50
>     regcache_flat_read+0x10c/0x110
>     regcache_read+0xf4/0x180
>     _regmap_read+0xc4/0x278
>     _regmap_update_bits+0x130/0x290
>     regmap_update_bits_base+0xc0/0x15c
>     snd_soc_component_update_bits+0xa8/0x22c
>     snd_soc_component_write_field+0x68/0xd4
>     tx_macro_digital_mute+0xec/0x140
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/1] ASoC: codecs: tx-macro: Fix for KASAN: slab-out-of-bounds
      commit: e5e7e398f6bb7918dab0612eb6991f7bae95520d

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark