CVE-2024-46822: Linux kernel · arm64: acpi: Harden get_cpu_for_acpi_id() against missing CPU entry
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 5.5 Medium · fixed in 5.4.0-1135.145~18.04.1 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 23:57 UTC
- Patch
- Available – fixed in 5.4.0-1135.145~18.04.1, 5.4.0-1140.147~18.04.1, 5.4.0-1139.148~18.04.1 +75
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 27 Sep 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-7088-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7088-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7088-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7088-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-7100-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7100-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7088-5 (opens in a new tab)
- ubuntu.com/security/notices/USN-7119-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7123-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7144-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7154-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7155-1 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 24.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gkepkg:deb/ubuntu/linux-gke?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gkeoppkg:deb/ubuntu/linux-gkeop?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch addressing this vulnerability is available and has been released in multiple Linux kernel versions including 5.4.0-1082.87~18.04.1 and later. Users and administrators should update their Linux kernel to one of the fixed versions to mitigate this issue. No additional mitigation steps are required as the vulnerability is resolved by the official fix.
Description
CVE-2024-46822 is a vulnerability in the Linux kernel's ARM64 ACPI code where the function get_cpu_for_acpi_id() could dereference a NULL pointer if a CPU entry is missing. This issue arises from a failure in mapping the MPIDR in acpi_map_gic_cpu_interface(), potentially leading to a NULL entry in cpu_madt_gicc[]. Although no exploitation path has been confirmed, the kernel code has been hardened to prevent this NULL pointer dereference. The vulnerability affects multiple Linux kernel versions prior to specific fixed releases. A patch is available and has been incorporated into various kernel updates.
References
- ubuntu.com/security/CVE-2024-46822 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2024-46822 (opens in a new tab)
- git.kernel.org/linus/2488444274c70038eb6b686cba5f1ce48ebb9cdd (opens in a new tab)
- git.kernel.org/stable/c/f57769ff6fa7f97f1296965f20e8a2bb3ee9fd0f (opens in a new tab)
- git.kernel.org/stable/c/4c3b21204abb4fa3ab310fbbb5cf7f0e85f3a1bc (opens in a new tab)
- git.kernel.org/stable/c/945be49f4e832a9184c313fdf8917475438a795b (opens in a new tab)
- git.kernel.org/stable/c/40cae0df42e5e7f7a1c0f32deed9c4027c1ba94e (opens in a new tab)
- git.kernel.org/stable/c/62ca6d3a905b4c40cd942f3cc645a6718f8bc7e7 (opens in a new tab)
- git.kernel.org/stable/c/bc7fbb37e3d2df59336eadbd6a56be632e3c7df7 (opens in a new tab)
- git.kernel.org/stable/c/2488444274c70038eb6b686cba5f1ce48ebb9cdd (opens in a new tab)
- ubuntu.com/security/notices/USN-7088-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7088-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7088-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7088-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-7100-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7100-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7088-5 (opens in a new tab)
- ubuntu.com/security/notices/USN-7119-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7123-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7144-1 (opens in a new tab)