CVE-2025-71078

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-01-13. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2026-2265 (ENISA EUVD) · GHSA-mh76-3pc6-49g3 (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

powerpc/64s/slb: Fix SLB multihit issue during SLB preload

On systems using the hash MMU, there is a software SLB preload cache that mirrors the entries loaded into the hardware SLB buffer. This preload cache is subject to periodic eviction — typically after every 256 context switches — to remove old entry.

To optimize performance, the kernel skips switch_mmu_context() in switch_mm_irqs_off() when the prev and next mm_struct are the same. However, on hash MMU systems, this can lead to inconsistencies between the hardware SLB and the software preload cache.

If an SLB entry for a process is evicted from the software cache on one CPU, and the same process later runs on another CPU without executing switch_mmu_context(), the hardware SLB may retain stale entries. If the kernel then attempts to reload that entry, it can trigger an SLB multi-hit error.

The following timeline shows how stale SLB entries are created and can cause a multi-hit error when a process moves between CPUs without a MMU context switch.

CPU 0 CPU 1 ----- ----- Process P exec swapper/1 load_elf_binary begin_new_exc activate_mm switch_mm_irqs_off switch_mmu_context switch_slb /* * This invalidates all * the entries in the HW * and setup the new HW * SLB entries as per the * preload cache. */ context_switch sched_migrate_task migrates process P to cpu-1

Process swapper/0 context switch (to process P) (uses mm_struct of Process P) switch_mm_irqs_off() switch_slb load_slb++ /* * load_slb becomes 0 here * and we evict an entry from * the preload cache with * preload_age(). We still * keep HW SLB and preload * cache in sync, that is * because all HW SLB entries * anyways gets evicted in * switch_slb during SLBIA. * We then only add those * entries back in HW SLB, * which are currently * present in preload_cache * (after eviction). */ load_elf_binary continues... setup_new_exec() slb_setup_new_exec()

sched_switch event sched_migrate_task migrates process P to cpu-0

context_switch from swapper/0 to Process P switch_mm_irqs_off() /* * Since both prev and next mm struct are same we don't call * switch_mmu_context(). This will cause the HW SLB and SW preload * cache to go out of sync in preload_new_slb_context. Because there * was an SLB entry which was evicted from both HW and preload cache * on cpu-1. Now later in preload_new_slb_context(), when we will try * to add the same preload entry again, we will add this to the SW * preload cache and then will add it to the HW SLB. Since on cpu-0 * this entry was never invalidated, hence adding this entry to the HW * SLB will cause a SLB multi-hit error. */ load_elf_binary cont ---truncated---

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/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)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.1%
EPSS %ILE
1st
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 (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). 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 low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 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 low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 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 total (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

January 13, 2026

Last Modified

October 19, 2026

Advisory Details (7)

Auto-updated Jul 30, 2026
Patch available.
Web page

powerpc/64s/slb: Fix SLB multihit issue during SLB preload - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c9f865022a1823d814032a09906e91e4701a35fc
Web page

powerpc/64s/slb: Fix SLB multihit issue during SLB preload - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b13a3dbfa196af68eae2031f209743735ad416bf
Web page

powerpc/64s/slb: Fix SLB multihit issue during SLB preload - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/895123c309a34d2cfccf7812b41e17261a3a6f37
Web page

powerpc/64s/slb: Fix SLB multihit issue during SLB preload - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4ae1e46d8a290319f33f71a2710a1382ba5431e8
Web page

powerpc/64s/slb: Fix SLB multihit issue during SLB preload - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2e9a95d60f1df7b57618fd5ef057aef331575bd2
Web page

powerpc/64s/slb: Fix SLB multihit issue during SLB preload - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/01324c0328181b94cf390bda22ff91c75126ea57
Web page

powerpc/64s/slb: Fix SLB multihit issue during SLB preload - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/00312419f0863964625d6dcda8183f96849412c6

Vendor Advisories for CVE-2025-71078(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(31)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1109.107) @ jammy2026-10-27ubuntu
ubuntulinux-tools-gcp-fips-5.15 (5.15.0.1103.93) @ jammy2026-10-27ubuntu
ubuntulinux-tools-realtime-5.15 (5.15.0.1102.106) @ jammy2026-10-27ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1094.98) @ jammy2026-10-27ubuntu
ubuntulinux-tools-nvidia-tegra-igx-rt-5.15 (5.15.0.1044.46) @ jammy2026-10-27ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1097.95) @ jammy2026-10-27ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1109.94) @ jammy2026-10-27ubuntu
ubuntulinux-tools-gke-5.15 (5.15.0.1099.98) @ jammy2026-10-27ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.17.0-22.22) @ questing2026-10-27ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1067 (5.15.0-1067.71) @ jammy2026-10-27ubuntu
ubuntulinux-tools-oracle-64k-6.17 (6.17.0-1011.11) @ questing2026-10-27ubuntu
ubuntulinux-virtual-6.8 (6.8.0-110.110) @ noble2026-10-27ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.17.0-1010.11~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-gcp-64k-6.17 (6.17.0-1012.12) @ questing2026-10-27ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1047.48) @ noble2026-10-27ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1054.57+fips1) @ noble2026-10-27ubuntu
ubuntulinux-tools-nvidia-64k-6.8 (6.8.0-1051.54) @ noble2026-10-27ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-110.110~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1049.50) @ noble2026-10-27ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2042.43) @ noble2026-10-27ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1051.54.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1054.57~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1110.119~20.04.1) @ focal2026-10-27ubuntu
ubuntulinux-tools-azure-6.17 (6.17.0-1013.13) @ questing2026-10-27ubuntu
ubuntulinux-tools-raspi-6.17 (6.17.0-1014.14) @ questing2026-10-27ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1054.60) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1054.60+fips1) @ noble2026-10-27ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1029.30) @ noble2026-10-27ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1022.22) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1059.65~22.04.1) @ jammy2026-10-27ubuntu
linuxKernel @ 5.10.248 (fixes >=4.20.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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
  • every version on: no fix on record
—
linux-6.16.1.106-3~deb11u1 ... 6.1.159-1~deb11u1 (14 versions)
  • every version up to 6.1.162-1~deb11u1: fixed in 6.1.162-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (46 versions)
  • every version up to 6.1.162-1: fixed in 6.1.162-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.69-1~bpo12+1 (10 versions)
  • every version up to 6.12.69-1: fixed in 6.12.69-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (95 versions)
  • every version up to 6.18.5-1: fixed in 6.18.5-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(24)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 8× in last 7d / 43× 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 99 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 110 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2025-71078?
CVE-2025-71078 is a high-severity vulnerability; its CVE record was published on January 13, 2026. In the Linux kernel, the following vulnerability has been resolved: powerpc/64s/slb: Fix SLB multihit issue during SLB preload On systems using the hash MMU, there is a software SLB preload cache that mirrors the entries loaded into the hardware SLB buffer. This preload cache is subject to periodic…
When was the CVE record for CVE-2025-71078 published?
The CVE record for CVE-2025-71078 was published on January 13, 2026. 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 October 19, 2026; the record at its source may have been updated since.
Is CVE-2025-71078 actively exploited?
CVE-2025-71078 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-71078?
CVE-2025-71078 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2025-71078?
A fix for CVE-2025-71078 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-71078 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-71078

Explore →

Is Your Infrastructure Affected by CVE-2025-71078?

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