Bug 2348977

Summary: CVE-2025-1744 radare2: Out-of-bounds Write in radare2 [epel-9]
Product: [Fedora] Fedora EPEL Reporter: Avinash Hanwate <ahanwate>
Component: radare2Assignee: Michal Ambroz <rebus>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: urgent    
Version: epel9CC: rebus
Target Milestone: ---Keywords: Security, SecurityTracking
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: {"flaws": ["ddc24003-4013-4883-b986-177247f9ae4c"]}
Fixed In Version: radare2-5.9.8-7.fc42 radare2-5.9.8-7.fc41 radare2-5.9.8-7.fc40 radare2-5.9.8-7.el10_1 radare2-5.9.8-7.el9 radare2-5.9.8-8.el8 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-03-20 00:16:30 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: 2348972    

Description Avinash Hanwate 2025-02-28 05:30:09 UTC
More information about this security flaw is available in the following bug:

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

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 Michal Ambroz 2025-03-06 19:49:19 UTC
pending release of 5.9.9

Comment 2 Fedora Update System 2025-03-11 15:12:09 UTC
FEDORA-EPEL-2025-209be3862d (radare2-5.9.8-6.el9) has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-209be3862d

Comment 3 Fedora Update System 2025-03-11 18:02:24 UTC
FEDORA-EPEL-2025-c3c21f0192 (radare2-5.9.8-7.el10_1) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-c3c21f0192

Comment 4 Fedora Update System 2025-03-11 18:02:54 UTC
FEDORA-EPEL-2025-b3b0248eac (radare2-5.9.8-7.el9) has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-b3b0248eac

Comment 5 Fedora Update System 2025-03-12 01:45:34 UTC
FEDORA-2025-1189bc2336 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-1189bc2336`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-1189bc2336

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

Comment 6 Fedora Update System 2025-03-12 02:23:49 UTC
FEDORA-EPEL-2025-c3c21f0192 has been pushed to the Fedora EPEL 10.1 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-c3c21f0192

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

Comment 7 Fedora Update System 2025-03-12 02:37:38 UTC
FEDORA-EPEL-2025-b3b0248eac has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-b3b0248eac

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

Comment 8 Fedora Update System 2025-03-12 02:41:32 UTC
FEDORA-2025-7b9adcd6ea 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-7b9adcd6ea`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-7b9adcd6ea

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

Comment 9 Fedora Update System 2025-03-12 02:51:07 UTC
FEDORA-EPEL-2025-5682727d1e has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-5682727d1e

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

Comment 10 Fedora Update System 2025-03-12 03:10:00 UTC
FEDORA-2025-f8eca89d63 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-f8eca89d63`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-f8eca89d63

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

Comment 11 Fedora Update System 2025-03-20 00:16:30 UTC
FEDORA-2025-1189bc2336 (radare2-5.9.8-7.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 12 Fedora Update System 2025-03-20 04:36:10 UTC
FEDORA-2025-7b9adcd6ea (radare2-5.9.8-7.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 13 Fedora Update System 2025-03-20 04:49:14 UTC
FEDORA-2025-f8eca89d63 (radare2-5.9.8-7.fc40) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 14 Fedora Update System 2025-03-20 04:52:35 UTC
FEDORA-EPEL-2025-c3c21f0192 (radare2-5.9.8-7.el10_1) has been pushed to the Fedora EPEL 10.1 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 15 Fedora Update System 2025-03-20 05:04:00 UTC
FEDORA-EPEL-2025-b3b0248eac (radare2-5.9.8-7.el9) has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 16 Fedora Update System 2025-03-20 05:07:14 UTC
FEDORA-EPEL-2025-5682727d1e (radare2-5.9.8-8.el8) has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.