Bug 2349366 - CVE-2025-26598 tigervnc: Out-of-bounds write in CreatePointerBarrierClient() [fedora-all]
Summary: CVE-2025-26598 tigervnc: Out-of-bounds write in CreatePointerBarrierClient() ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: tigervnc
Version: 41
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: Jan Grulich
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: {"flaws": ["2d86978b-d72f-4862-b68c-9...
Depends On:
Blocks: CVE-2025-26598
TreeView+ depends on / blocked
 
Reported: 2025-03-03 05:17 UTC by Sandipan Roy
Modified: 2025-03-19 02:05 UTC (History)
1 user (show)

Fixed In Version: tigervnc-1.15.0-2.fc40 tigervnc-1.15.0-2.fc42 tigervnc-1.15.0-2.fc41
Clone Of:
Environment:
Last Closed: 2025-03-13 01:47:46 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Sandipan Roy 2025-03-03 05:17:47 UTC
More information about this security flaw is available in the following bug:

https://bugzilla.redhat.com/show_bug.cgi?id=2345254

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 Fedora Update System 2025-03-03 06:54:03 UTC
FEDORA-2025-96f8a2da96 (tigervnc-1.15.0-2.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-96f8a2da96

Comment 2 Fedora Update System 2025-03-03 06:55:10 UTC
FEDORA-2025-a87bc329fe (tigervnc-1.15.0-2.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-a87bc329fe

Comment 3 Fedora Update System 2025-03-03 06:55:11 UTC
FEDORA-2025-ef7fb833f2 (tigervnc-1.15.0-2.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-ef7fb833f2

Comment 4 Fedora Update System 2025-03-04 01:13:04 UTC
FEDORA-2025-96f8a2da96 has been pushed to the Fedora 41 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-96f8a2da96`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-96f8a2da96

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

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

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

Comment 6 Fedora Update System 2025-03-04 02:14:08 UTC
FEDORA-2025-a87bc329fe 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-2025-a87bc329fe`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-a87bc329fe

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

Comment 7 Fedora Update System 2025-03-13 01:47:46 UTC
FEDORA-2025-a87bc329fe (tigervnc-1.15.0-2.fc40) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2025-03-15 00:37:11 UTC
FEDORA-2025-ef7fb833f2 (tigervnc-1.15.0-2.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Fedora Update System 2025-03-19 02:05:10 UTC
FEDORA-2025-96f8a2da96 (tigervnc-1.15.0-2.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.