CVE-2024-47722

kernel: xen: use correct end address of kernel for conflict checking

Published Oct 21, 2024 CVSS 3.1 · 0.0 Low EPSS n/a KEV · Not listed
Description
This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.

Analysis

This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.

Remediation

No remediation available yet

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
References
Metrics cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Moderate

cvssV3_1

{'score': 0.0, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:N'}

threat_severity

None

Type Values Removed Values Added
Title kernel: xen: use correct end address of kernel for conflict checking
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Moderate

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: xen: use correct end address of kernel for conflict checking When running as a Xen PV dom0 the kernel is loaded by the hypervisor using a different memory map than that of the host. In order to minimize the required changes in the kernel, the kernel adapts its memory map to that of the host. In order to do that it is checking for conflicts of its load address with the host memory map. Unfortunately the tested memory range does not include the .brk area, which might result in crashes or memory corruption when this area does conflict with the memory map of the host. Fix the test by using the _end label instead of __bss_stop. This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
Title xen: use correct end address of kernel for conflict checking
References
Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: xen: use correct end address of kernel for conflict checking When running as a Xen PV dom0 the kernel is loaded by the hypervisor using a different memory map than that of the host. In order to minimize the required changes in the kernel, the kernel adapts its memory map to that of the host. In order to do that it is checking for conflicts of its load address with the host memory map. Unfortunately the tested memory range does not include the .brk area, which might result in crashes or memory corruption when this area does conflict with the memory map of the host. Fix the test by using the _end label instead of __bss_stop.
Title xen: use correct end address of kernel for conflict checking
References

Subscriptions

No data.

Weaknesses

No weakness.

Sources

Status
REJECTED
Assigner
Linux
Published
Updated
Oct 21, 2024, 12:58 PM
Reserved
Sep 30, 2024, 4:00 PM
Status
Rejected
Published
Oct 21, 2024, 1:15 PM
Modified
Oct 16, 2026, 1:10 PM
Severity
Public date
Oct 21, 2024, 12:00 AM