CVE-2025-38245

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 2025-07-09. 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-2025-20816 (ENISA EUVD) · GHSA-w7f8-76rv-q749 (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.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

atm: Release atm_dev_mutex after removing procfs in atm_dev_deregister().

syzbot reported a warning below during atm_dev_register(). [0]

Before creating a new device and procfs/sysfs for it, atm_dev_register() looks up a duplicated device by __atm_dev_lookup(). These operations are done under atm_dev_mutex.

However, when removing a device in atm_dev_deregister(), it releases the mutex just after removing the device from the list that __atm_dev_lookup() iterates over.

So, there will be a small race window where the device does not exist on the device list but procfs/sysfs are still not removed, triggering the splat.

Let's hold the mutex until procfs/sysfs are removed in atm_dev_deregister().

[0]: proc_dir_entry 'atm/atmtcp:0' already registered WARNING: CPU: 0 PID: 5919 at fs/proc/generic.c:377 proc_register+0x455/0x5f0 fs/proc/generic.c:377 Modules linked in: CPU: 0 UID: 0 PID: 5919 Comm: syz-executor284 Not tainted 6.16.0-rc2-syzkaller-00047-g52da431bf03b #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025 RIP: 0010:proc_register+0x455/0x5f0 fs/proc/generic.c:377 Code: 48 89 f9 48 c1 e9 03 80 3c 01 00 0f 85 a2 01 00 00 48 8b 44 24 10 48 c7 c7 20 c0 c2 8b 48 8b b0 d8 00 00 00 e8 0c 02 1c ff 90 <0f> 0b 90 90 48 c7 c7 80 f2 82 8e e8 0b de 23 09 48 8b 4c 24 28 48 RSP: 0018:ffffc9000466fa30 EFLAGS: 00010282 RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff817ae248 RDX: ffff888026280000 RSI: ffffffff817ae255 RDI: 0000000000000001 RBP: ffff8880232bed48 R08: 0000000000000001 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000001 R12: ffff888076ed2140 R13: dffffc0000000000 R14: ffff888078a61340 R15: ffffed100edda444 FS: 00007f38b3b0c6c0(0000) GS:ffff888124753000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f38b3bdf953 CR3: 0000000076d58000 CR4: 00000000003526f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: proc_create_data+0xbe/0x110 fs/proc/generic.c:585 atm_proc_dev_register+0x112/0x1e0 net/atm/proc.c:361 atm_dev_register+0x46d/0x890 net/atm/resources.c:113 atmtcp_create+0x77/0x210 drivers/atm/atmtcp.c:369 atmtcp_attach drivers/atm/atmtcp.c:403 [inline] atmtcp_ioctl+0x2f9/0xd60 drivers/atm/atmtcp.c:464 do_vcc_ioctl+0x12c/0x930 net/atm/ioctl.c:159 sock_do_ioctl+0x115/0x280 net/socket.c:1190 sock_ioctl+0x227/0x6b0 net/socket.c:1311 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:907 [inline] __se_sys_ioctl fs/ioctl.c:893 [inline] __x64_sys_ioctl+0x18b/0x210 fs/ioctl.c:893 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xcd/0x4c0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f38b3b74459 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 51 18 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f38b3b0c198 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007f38b3bfe318 RCX: 00007f38b3b74459 RDX: 0000000000000000 RSI: 0000000000006180 RDI: 0000000000000005 RBP: 00007f38b3bfe310 R08: 65732f636f72702f R09: 65732f636f72702f R10: 65732f636f72702f R11: 0000000000000246 R12: 00007f38b3bcb0ac R13: 00007f38b3b0c1a0 R14: 0000200000000200 R15: 00007f38b3bcb03b

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.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 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.2%
EPSS %ILE
8th
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.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-05). 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

July 9, 2025

Last Modified

November 5, 2026

Advisory Details (10)

Auto-updated Oct 1, 2026
Patch available.
Web pageMentions a patch (unverified)

[SECURITY] [DLA 4328-1] linux-6.1 security update

https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html
Web pageMentions a patch (unverified)

[SECURITY] [DLA 4327-1] linux security update

https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html
Web page

atm: Release atm_dev_mutex after removing procfs in atm_dev_deregister(). - kernel/git/stable/linux.git - Linux kernel stable tree

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

