From: epirat07@gmail.com To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] lavfi/perlin: Fix out of bounds stack buffer write Date: Tue, 09 Jul 2024 14:41:16 +0200 Message-ID: <60EF3818-98FC-441B-87D5-4494623799E9@gmail.com> (raw) In-Reply-To: <ZokNqNoufsJwI5GO@mariano> On 6 Jul 2024, at 11:26, Stefano Sabatini wrote: > On date Tuesday 2024-07-02 20:38:00 +0200, Marvin Scholz wrote: >> An incorrect calculation in ff_perlin_init causes a write to the >> stack array at index 256, which is out of bounds. >> >> Fixes: CID1608711 >> --- >> libavfilter/perlin.c | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/libavfilter/perlin.c b/libavfilter/perlin.c >> index 09bae7ad33..ffad8c1e4e 100644 >> --- a/libavfilter/perlin.c >> +++ b/libavfilter/perlin.c >> @@ -129,7 +129,7 @@ int ff_perlin_init(FFPerlin *perlin, double period, int octaves, double persiste >> for (i = 0; i < 256; i++) { >> unsigned int random_idx = av_lfg_get(&lfg) % (256-i); >> uint8_t random_val = random_permutations[random_idx]; >> - random_permutations[random_idx] = random_permutations[256-i]; >> + random_permutations[random_idx] = random_permutations[255-i]; >> >> perlin->permutations[i] = perlin->permutations[i+256] = random_val; >> } > > Looks good, thanks. Please push then, I do not have commit access. > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > To unsubscribe, visit link above, or email > ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe". _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2024-07-09 12:41 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-07-02 18:38 Marvin Scholz 2024-07-06 9:26 ` Stefano Sabatini 2024-07-09 12:41 ` epirat07 [this message] 2024-07-10 16:19 ` Michael Niedermayer
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=60EF3818-98FC-441B-87D5-4494623799E9@gmail.com \ --to=epirat07@gmail.com \ --cc=ffmpeg-devel@ffmpeg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git