CVE-2025-40274

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-12-07. The CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Trending — 3 sources updated this week

Also known asEUVD-2025-201581 (ENISA EUVD) · GHSA-h3qw-rx4w-h8fj (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:

KVM: guest_memfd: Remove bindings on memslot deletion when gmem is dying

When unbinding a memslot from a guest_memfd instance, remove the bindings even if the guest_memfd file is dying, i.e. even if its file refcount has gone to zero. If the memslot is freed before the file is fully released, nullifying the memslot side of the binding in kvm_gmem_release() will write to freed memory, as detected by syzbot+KASAN:

================================================================== BUG: KASAN: slab-use-after-free in kvm_gmem_release+0x176/0x440 virt/kvm/guest_memfd.c:353 Write of size 8 at addr ffff88807befa508 by task syz.0.17/6022

CPU: 0 UID: 0 PID: 6022 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025 Call Trace: dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0xca/0x240 mm/kasan/report.c:482 kasan_report+0x118/0x150 mm/kasan/report.c:595 kvm_gmem_release+0x176/0x440 virt/kvm/guest_memfd.c:353 __fput+0x44c/0xa70 fs/file_table.c:468 task_work_run+0x1d4/0x260 kernel/task_work.c:227 resume_user_mode_work include/linux/resume_user_mode.h:50 [inline] exit_to_user_mode_loop+0xe9/0x130 kernel/entry/common.c:43 exit_to_user_mode_prepare include/linux/irq-entry-common.h:225 [inline] syscall_exit_to_user_mode_work include/linux/entry-common.h:175 [inline] syscall_exit_to_user_mode include/linux/entry-common.h:210 [inline] do_syscall_64+0x2bd/0xfa0 arch/x86/entry/syscall_64.c:100 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fbeeff8efc9

Allocated by task 6023: kasan_save_stack mm/kasan/common.c:56 [inline] kasan_save_track+0x3e/0x80 mm/kasan/common.c:77 poison_kmalloc_redzone mm/kasan/common.c:397 [inline] __kasan_kmalloc+0x93/0xb0 mm/kasan/common.c:414 kasan_kmalloc include/linux/kasan.h:262 [inline] __kmalloc_cache_noprof+0x3e2/0x700 mm/slub.c:5758 kmalloc_noprof include/linux/slab.h:957 [inline] kzalloc_noprof include/linux/slab.h:1094 [inline] kvm_set_memory_region+0x747/0xb90 virt/kvm/kvm_main.c:2104 kvm_vm_ioctl_set_memory_region+0x6f/0xd0 virt/kvm/kvm_main.c:2154 kvm_vm_ioctl+0x957/0xc60 virt/kvm/kvm_main.c:5201 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:597 [inline] __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:583 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0xfa0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f

Freed by task 6023: kasan_save_stack mm/kasan/common.c:56 [inline] kasan_save_track+0x3e/0x80 mm/kasan/common.c:77 kasan_save_free_info+0x46/0x50 mm/kasan/generic.c:584 poison_slab_object mm/kasan/common.c:252 [inline] __kasan_slab_free+0x5c/0x80 mm/kasan/common.c:284 kasan_slab_free include/linux/kasan.h:234 [inline] slab_free_hook mm/slub.c:2533 [inline] slab_free mm/slub.c:6622 [inline] kfree+0x19a/0x6d0 mm/slub.c:6829 kvm_set_memory_region+0x9c4/0xb90 virt/kvm/kvm_main.c:2130 kvm_vm_ioctl_set_memory_region+0x6f/0xd0 virt/kvm/kvm_main.c:2154 kvm_vm_ioctl+0x957/0xc60 virt/kvm/kvm_main.c:5201 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:597 [inline] __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:583 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0xfa0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f

Deliberately don't acquire filemap invalid lock when the file is dying as the lifecycle of f_mapping is outside the purview of KVM. Dereferencing the mapping is *probably* fine, but there's no need to invalidate anything as memslot deletion is responsible for zapping SPTEs, and the only code that can access the dying file is kvm_gmem_release(), whose core code is mutual ---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 BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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
4th
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. 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 (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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

December 6, 2025

Last Modified

August 5, 2026

Advisory Details (3)

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

KVM: guest_memfd: Remove bindings on memslot deletion when gmem is dying - kernel/git/stable/linux.git - Linux kernel stable tree

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

KVM: guest_memfd: Remove bindings on memslot deletion when gmem is dying - kernel/git/stable/linux.git - Linux kernel stable tree

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

KVM: guest_memfd: Remove bindings on memslot deletion when gmem is dying - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/393893693a523e053f84d69320d090b93503f79f

Vendor Advisories for CVE-2025-40274(1)

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

Patch Availability(7)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-gcp-64k-6.17 (6.17.0-1007.7) @ questing2026-10-27ubuntu
ubuntulinux-tools-oem-6.17 (6.17.0-1011.11) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-6.17 (6.17.0-1008.8) @ questing2026-10-27ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1035.38) @ noble2026-10-27ubuntu
ubuntulinux-tools-oracle-64k-6.17 (6.17.0-1007.7) @ questing2026-10-27ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.17.0-14.14) @ questing2026-10-27ubuntu
linuxKernel @ 6.12.59 (fixes >=6.8.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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.63-1~bpo12+1 (8 versions)
  • every version up to 6.12.63-1: fixed in 6.12.63-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.17.8-1~bpo13+1 (80 versions)
  • every version up to 6.17.9-1: fixed in 6.17.9-1
—

All Vendor Advisories

(6)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 9× 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 98 of 238 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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 140 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2025-40274?
CVE-2025-40274 is a high-severity vulnerability; its CVE record was published on December 6, 2025. In the Linux kernel, the following vulnerability has been resolved: KVM: guest_memfd: Remove bindings on memslot deletion when gmem is dying When unbinding a memslot from a guest_memfd instance, remove the bindings even if the guest_memfd file is dying, i.e. even if its file refcount has gone to…
When was the CVE record for CVE-2025-40274 published?
The CVE record for CVE-2025-40274 was published on December 6, 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 August 5, 2026; the record at its source may have been updated since.
Is CVE-2025-40274 actively exploited?
CVE-2025-40274 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-40274?
CVE-2025-40274 has a CVSS base score of 7.8 (the CNA's own assessment, by linux; NVD's own analysis pending).
How do I remediate CVE-2025-40274?
A fix for CVE-2025-40274 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-40274 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-40274

Explore →

Is Your Infrastructure Affected by CVE-2025-40274?

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

Book a Demo →Browse All CVEs