Bug 2434045 - CVE-2025-58150 xen: x86: buffer overrun with shadow paging + tracing [fedora-42]
Summary: CVE-2025-58150 xen: x86: buffer overrun with shadow paging + tracing [fedora-42]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: xen
Version: 42
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: Michael Young
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: {"flaws": ["2cb59316-4c74-495c-bf95-b...
Depends On:
Blocks: CVE-2025-58150
TreeView+ depends on / blocked
 
Reported: 2026-01-28 17:48 UTC by Guilherme de Almeida Suckevicz
Modified: 2026-02-15 01:28 UTC (History)
2 users (show)

Fixed In Version: xen-4.19.4-2.fc42
Clone Of:
Environment:
Last Closed: 2026-02-15 01:28:16 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Guilherme de Almeida Suckevicz 2026-01-28 17:48:01 UTC 
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 2026-01-29 22:04:20 UTC 
FEDORA-2026-e39149a8a0 (xen-4.19.4-2.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-e39149a8a0
Comment 2 Fedora Update System 2026-01-31 18:30:08 UTC 
FEDORA-2026-e39149a8a0 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-2026-e39149a8a0`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-e39149a8a0

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 3 Fedora Update System 2026-02-15 01:28:16 UTC 
FEDORA-2026-e39149a8a0 (xen-4.19.4-2.fc42) has been pushed to the Fedora 42 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.