Linux · Ubuntu · Package update · September 23, 2020

libxenforeignmemory1 4.11.3+24-g14b62ab3e5-1ubuntu2.3: libxenforeignmemory1 4.11.3+24-g14b62ab3e5-1ubuntu2.3 for Ubuntu 20.04.3 LTS (focal)

libxenforeignmemory1 4.11.3+24-g14b62ab3e5-1ubuntu2.3, released September 23, 2020, fixes 20 CVEs in libxenforeignmemory1. None of them is reported as exploited. Patch Radar priority: Routine. The product is no longer supported.

RoutineUnsupported product
CVEs closed
20
None rated Critical
Exploited
0
None reported
Highest CVSS
6.5
Base score, 0 to 10
Highest EPSS
0.0054
45th percentile

Priority of the 20 CVEs

Patch now 0 Urgent 0 High 0 Routine 20

Fixed package versions

ProductReleaseFixed in
libxenforeignmemory1Ubuntu 20.04.3 LTS (focal)4.11.3+24-g14b62ab3e5-1ubuntu2.3

CVEs this fix closes

PriorityCVETitleCVSSEPSSExploitation
Routine CVE-2020-0543 kernel-uek: ELSA-2020-5756: Unbreakable Enterprise kernel security update (IMPORTANT)6.5 0.0054 None reported
Routine CVE-2020-11743 libxencall1: An issue was discovered in Xen through 4.13.x, allowing guest OS users to cause a denial of service because of a bad...n/a 0.0053 None reported
Routine CVE-2020-25596 libxenmisc4.11: An issue was discovered in Xen through 4.14.xn/a 0.0051 None reported
Routine CVE-2020-11740 libxenevtchn1: An issue was discovered in xenoprof in Xen through 4.13.x, allowing guest OS users (without active profiling) to obta...n/a 0.0043 None reported
Routine CVE-2020-25600 libxencall1: An issue was discovered in Xen through 4.14.xn/a 0.0043 None reported
Routine CVE-2020-11741 libxencall1: An issue was discovered in xenoprof in Xen through 4.13.x, allowing guest OS users (with active profiling) to obtain...n/a 0.0042 None reported
Routine CVE-2020-25601 libxengnttab1: An issue was discovered in Xen through 4.14.xn/a 0.0042 None reported
Routine CVE-2020-25603 libxencall1: An issue was discovered in Xen through 4.14.xn/a 0.0042 None reported
Routine CVE-2020-15563 libxencall1: An issue was discovered in Xen through 4.13.x, allowing x86 HVM guest OS users to cause a hypervisor crashn/a 0.0041 None reported
Routine CVE-2020-11742 libxencall1: An issue was discovered in Xen through 4.13.x, allowing guest OS users to cause a denial of service because of bad co...n/a 0.0041 None reported
Routine CVE-2020-15566 libxencall1: An issue was discovered in Xen through 4.13.x, allowing guest OS users to cause a host OS crash because of incorrect...n/a 0.0041 None reported
Routine CVE-2020-15564 libxenevtchn1: An issue was discovered in Xen through 4.13.x, allowing Arm guest OS users to cause a hypervisor crash because of a m...n/a 0.0040 None reported
Routine CVE-2020-25595 libxencall1: An issue was discovered in Xen through 4.14.xn/a 0.0037 None reported
Routine CVE-2020-15565 libxencall1: An issue was discovered in Xen through 4.13.x, allowing x86 Intel HVM guest OS users to cause a host OS denial of ser...n/a 0.0036 None reported
Routine CVE-2020-25597 libxencall1: An issue was discovered in Xen through 4.14.xn/a 0.0036 None reported
Routine CVE-2020-25602 libxencall1: An issue was discovered in Xen through 4.14.xn/a 0.0032 None reported
Routine CVE-2020-11739 libxencall1: An issue was discovered in Xen through 4.13.x, allowing guest OS users to cause a denial of service or possibly gain...n/a 0.0029 None reported
Routine CVE-2020-25599 libxencall1: An issue was discovered in Xen through 4.14.xn/a 0.0029 None reported
Routine CVE-2020-15567 libxencall1: An issue was discovered in Xen through 4.13.x, allowing Intel guest OS users to gain privileges or cause a denial of...n/a 0.0028 None reported
Routine CVE-2020-25604 libxencall1: An issue was discovered in Xen through 4.14.xn/a 0.0026 None reported
Showing 1 to 20 of 20 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.