CVE-2025-38323

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-10. 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-20923 (ENISA EUVD) · GHSA-q8ww-99pm-fjf2 (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:

net: atm: add lec_mutex

syzbot found its way in net/atm/lec.c, and found an error path in lecd_attach() could leave a dangling pointer in dev_lec[].

Add a mutex to protect dev_lecp[] uses from lecd_attach(), lec_vcc_attach() and lec_mcast_attach().

Following patch will use this mutex for /proc/net/atm/lec.

BUG: KASAN: slab-use-after-free in lecd_attach net/atm/lec.c:751 [inline] BUG: KASAN: slab-use-after-free in lane_ioctl+0x2224/0x23e0 net/atm/lec.c:1008 Read of size 8 at addr ffff88807c7b8e68 by task syz.1.17/6142

CPU: 1 UID: 0 PID: 6142 Comm: syz.1.17 Not tainted 6.16.0-rc1-syzkaller-00239-g08215f5486ec #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025 Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:408 [inline] print_report+0xcd/0x680 mm/kasan/report.c:521 kasan_report+0xe0/0x110 mm/kasan/report.c:634 lecd_attach net/atm/lec.c:751 [inline] lane_ioctl+0x2224/0x23e0 net/atm/lec.c:1008 do_vcc_ioctl+0x12c/0x930 net/atm/ioctl.c:159 sock_do_ioctl+0x118/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+0x18e/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

Allocated by task 6132: kasan_save_stack+0x33/0x60 mm/kasan/common.c:47 kasan_save_track+0x14/0x30 mm/kasan/common.c:68 poison_kmalloc_redzone mm/kasan/common.c:377 [inline] __kasan_kmalloc+0xaa/0xb0 mm/kasan/common.c:394 kasan_kmalloc include/linux/kasan.h:260 [inline] __do_kmalloc_node mm/slub.c:4328 [inline] __kvmalloc_node_noprof+0x27b/0x620 mm/slub.c:5015 alloc_netdev_mqs+0xd2/0x1570 net/core/dev.c:11711 lecd_attach net/atm/lec.c:737 [inline] lane_ioctl+0x17db/0x23e0 net/atm/lec.c:1008 do_vcc_ioctl+0x12c/0x930 net/atm/ioctl.c:159 sock_do_ioctl+0x118/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+0x18e/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

Freed by task 6132: kasan_save_stack+0x33/0x60 mm/kasan/common.c:47 kasan_save_track+0x14/0x30 mm/kasan/common.c:68 kasan_save_free_info+0x3b/0x60 mm/kasan/generic.c:576 poison_slab_object mm/kasan/common.c:247 [inline] __kasan_slab_free+0x51/0x70 mm/kasan/common.c:264 kasan_slab_free include/linux/kasan.h:233 [inline] slab_free_hook mm/slub.c:2381 [inline] slab_free mm/slub.c:4643 [inline] kfree+0x2b4/0x4d0 mm/slub.c:4842 free_netdev+0x6c5/0x910 net/core/dev.c:11892 lecd_attach net/atm/lec.c:744 [inline] lane_ioctl+0x1ce8/0x23e0 net/atm/lec.c:1008 do_vcc_ioctl+0x12c/0x930 net/atm/ioctl.c:159 sock_do_ioctl+0x118/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+0x18e/0x210 fs/ioctl.c:893

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 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.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 (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-10-26). 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

July 10, 2025

Last Modified

December 19, 2025

Advisory Details (10)

Auto-updated Oct 10, 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

net: atm: add lec_mutex - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: atm: add lec_mutex - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: atm: add lec_mutex - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: atm: add lec_mutex - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: atm: add lec_mutex - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: atm: add lec_mutex - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/64b378db28a967f7b271b055380c2360279aa424
Web page

net: atm: add lec_mutex - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/18e8f0c4f826fb08c2d3825cdd6c57e24b207e0a
Web page

net: atm: add lec_mutex - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/17e156a94e94a906a570dbf9b48877956c60bef8

Vendor Advisories for CVE-2025-38323(1)

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

Patch Availability(18)

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.35-1: fixed in 6.12.35-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.35-1: fixed in 6.12.35-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(17)

Data Freshness Timeline

(refreshed 10× in last 7d / 41× 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 194 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 96 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2025-38323?
CVE-2025-38323 is a high-severity vulnerability; its CVE record was published on July 10, 2025. In the Linux kernel, the following vulnerability has been resolved: net: atm: add lec_mutex syzbot found its way in net/atm/lec.c, and found an error path in lecd_attach() could leave a dangling pointer in dev_lec[]. Add a mutex to protect dev_lecp[] uses from lecd_attach(), lec_vcc_attach() and…
When was the CVE record for CVE-2025-38323 published?
The CVE record for CVE-2025-38323 was published on July 10, 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 December 19, 2025; the record at its source may have been updated since.
Is CVE-2025-38323 actively exploited?
CVE-2025-38323 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-38323?
CVE-2025-38323 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2025-38323?
A fix for CVE-2025-38323 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-38323 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-38323

Explore →

Is Your Infrastructure Affected by CVE-2025-38323?

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