public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Than Ngo <than@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/chromium] epel9-next: - Update to 130.0.6723.116
Date: Fri, 07 Aug 2026 16:07:06 GMT [thread overview]
Message-ID: <178611882656.1.16954108050409919398.rpms-chromium-da89ab8ed27d@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/chromium
Branch : epel9-next
Commit : da89ab8ed27d5fb76ab85b6b4d11aa3dddf45c86
Author : Than Ngo <than@redhat.com>
Date : 2024-11-10T14:18:02+01:00
Stats : +8/-3 in 3 file(s)
URL : https://src.fedoraproject.org/rpms/chromium/c/da89ab8ed27d5fb76ab85b6b4d11aa3dddf45c86?branch=epel9-next
Log:
- Update to 130.0.6723.116
* High CVE-2024-10826: Use after free in Family Experience
* High CVE-2024-10827: Use after free in Serial
---
diff --git a/chromium.conf b/chromium.conf
index 62cecce..d89ba3c 100644
--- a/chromium.conf
+++ b/chromium.conf
@@ -34,7 +34,7 @@ case "$GRAPHIC_DRIVER" in
# The NVIDIA VaAPI drivers are known to not support Chromium
# see https://crbug.com/1492880. This feature switch is
# provided for developers to test VaAPI drivers on NVIDIA GPUs
- CHROMIUM_FLAGS+=" --use-gl=angle --use-angle=gl"
+ CHROMIUM_FLAGS+=" --use-gl=angle --use-angle=gl --disable-gpu-compositing"
FEATURES+="VaapiVideoDecodeLinuxGL,VaapiVideoEncoder,VaapiOnNvidiaGPUs"
;;
intel)
diff --git a/chromium.spec b/chromium.spec
index 1fabc04..16e1b02 100644
--- a/chromium.spec
+++ b/chromium.spec
@@ -273,7 +273,7 @@
%endif
Name: chromium%{chromium_channel}
-Version: 130.0.6723.91
+Version: 130.0.6723.116
Release: 1%{?dist}
Summary: A WebKit (Blink) powered web browser that Google doesn't want you to use
Url: http://www.chromium.org/Home
@@ -1917,6 +1917,11 @@ getent group chrome-remote-desktop >/dev/null || groupadd -r chrome-remote-deskt
%endif
%changelog
+* Sun Nov 10 2024 Than Ngo <than@redhat.com> - 130.0.6723.116-1
+- Update to 130.0.6723.116
+ * High CVE-2024-10826: Use after free in Family Experience
+ * High CVE-2024-10827: Use after free in Serial
+
* Wed Oct 30 2024 Than Ngo <than@redhat.com> - 130.0.6723.91-1
- Update to 130.0.6723.91
* Critical CVE-2024-10487: Out of bounds write in Dawn
diff --git a/sources b/sources
index b1d086e..2bcb712 100644
--- a/sources
+++ b/sources
@@ -2,4 +2,4 @@ SHA512 (node-v20.6.1-linux-arm64.tar.xz) = adfcaf2c22614797fd69fb46d94c1cbf64dea
SHA512 (node-v20.6.1-linux-x64.tar.xz) = 7e15c05041a9a50f0046266aadb2e092a5aefbec19be1c7c809471add520cb57c7df3c47d88b1888b29bf2979dca3c92adddfd965370fa2a9da4ea02186464fd
SHA512 (linux-arm64-0.19.2.tgz) = 8a0d8fec6786fffcd6954d00820037a55d61e60762c74300df0801f8db27057562c221a063bedfb8df56af9ba80abb366336987e881782c5996e6f871abd3dc6
SHA512 (linux-x64-0.19.2.tgz) = a31cc74c4bfa54f9b75d735a1cfc944d3b5efb7c06bfba9542da9a642ae0b2d235ea00ae84d3ad0572c406405110fe7b61377af0fd15803806ef78d20fc6f05d
-SHA512 (chromium-130.0.6723.91-clean.tar.xz) = fd09b713f83a4da85b20d8fbd55732c6b6837b194dab6bbc151c9ca60d96811e2fbe24f2c235e3e644418b93b8f8153fdff2c4d46fc44af04c9815c9c76715b0
+SHA512 (chromium-130.0.6723.116-clean.tar.xz) = ea9a84da6dbf90364e52cef81016683a2a6ac06de75df26c0522090dc0ccb8725b40364cf3d8330ca5d5f6d99ded99f2bf0858ac8d581b974f007c5cc887e62a
reply other threads:[~2026-08-07 16:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=178611882656.1.16954108050409919398.rpms-chromium-da89ab8ed27d@fedoraproject.org \
--to=than@redhat.com \
--cc=git-commits@fedoraproject.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
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