CVE-2025-23141

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Score 5.5 from GitHub Security Advisory (severity: MODERATE) published 2025-05-01. NVD baseline CVSS 5.5; sources differ by 0.0.

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

Also known asEUVD-2025-13106 (ENISA EUVD) · GHSA-crp4-4q2h-fprq (GitHub Security Advisories)Source: ENISA EUVD

5.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.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

KVM: x86: Acquire SRCU in KVM_GET_MP_STATE to protect guest memory accesses

Acquire a lock on kvm->srcu when userspace is getting MP state to handle a rather extreme edge case where "accepting" APIC events, i.e. processing pending INIT or SIPI, can trigger accesses to guest memory. If the vCPU is in L2 with INIT *and* a TRIPLE_FAULT request pending, then getting MP state will trigger a nested VM-Exit by way of ->check_nested_events(), and emuating the nested VM-Exit can access guest memory.

The splat was originally hit by syzkaller on a Google-internal kernel, and reproduced on an upstream kernel by hacking the triple_fault_event_test selftest to stuff a pending INIT, store an MSR on VM-Exit (to generate a memory access on VMX), and do vcpu_mp_state_get() to trigger the scenario.

============================= WARNING: suspicious RCU usage 6.14.0-rc3-b112d356288b-vmx/pi_lockdep_false_pos-lock #3 Not tainted ----------------------------- include/linux/kvm_host.h:1058 suspicious rcu_dereference_check() usage!

other info that might help us debug this:

rcu_scheduler_active = 2, debug_locks = 1 1 lock held by triple_fault_ev/1256: #0: ffff88810df5a330 (&vcpu->mutex){+.+.}-{4:4}, at: kvm_vcpu_ioctl+0x8b/0x9a0 [kvm]

stack backtrace: CPU: 11 UID: 1000 PID: 1256 Comm: triple_fault_ev Not tainted 6.14.0-rc3-b112d356288b-vmx #3 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015 Call Trace: dump_stack_lvl+0x7f/0x90 lockdep_rcu_suspicious+0x144/0x190 kvm_vcpu_gfn_to_memslot+0x156/0x180 [kvm] kvm_vcpu_read_guest+0x3e/0x90 [kvm] read_and_check_msr_entry+0x2e/0x180 [kvm_intel] __nested_vmx_vmexit+0x550/0xde0 [kvm_intel] kvm_check_nested_events+0x1b/0x30 [kvm] kvm_apic_accept_events+0x33/0x100 [kvm] kvm_arch_vcpu_ioctl_get_mpstate+0x30/0x1d0 [kvm] kvm_vcpu_ioctl+0x33e/0x9a0 [kvm] __x64_sys_ioctl+0x8b/0xb0 do_syscall_64+0x6c/0x170 entry_SYSCALL_64_after_hwframe+0x4b/0x53

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/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)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 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.2%
EPSS %ILE
11th
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 (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-11). 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

May 1, 2025

Last Modified

October 15, 2026

Advisory Details (7)

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

KVM: x86: Acquire SRCU in KVM_GET_MP_STATE to protect guest memory accesses - kernel/git/stable/linux.git - Linux kernel stable tree

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

KVM: x86: Acquire SRCU in KVM_GET_MP_STATE to protect guest memory accesses - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/592e040572f216d916f465047c8ce4a308fcca44
Web page

KVM: x86: Acquire SRCU in KVM_GET_MP_STATE to protect guest memory accesses - kernel/git/stable/linux.git - Linux kernel stable tree

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

KVM: x86: Acquire SRCU in KVM_GET_MP_STATE to protect guest memory accesses - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7bc5c360375d28ba5ef6298b0d53e735c81d66a1
Web page

KVM: x86: Acquire SRCU in KVM_GET_MP_STATE to protect guest memory accesses - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8a3df0aa1087a89f5ce55f4aba816bfcb1ecf1be
Web page

KVM: x86: Acquire SRCU in KVM_GET_MP_STATE to protect guest memory accesses - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0357c8406dfa09430dd9858ebe813feb65524b6e
Web page

KVM: x86: Acquire SRCU in KVM_GET_MP_STATE to protect guest memory accesses - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/56d997b257075951a46663970cd350cd5e34c041

Vendor Advisories for CVE-2025-23141(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-virtual-hwe-24.04-edge (6.14.0-22.22) @ plucky2026-10-15ubuntu
ubuntulinux-tools-azure (6.14.0-1007.7) @ plucky2026-10-15ubuntu
ubuntulinux-tools-oracle-64k (6.14.0-1007.7) @ plucky2026-10-15ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1047.50+fips1) @ noble2026-10-15ubuntu
ubuntulinux-virtual-6.8 (6.8.0-100.100) @ noble2026-10-15ubuntu
ubuntulinux-tools-realtime-hwe-22.04 (6.8.1-1041.42~22.04.1) @ jammy2026-10-15ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1047.50~22.04.2) @ jammy2026-10-15ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1043.44) @ noble2026-10-15ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1041.42) @ noble2026-10-15ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-10-15ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-100.100+fips1) @ noble2026-10-15ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1104.108) @ jammy2026-10-15ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1075 (5.15.0-1075.79) @ jammy2026-10-15ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-10-15ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1107.106) @ jammy2026-10-15ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1106.104) @ jammy2026-10-15ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1112.122~20.04.1) @ focal2026-10-15ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-100.100~22.04.1) @ jammy2026-10-15ubuntu
ubuntulinux-tools-gke-64k-6.8 (6.8.0-1043.48) @ noble2026-10-15ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-100.100.1) @ noble2026-10-15ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1046.49.1) @ noble2026-10-15ubuntu
ubuntulinux-tools-ibm-lts-24.04 (6.8.0-1044.44) @ noble2026-10-15ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1023.24) @ noble2026-10-15ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1046.52) @ noble2026-10-15ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1046.52+fips1) @ noble2026-10-15ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1051.57~22.04.1) @ jammy2026-10-15ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-10-15ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1107.107) @ jammy2026-10-15ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1106.110~20.04.1) @ focal2026-10-15ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1117.126) @ jammy2026-10-15ubuntu
linuxKernel @ 5.15.209 (fixes >=5.11.0)—osv

These rows come from Ubuntu and OSV. Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux-6.16.1.106-3~deb11u1 ... 6.1.129-1~deb11u1 (7 versions)
  • every version up to 6.1.137-1~deb11u1: fixed in 6.1.137-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (37 versions)
  • every version up to 6.1.135-1: fixed in 6.1.135-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.25-1: fixed in 6.12.25-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.25-1: fixed in 6.12.25-1
—

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 5× in last 7d / 31× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 227 rows on record for this CVE, as 97 entries (3 repeats merged).

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 127 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2025-23141?
CVE-2025-23141 is a medium-severity vulnerability; its CVE record was published on May 1, 2025. In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Acquire SRCU in KVM_GET_MP_STATE to protect guest memory accesses Acquire a lock on kvm->srcu when userspace is getting MP state to handle a rather extreme edge case where "accepting" APIC events, i.e. processing pending…
When was the CVE record for CVE-2025-23141 published?
The CVE record for CVE-2025-23141 was published on May 1, 2025. 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 15, 2026; the record at its source may have been updated since.
Is CVE-2025-23141 actively exploited?
CVE-2025-23141 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (11th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-23141?
CVE-2025-23141 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-23141?
A fix for CVE-2025-23141 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-23141 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-23141

Explore →

Is Your Infrastructure Affected by CVE-2025-23141?

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