CVE-2024-26768

MEDIUMNVD 6.56.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 6.5 from GitHub Security Advisory published 2024-04-03. NVD baseline CVSS 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2024-24030 (ENISA EUVD) · GHSA-hg7x-x4qq-cq6w (GitHub Security Advisories)Source: ENISA EUVD

6.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 6.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

LoongArch: Change acpi_core_pic[NR_CPUS] to acpi_core_pic[MAX_CORE_PIC]

With default config, the value of NR_CPUS is 64. When HW platform has more then 64 cpus, system will crash on these platforms. MAX_CORE_PIC is the maximum cpu number in MADT table (max physical number) which can exceed the supported maximum cpu number (NR_CPUS, max logical number), but kernel should not crash. Kernel should boot cpus with NR_CPUS, let the remainder cpus stay in BIOS.

The potential crash reason is that the array acpi_core_pic[NR_CPUS] can be overflowed when parsing MADT table, and it is obvious that CORE_PIC should be corresponding to physical core rather than logical core, so it is better to define the array as acpi_core_pic[MAX_CORE_PIC].

With the patch, system can boot up 64 vcpus with qemu parameter -smp 128, otherwise system will crash with the following message.

[ 0.000000] CPU 0 Unable to handle kernel paging request at virtual address 0000420000004259, era == 90000000037a5f0c, ra == 90000000037a46ec [ 0.000000] Oops[#1]: [ 0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 6.8.0-rc2+ #192 [ 0.000000] Hardware name: QEMU QEMU Virtual Machine, BIOS unknown 2/2/2022 [ 0.000000] pc 90000000037a5f0c ra 90000000037a46ec tp 9000000003c90000 sp 9000000003c93d60 [ 0.000000] a0 0000000000000019 a1 9000000003d93bc0 a2 0000000000000000 a3 9000000003c93bd8 [ 0.000000] a4 9000000003c93a74 a5 9000000083c93a67 a6 9000000003c938f0 a7 0000000000000005 [ 0.000000] t0 0000420000004201 t1 0000000000000000 t2 0000000000000001 t3 0000000000000001 [ 0.000000] t4 0000000000000003 t5 0000000000000000 t6 0000000000000030 t7 0000000000000063 [ 0.000000] t8 0000000000000014 u0 ffffffffffffffff s9 0000000000000000 s0 9000000003caee98 [ 0.000000] s1 90000000041b0480 s2 9000000003c93da0 s3 9000000003c93d98 s4 9000000003c93d90 [ 0.000000] s5 9000000003caa000 s6 000000000a7fd000 s7 000000000f556b60 s8 000000000e0a4330 [ 0.000000] ra: 90000000037a46ec platform_init+0x214/0x250 [ 0.000000] ERA: 90000000037a5f0c efi_runtime_init+0x30/0x94 [ 0.000000] CRMD: 000000b0 (PLV0 -IE -DA +PG DACF=CC DACM=CC -WE) [ 0.000000] PRMD: 00000000 (PPLV0 -PIE -PWE) [ 0.000000] EUEN: 00000000 (-FPE -SXE -ASXE -BTE) [ 0.000000] ECFG: 00070800 (LIE=11 VS=7) [ 0.000000] ESTAT: 00010000 [PIL] (IS= ECode=1 EsubCode=0) [ 0.000000] BADV: 0000420000004259 [ 0.000000] PRID: 0014c010 (Loongson-64bit, Loongson-3A5000) [ 0.000000] Modules linked in: [ 0.000000] Process swapper (pid: 0, threadinfo=(____ptrval____), task=(____ptrval____)) [ 0.000000] Stack : 9000000003c93a14 9000000003800898 90000000041844f8 90000000037a46ec [ 0.000000] 000000000a7fd000 0000000008290000 0000000000000000 0000000000000000 [ 0.000000] 0000000000000000 0000000000000000 00000000019d8000 000000000f556b60 [ 0.000000] 000000000a7fd000 000000000f556b08 9000000003ca7700 9000000003800000 [ 0.000000] 9000000003c93e50 9000000003800898 9000000003800108 90000000037a484c [ 0.000000] 000000000e0a4330 000000000f556b60 000000000a7fd000 000000000f556b08 [ 0.000000] 9000000003ca7700 9000000004184000 0000000000200000 000000000e02b018 [ 0.000000] 000000000a7fd000 90000000037a0790 9000000003800108 0000000000000000 [ 0.000000] 0000000000000000 000000000e0a4330 000000000f556b60 000000000a7fd000 [ 0.000000] 000000000f556b08 000000000eaae298 000000000eaa5040 0000000000200000 [ 0.000000] ... [ 0.000000] Call Trace: [ 0.000000] [<90000000037a5f0c>] efi_runtime_init+0x30/0x94 [ 0.000000] [<90000000037a46ec>] platform_init+0x214/0x250 [ 0.000000] [<90000000037a484c>] setup_arch+0x124/0x45c [ 0.000000] [<90000000037a0790>] start_kernel+0x90/0x670 [ 0.000000] [<900000000378b0d8>] kernel_entry+0xd8/0xdc

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
29
EG Risk 29/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.6%
EPSS %ILE
48th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 3, 2024

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Aug 5, 2026
Patch available.
Web page

LoongArch: Change acpi_core_pic[NR_CPUS] to acpi_core_pic[MAX_CORE_PIC] - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4551b30525cf3d2f026b92401ffe241eb04dfebe
Web page

LoongArch: Change acpi_core_pic[NR_CPUS] to acpi_core_pic[MAX_CORE_PIC] - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0f6810e39898af2d2cabd9313e4dbc945fb5dfdd
Web page

LoongArch: Change acpi_core_pic[NR_CPUS] to acpi_core_pic[MAX_CORE_PIC] - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/88e189bd16e5889e44a41b3309558ebab78b9280

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 6.6.19 (fixes >=5.19.0)—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (353 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.7.7-1: fixed in 6.7.7-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.7.7-1: fixed in 6.7.7-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 38× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 97 of 209 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 3 repeat rows among the latest 100 are merged into the row they repeat. The 112 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:40 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  2. 2026-11-01 16:31 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  3. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  4. 2026-10-30 16:31 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  5. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  6. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  7. 2026-10-27 16:29 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  8. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  9. 2026-10-25 17:15 UTCEG score recompute
  10. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  11. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  12. 2026-10-24 08:24 UTCEG score recompute
  13. 2026-10-24 08:24 UTCGHSA enrichmentGHSA-hg7x-x4qq-cq6w · GitHub CVSS 6.5
  14. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  15. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  16. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  17. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  18. 2026-10-19 20:25 UTCOSV refresh
  19. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  20. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  21. 2026-10-18 07:22 UTCEG score recompute
  22. 2026-10-17 16:30 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  23. 2026-10-16 16:36 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  24. 2026-10-15 16:29 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  25. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.6% · 47th percentile
Show 72 more
  1. 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  2. 2026-10-12 17:59 UTCEG score recompute
  3. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  4. 2026-10-11 21:23 UTCEG score recompute
  5. 2026-10-11 16:17 UTCEG score recompute
  6. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  7. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  8. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  9. 2026-10-08 17:07 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  10. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  11. 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  12. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  13. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  14. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  15. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  16. 2026-09-30 16:59 UTCEG score recompute
  17. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  18. 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  19. 2026-09-28 13:49 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  20. 2026-09-27 01:12 UTCOSV refresh
  21. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  22. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  23. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  24. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  25. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  26. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  27. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  28. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  29. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  30. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  31. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  32. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  33. 2026-09-07 10:48 UTCOSV refresh
  34. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  35. 2026-09-05 15:26 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  36. 2026-09-04 13:58 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  37. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  38. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  39. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  40. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  41. 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  42. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  43. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  44. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  45. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  46. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  47. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  48. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  49. 2026-08-20 19:31 UTCOSV refresh
  50. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  51. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  52. 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  53. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  54. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  55. 2026-08-15 01:28 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  56. 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  57. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  58. 2026-08-11 13:40 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  59. 2026-08-09 13:45 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  60. 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  61. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  62. 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  63. 2026-08-05 12:23 UTCEG score recompute
  64. 2026-08-05 12:23 UTCGHSA enrichmentGHSA-hg7x-x4qq-cq6w · GitHub CVSS 6.5
  65. 2026-08-04 15:08 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  66. 2026-08-04 12:19 UTCEG score recompute
  67. 2026-08-04 12:19 UTCGHSA enrichmentGHSA-hg7x-x4qq-cq6w · GitHub CVSS 6.5
  68. 2026-08-04 10:36 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  69. 2026-08-03 10:34 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  70. 2026-08-02 02:25 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  71. 2026-08-01 08:06 UTCOSV refresh
  72. 2026-07-30 16:26 UTCEPSS rescoreEPSS 0.2% · 14th percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2024-26768?
CVE-2024-26768 is a medium-severity vulnerability; its CVE record was published on April 3, 2024. In the Linux kernel, the following vulnerability has been resolved: LoongArch: Change acpi_core_pic[NR_CPUS] to acpi_core_pic[MAX_CORE_PIC] With default config, the value of NR_CPUS is 64. When HW platform has more then 64 cpus, system will crash on these platforms. MAX_CORE_PIC is the maximum cpu…
When was the CVE record for CVE-2024-26768 published?
The CVE record for CVE-2024-26768 was published on April 3, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 5, 2026; the record at its source may have been updated since.
Is CVE-2024-26768 actively exploited?
CVE-2024-26768 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (48th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-26768?
CVE-2024-26768 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2024-26768?
A fix for CVE-2024-26768 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-26768

Explore →

Is Your Infrastructure Affected by CVE-2024-26768?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs