Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-46822arm64: acpi: Harden get_cpu_for_acpi_id() against missing CPU entry

Description

In the Linux kernel, the following vulnerability has been resolved: arm64: acpi: Harden get_cpu_for_acpi_id() against missing CPU entry In a review discussion of the changes to support vCPU hotplug where a check was added on the GICC being enabled if was online, it was noted that there is need to map back to the cpu and use that to index into a cpumask. As such, a valid ID is needed. If an MPIDR check fails in acpi_map_gic_cpu_interface() it is possible for the entry in cpu_madt_gicc[cpu] == NULL. This function would then cause a NULL pointer dereference. Whilst a path to trigger this has not been established, harden this caller against the possibility.

Timeline

  1. ID reserved

    By Linux

  2. · 16 days later

    Published

  3. · 20 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-46822, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.25% · top 83% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 0be7320a635c2e434e8b67e0e9474a85ceb421c4 – < f57769ff6fa7f97f1296965f20e8a2bb3ee9fd0f
    • affected 0be7320a635c2e434e8b67e0e9474a85ceb421c4 – < 4c3b21204abb4fa3ab310fbbb5cf7f0e85f3a1bc
    • affected 0be7320a635c2e434e8b67e0e9474a85ceb421c4 – < 945be49f4e832a9184c313fdf8917475438a795b
    • affected 0be7320a635c2e434e8b67e0e9474a85ceb421c4 – < 40cae0df42e5e7f7a1c0f32deed9c4027c1ba94e
    • affected 0be7320a635c2e434e8b67e0e9474a85ceb421c4 – < 62ca6d3a905b4c40cd942f3cc645a6718f8bc7e7
    • affected 0be7320a635c2e434e8b67e0e9474a85ceb421c4 – < bc7fbb37e3d2df59336eadbd6a56be632e3c7df7
    • affected 0be7320a635c2e434e8b67e0e9474a85ceb421c4 – < 2488444274c70038eb6b686cba5f1ce48ebb9cdd
  • Linux · Linux

    • affected 3.7
    • unaffected < 3.7
    • unaffected 5.4.284 – ≤ 5.4.*
    • unaffected 5.10.226 – ≤ 5.10.*
    • unaffected 5.15.167 – ≤ 5.15.*
    • unaffected 6.1.110 – ≤ 6.1.*
    • unaffected 6.6.51 – ≤ 6.6.*
    • unaffected 6.10.10 – ≤ 6.10.*
    • unaffected 6.11 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-46822 badge
[![CVE-2024-46822](https://cveledger.app/badge/CVE-2024-46822.svg)](https://cveledger.app/cve/CVE-2024-46822)

Record last updated .