Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Roy Kollen Svendsen <roykollensvendsen@gmail.com>
Cc: Jesse Van Gavere <jesseevg@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/qt6base: fix CVE-2024-39936
Date: Thu, 15 Aug 2024 14:36:52 +0200	[thread overview]
Message-ID: <20240815143652.7265bd45@windsurf> (raw)
In-Reply-To: <CA+R_deriCwom9cj5cYO3R4P9NXXJrHdCvYCTqzkH1UAAOCwdOA@mail.gmail.com>

Hello Roy,

On Thu, 15 Aug 2024 13:19:08 +0200
Roy Kollen Svendsen <roykollensvendsen@gmail.com> wrote:

> CVE-2024-36048-qtnetworkauth-6.7.diff:
>   - Does not apply since we have not yet added a package for the
> qtnetworkauth module.
> 
> CVE-2024-33861-qtbase-6.7.diff:
>   - It is already in 6.7.2:
>     $ git branch --contains 7c4e1357e49baebdd2d20710fccb5604cbb36c0d
>       6.7.1
>       6.7.2
> 
>   - As Jesse pointed out earlier the bugzilla report dos not mention 6.4.x:
>     https://bugzilla.suse.com/show_bug.cgi?id=1223917
> 
>     The patch applies without warnings/errors to 6.4.3 though.

ACK, thanks, makes sense!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-08-15 12:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-15  6:28 [Buildroot] [PATCH 1/1] package/qt6base: fix CVE-2024-39936 Roy Kollen Svendsen
2024-08-15  7:47 ` Thomas Petazzoni via buildroot
2024-08-15 11:19   ` Roy Kollen Svendsen
2024-08-15 12:36     ` Thomas Petazzoni via buildroot [this message]
2024-08-15  9:26 ` [Buildroot] [PATCH v2] " Roy Kollen Svendsen
2024-08-15 12:52   ` Thomas Petazzoni via buildroot

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=20240815143652.7265bd45@windsurf \
    --to=buildroot@buildroot.org \
    --cc=jesseevg@gmail.com \
    --cc=roykollensvendsen@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox