Bug 1220774 (CVE-2021-47018) - VUL-0: CVE-2021-47018: kernel: powerpc/64: Fix the definition of the fixmap area
Summary: VUL-0: CVE-2021-47018: kernel: powerpc/64: Fix the definition of the fixmap area
Status: RESOLVED FIXED
Alias: CVE-2021-47018
Product: SUSE Security Incidents
Classification: Novell Products
Component: Incidents (show other bugs)
Version: unspecified
Hardware: Other Other
: P3 - Medium : Normal
Target Milestone: ---
Assignee: Kernel Bugs
QA Contact: Security Team bot
URL: https://smash.suse.de/issue/395466/
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-03-01 11:33 UTC by SMASH SMASH
Modified: 2024-04-05 16:04 UTC (History)
3 users (show)

See Also:
Found By: Security Response Team
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description SMASH SMASH 2024-03-01 11:33:36 UTC
In the Linux kernel, the following vulnerability has been resolved:

powerpc/64: Fix the definition of the fixmap area

At the time being, the fixmap area is defined at the top of
the address space or just below KASAN.

This definition is not valid for PPC64.

For PPC64, use the top of the I/O space.

Because of circular dependencies, it is not possible to include
asm/fixmap.h in asm/book3s/64/pgtable.h , so define a fixed size
AREA at the top of the I/O space for fixmap and ensure during
build that the size is big enough.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-47018
https://www.cve.org/CVERecord?id=CVE-2021-47018
https://bugzilla.redhat.com/show_bug.cgi?id=2266594
https://lore.kernel.org/linux-cve-announce/2024022832-CVE-2021-47018-f631@gregkh/T/#u

Patch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=9ccba66d4d2a
Comment 1 Andrea Mattiazzo 2024-03-01 11:35:09 UTC
Closing since:
-code streams below cve/linux-5.14 are not affected
-cve/linux-5.14, stable and SLE15-SP6 are already patched
Comment 8 Michal Suchanek 2024-04-05 16:04:36 UTC
This was broken in Linux 5.5 and fixed in 5.13. We don't have any kernel released in that range.