CVE-2024-56617: cacheinfo: Allocate memory during CPU hotplug if not done from the primary CPU
In the Linux kernel, the following vulnerability has been resolved:
cacheinfo: Allocate memory during CPU hotplug if not done from the primary CPU
Commit
5944ce092b97 ("archtopology: Build cacheinfo from primary CPU")
adds functionality that architectures can use to optionally allocate and build cacheinfo early during boot. Commit
6539cffa9495 ("cacheinfo: Add arch specific early level initializer")
lets secondary CPUs correct (and reallocate memory) cacheinfo data if needed.
If the early build functionality is not used and cacheinfo does not need correction, memory for cacheinfo is never allocated. x86 does not use the early build functionality. Consequently, during the cacheinfo CPU hotplug callback, lastlevelcacheisvalid() attempts to dereference a NULL pointer:
BUG: kernel NULL pointer dereference, address: 0000000000000100 #PF: supervisor read access in kernel mode #PF: errorcode(0x0000) - not present page PGD 0 P4D 0 Oops: 0000 [#1] PREEPMT SMP NOPTI CPU: 0 PID 19 Comm: cpuhp/0 Not tainted 6.4.0-rc2 #1 RIP: 0010: lastlevelcacheisvalid+0x95/0xe0a
Allocate memory for cacheinfo during the cacheinfo CPU hotplug callback if not done earlier.
Moreover, before determining the validity of the last-level cache info, ensure that it has been allocated. Simply checking for non-zero cacheleaves() is not sufficient, as some architectures (e.g., Intel processors) have non-zero cacheleaves() before allocation.
Dereferencing NULL cacheinfo can occur in updatepercpudataslicesize(). This function iterates over all online CPUs. However, a CPU may have come online recently, but its cacheinfo may not have been allocated yet.
While here, remove an unnecessary indentation in allocatecacheinfo().
[ bp: Massage. ]
Other sources
This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.
— Launchpad
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-56617?
CVE-2024-56617 has been classified as a moderate severity vulnerability in the Linux kernel.
How do I fix CVE-2024-56617?
To remediate CVE-2024-56617, update the Linux kernel to a version that is beyond 6.6.66 or 6.12.5 depending on your current version.
Which versions of the Linux kernel are affected by CVE-2024-56617?
CVE-2024-56617 affects Linux kernel versions between 6.4 and 6.6.66 and between 6.7 and 6.12.5, as well as 6.13-rc1.
Is CVE-2024-56617 a hardware or software vulnerability?
CVE-2024-56617 is a software vulnerability found in the Linux kernel.
When was CVE-2024-56617 reported?
CVE-2024-56617 was resolved and reported in updates related to architecture enhancements in the Linux kernel.