Linux · Ubuntu · Package update · August 22, 2023

binutils-aarch64-linux-gnu 2.38-4ubuntu2.5: binutils-aarch64-linux-gnu 2.38-4ubuntu2.5 for Ubuntu 22.04.1 LTS (jammy)

binutils-aarch64-linux-gnu 2.38-4ubuntu2.5, released August 22, 2023, fixes 6 CVEs in binutils-aarch64-linux-gnu. None of them is reported as exploited. Patch Radar priority: High.

High
CVEs closed
6
None rated Critical
Exploited
0
None reported
Highest CVSS
7.8
Base score, 0 to 10
Highest EPSS
0.0049
42nd percentile

Priority of the 6 CVEs

Patch now 0 Urgent 0 High 2 Routine 4

Fixed package versions

ProductReleaseFixed in
binutils-aarch64-linux-gnuUbuntu 22.04.1 LTS (jammy)2.38-4ubuntu2.5

CVEs this fix closes

PriorityCVETitleCVSSEPSSExploitation
High CVE-2022-44840 binutils-ia64-linux-gnu: Heap buffer overflow vulnerability in binutils readelf before 2.40 via function find_section_in_set in file readelf.c.7.8 0.0049 None reported
High CVE-2022-45703 binutils-riscv64-linux-gnu: Heap buffer overflow vulnerability in binutils readelf before 2.40 via function display_debug_section in file readelf.c.7.8 0.0049 None reported
Routine CVE-2022-47007 binutils: An issue was discovered function stab_demangle_v3_arg in stabs.c in Binutils 2.34 thru 2.38, allows attackers to caus...5.5 0.0039 None reported
Routine CVE-2022-47010 binutils: An issue was discovered function pr_function_type in prdbg.c in Binutils 2.34 thru 2.38, allows attackers to cause a...5.5 0.0039 None reported
Routine CVE-2022-47011 binutils-m68k-linux-gnu: An issue was discovered function parse_stab_struct_fields in stabs.c in Binutils 2.34 thru 2.38, allows attackers to...5.5 0.0039 None reported
Routine CVE-2022-47008 binutils-powerpc-linux-gnuspe: An issue was discovered function make_tempdir, and make_tempname in bucomm.c in Binutils 2.34 thru 2.38, allows attac...5.5 0.0039 None reported
Showing 1 to 6 of 6 1

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.