CVE-2025-39828

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-09-16. 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-29586 (ENISA EUVD) · GHSA-2v5c-9mj7-vp9g (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: atmtcp: Prevent arbitrary write in atmtcp_recv_control().

syzbot reported the splat below. [0]

When atmtcp_v_open() or atmtcp_v_close() is called via connect() or close(), atmtcp_send_control() is called to send an in-kernel special message.

The message has ATMTCP_HDR_MAGIC in atmtcp_control.hdr.length. Also, a pointer of struct atm_vcc is set to atmtcp_control.vcc.

The notable thing is struct atmtcp_control is uAPI but has a space for an in-kernel pointer.

struct atmtcp_control { struct atmtcp_hdr hdr; /* must be first */ ... atm_kptr_t vcc; /* both directions */ ... } __ATM_API_ALIGN;

typedef struct { unsigned char _[8]; } __ATM_API_ALIGN atm_kptr_t;

The special message is processed in atmtcp_recv_control() called from atmtcp_c_send().

atmtcp_c_send() is vcc->dev->ops->send() and called from 2 paths:

  • .ndo_start_xmit() (vcc->send() == atm_send_aal0())
  • vcc_sendmsg()

The problem is sendmsg() does not validate the message length and userspace can abuse atmtcp_recv_control() to overwrite any kptr by atmtcp_control.

Let's add a new ->pre_send() hook to validate messages from sendmsg().

[0]: Oops: general protection fault, probably for non-canonical address 0xdffffc00200000ab: 0000 [#1] SMP KASAN PTI KASAN: probably user-memory-access in range [0x0000000100000558-0x000000010000055f] CPU: 0 UID: 0 PID: 5865 Comm: syz-executor331 Not tainted 6.17.0-rc1-syzkaller-00215-gbab3ce404553 #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025 RIP: 0010:atmtcp_recv_control drivers/atm/atmtcp.c:93 [inline] RIP: 0010:atmtcp_c_send+0x1da/0x950 drivers/atm/atmtcp.c:297 Code: 4d 8d 75 1a 4c 89 f0 48 c1 e8 03 42 0f b6 04 20 84 c0 0f 85 15 06 00 00 41 0f b7 1e 4d 8d b7 60 05 00 00 4c 89 f0 48 c1 e8 03 <42> 0f b6 04 20 84 c0 0f 85 13 06 00 00 66 41 89 1e 4d 8d 75 1c 4c RSP: 0018:ffffc90003f5f810 EFLAGS: 00010203 RAX: 00000000200000ab RBX: 0000000000000000 RCX: 0000000000000000 RDX: ffff88802a510000 RSI: 00000000ffffffff RDI: ffff888030a6068c RBP: ffff88802699fb40 R08: ffff888030a606eb R09: 1ffff1100614c0dd R10: dffffc0000000000 R11: ffffffff8718fc40 R12: dffffc0000000000 R13: ffff888030a60680 R14: 000000010000055f R15: 00000000ffffffff FS: 00007f8d7e9236c0(0000) GS:ffff888125c1c000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000000000045ad50 CR3: 0000000075bde000 CR4: 00000000003526f0 Call Trace: vcc_sendmsg+0xa10/0xc60 net/atm/common.c:645 sock_sendmsg_nosec net/socket.c:714 [inline] __sock_sendmsg+0x219/0x270 net/socket.c:729 ____sys_sendmsg+0x505/0x830 net/socket.c:2614 ___sys_sendmsg+0x21f/0x2a0 net/socket.c:2668 __sys_sendmsg net/socket.c:2700 [inline] __do_sys_sendmsg net/socket.c:2705 [inline] __se_sys_sendmsg net/socket.c:2703 [inline] __x64_sys_sendmsg+0x19b/0x260 net/socket.c:2703 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f8d7e96a4a9 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:00007f8d7e923198 EFLAGS: 00000246 ORIG_RAX: 000000000000002e RAX: ffffffffffffffda RBX: 00007f8d7e9f4308 RCX: 00007f8d7e96a4a9 RDX: 0000000000000000 RSI: 0000200000000240 RDI: 0000000000000005 RBP: 00007f8d7e9f4300 R08: 65732f636f72702f R09: 65732f636f72702f R10: 65732f636f72702f R11: 0000000000000246 R12: 00007f8d7e9c10ac R13: 00007f8d7e9231a0 R14: 0000200000000200 R15: 0000200000000250 Modules linked in:

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
6th
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-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 (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

September 16, 2025

Last Modified

October 19, 2026

Advisory Details (10)

Auto-updated Sep 24, 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: atmtcp: Prevent arbitrary write in atmtcp_recv_control(). - kernel/git/stable/linux.git - Linux kernel stable tree

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

atm: atmtcp: Prevent arbitrary write in atmtcp_recv_control(). - kernel/git/stable/linux.git - Linux kernel stable tree

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

atm: atmtcp: Prevent arbitrary write in atmtcp_recv_control(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/62f368472b0aa4b5d91d9b983152855c6b6d8925
Web page

atm: atmtcp: Prevent arbitrary write in atmtcp_recv_control(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/51872b26429077be611b0a1816e0e722278015c3
Web page

atm: atmtcp: Prevent arbitrary write in atmtcp_recv_control(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3c80c230d6e3e6f63d43f4c3f0bb344e3e8b119b
Web page

atm: atmtcp: Prevent arbitrary write in atmtcp_recv_control(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3ab9f5ad9baefe6d3d4c37053cdfca2761001dfe
Web page

atm: atmtcp: Prevent arbitrary write in atmtcp_recv_control(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/33f9e6dc66b32202b95fc861e6b3ea4b0c185b0b
Web page

atm: atmtcp: Prevent arbitrary write in atmtcp_recv_control(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0a6a6d4fb333f7afe22e59ffed18511a7a98efc8

Vendor Advisories for CVE-2025-39828(1)

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

Patch Availability(20)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1101.86) @ jammy2026-10-27ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1102.111~20.04.1) @ focal2026-10-27ubuntu
ubuntulinux-tools-kvm-5.15 (5.15.0.1089.85) @ jammy2026-10-27ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1091.89) @ jammy2026-10-27ubuntu
ubuntulinux-tools-gcp-fips-5.15 (5.15.0.1097.87) @ jammy2026-10-27ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1101.99) @ jammy2026-10-27ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1045.46) @ noble2026-10-27ubuntu
ubuntulinux-tools-aws-edge (6.8.0-1050.53~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1051.57) @ noble2026-10-27ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2040.41) @ noble2026-10-27ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1029.30) @ noble2026-10-27ubuntu
ubuntulinux-virtual-6.8 (6.8.0-106.106) @ noble2026-10-27ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1049.52.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-gkeop-5.15 (5.15.0.1080.79) @ jammy2026-10-27ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1052.55+fips1) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1052.58+fips1) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1051.57~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1061 (5.15.0-1061.65) @ jammy2026-10-27ubuntu
ubuntulinux-tools-realtime-5.15 (5.15.0.1096.100) @ jammy2026-10-27ubuntu
linuxKernel @ 5.4.298 (fixes >=2.6.12)—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 (43 versions)
  • every version up to 6.1.153-1: fixed in 6.1.153-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1, 6.12.41-1, 6.12.43-1, 6.12.43-1~bpo12+1
  • every version up to 6.12.48-1: fixed in 6.12.48-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.16~rc7-1~exp1 (63 versions)
  • every version up to 6.16.5-1: fixed in 6.16.5-1
—

Additional Vendor Advisories

(19)

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

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2025-39828?
CVE-2025-39828 is a high-severity vulnerability; its CVE record was published on September 16, 2025. In the Linux kernel, the following vulnerability has been resolved: atm: atmtcp: Prevent arbitrary write in atmtcp_recv_control(). syzbot reported the splat below. [0] When atmtcp_v_open() or atmtcp_v_close() is called via connect() or close(), atmtcp_send_control() is called to send an in-kernel…
When was the CVE record for CVE-2025-39828 published?
The CVE record for CVE-2025-39828 was published on September 16, 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 19, 2026; the record at its source may have been updated since.
Is CVE-2025-39828 actively exploited?
CVE-2025-39828 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-39828?
CVE-2025-39828 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2025-39828?
A fix for CVE-2025-39828 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-39828 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-39828

Explore →

Is Your Infrastructure Affected by CVE-2025-39828?

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

Book a Demo →Browse All CVEs