atm: Release atm_dev_mutex after removing procfs in atm_dev_deregister(). - kernel/git/stable/linux.git - Linux kernel stable tree

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

atm: Release atm_dev_mutex after removing procfs in atm_dev_deregister(). - kernel/git/stable/linux.git - Linux kernel stable tree

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

atm: Release atm_dev_mutex after removing procfs in atm_dev_deregister(). - kernel/git/stable/linux.git - Linux kernel stable tree

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

atm: Release atm_dev_mutex after removing procfs in atm_dev_deregister(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6922f1a048c090f10704bbef4a3a1e81932d2e0a
Web page

atm: Release atm_dev_mutex after removing procfs in atm_dev_deregister(). - kernel/git/stable/linux.git - Linux kernel stable tree

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

atm: Release atm_dev_mutex after removing procfs in atm_dev_deregister(). - kernel/git/stable/linux.git - Linux kernel stable tree

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

atm: Release atm_dev_mutex after removing procfs in atm_dev_deregister(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/26248d5d68c865b888d632162abbf8130645622c

Vendor Advisories for CVE-2025-38245(1)

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-20.04-edge (5.15.0.156.166~20.04.1) @ focal2026-10-27ubuntu
ubuntulinux-tools-gcp-fips-5.15 (5.15.0.1092.82) @ jammy2026-10-27ubuntu
ubuntulinux-tools-gke-64k-6.8 (6.8.0-1043.48) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-6.14 (6.14.0-1014.14) @ plucky2026-10-27ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.14.0-34.34) @ plucky2026-10-27ubuntu
ubuntulinux-tools-aws-edge (6.14.0-1015.15~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1051.57~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1041.42) @ noble2026-10-27ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-100.100+fips1) @ noble2026-10-27ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1043.44) @ noble2026-10-27ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-100.100~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-100.100.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1046.49.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-ibm-lts-24.04 (6.8.0-1044.44) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1046.52) @ noble2026-10-27ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1023.24) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1046.52+fips1) @ noble2026-10-27ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1090.96~20.04.1) @ focal2026-10-27ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1096.81) @ jammy2026-10-27ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1096.94) @ jammy2026-10-27ubuntu
ubuntulinux-tools-kvm-5.15 (5.15.0.1088.84) @ jammy2026-10-27ubuntu
ubuntulinux-tools-nvidia-tegra-igx-rt-5.15 (5.15.0.1034.36) @ jammy2026-10-27ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1096.105~20.04.1) @ focal2026-10-27ubuntu
ubuntulinux-tools-realtime-5.15 (5.15.0.1092.96) @ jammy2026-10-27ubuntu
ubuntulinux-tools-gcp-edge (6.14.0-1018.19~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.14.0-1014.14~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1047.50+fips1) @ noble2026-10-27ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.14.0-34.34~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-virtual-6.8 (6.8.0-100.100) @ noble2026-10-27ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1047.50~22.04.2) @ jammy2026-10-27ubuntu
linuxKernel @ 5.4.296 (fixes >=2.6.15)—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 ... 5.10.92-2 (46 versions)
  • every version up to 5.10.244-1: fixed in 5.10.244-1
—
linux-6.16.1.106-3~deb11u1 ... 6.1.148-1~deb11u1 (11 versions)
  • every version up to 6.1.153-1~deb11u1: fixed in 6.1.153-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (41 versions)
  • every version up to 6.1.147-1: fixed in 6.1.147-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.37-1: fixed in 6.12.37-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.37-1: fixed in 6.12.37-1
—

Additional Vendor Advisories

(24)

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2025-38245?
CVE-2025-38245 is a high-severity vulnerability; its CVE record was published on July 9, 2025. In the Linux kernel, the following vulnerability has been resolved: atm: Release atm_dev_mutex after removing procfs in atm_dev_deregister(). syzbot reported a warning below during atm_dev_register(). [0] Before creating a new device and procfs/sysfs for it, atm_dev_register() looks up a duplicated…
When was the CVE record for CVE-2025-38245 published?
The CVE record for CVE-2025-38245 was published on July 9, 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 November 5, 2026; the record at its source may have been updated since.
Is CVE-2025-38245 actively exploited?
CVE-2025-38245 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-38245?
CVE-2025-38245 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2025-38245?
A fix for CVE-2025-38245 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-38245 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-38245

Explore →

Is Your Infrastructure Affected by CVE-2025-38245?

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