Bug 2266937

Summary: CVE-2024-1939 chromium: type confusion [fedora-all]
Product: [Fedora] Fedora Reporter: ybuenos
Component: chromiumAssignee: Tom "spot" Callaway <spotrh>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: high    
Version: 39CC: spotrh, than, tpopela, yaneti
Target Milestone: ---Keywords: Security, SecurityTracking
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: chromium-122.0.6261.94-1.fc38 chromium-122.0.6261.94-1.fc39 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-03-03 01:36:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2266935    

Description ybuenos 2024-02-29 09:00:24 UTC
More information about this security flaw is available in the following bug:

http://bugzilla.redhat.com/show_bug.cgi?id=2266935

Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

Comment 1 ybuenos 2024-02-29 09:00:27 UTC
Use the following template to for the 'fedpkg update' request to submit an
update for this issue as it contains the top-level parent bug(s) as well as
this tracking bug.  This will ensure that all associated bugs get updated
when new packages are pushed to stable.

=====

# bugfix, security, enhancement, newpackage (required)
type=security

# low, medium, high, urgent (required)
severity=high

# testing, stable
request=testing

# Bug numbers: 1234,9876
bugs=2266935,2266937

# Description of your update
notes=Security fix for [PUT CVEs HERE]

# Enable request automation based on the stable/unstable karma thresholds
autokarma=True
stable_karma=3
unstable_karma=-3

# Automatically close bugs when this marked as stable
close_bugs=True

# Suggest that users restart after update
suggest_reboot=False

======

Additionally, you may opt to use the bodhi web interface to submit updates:

https://bodhi.fedoraproject.org/updates/new

Comment 2 Fedora Update System 2024-03-01 10:33:33 UTC
FEDORA-2024-9ce64d8940 (chromium-122.0.6261.94-1.fc39) has been submitted as an update to Fedora 39.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-9ce64d8940

Comment 3 Fedora Update System 2024-03-01 10:33:36 UTC
FEDORA-2024-71395e12ce (chromium-122.0.6261.94-1.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-71395e12ce

Comment 4 Fedora Update System 2024-03-01 10:33:40 UTC
FEDORA-2024-449696cdb8 (chromium-122.0.6261.94-1.fc38) has been submitted as an update to Fedora 38.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-449696cdb8

Comment 5 Fedora Update System 2024-03-02 01:02:25 UTC
FEDORA-2024-9ce64d8940 has been pushed to the Fedora 39 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-9ce64d8940`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-9ce64d8940

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2024-03-02 01:41:20 UTC
FEDORA-2024-71395e12ce has been pushed to the Fedora 40 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-71395e12ce`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-71395e12ce

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2024-03-02 02:00:53 UTC
FEDORA-2024-449696cdb8 has been pushed to the Fedora 38 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-449696cdb8`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-449696cdb8

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2024-03-03 01:36:51 UTC
FEDORA-2024-449696cdb8 (chromium-122.0.6261.94-1.fc38) has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Fedora Update System 2024-03-05 01:58:32 UTC
FEDORA-2024-129d8ca6fc has been pushed to the Fedora 40 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-129d8ca6fc`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-129d8ca6fc

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 10 Fedora Update System 2024-03-06 01:05:25 UTC
FEDORA-2024-9ce64d8940 (chromium-122.0.6261.94-1.fc39) has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 11 Fedora Update System 2024-03-06 02:10:51 UTC
FEDORA-2024-129d8ca6fc has been pushed to the Fedora 40 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-129d8ca6fc`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-129d8ca6fc

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 12 Fedora Update System 2024-03-07 22:25:04 UTC
FEDORA-2024-129d8ca6fc (System JDK update from 17 to 21) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.