CVE-2025-38236

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-08. 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-20419 (ENISA EUVD) · GHSA-wqm2-9j5j-vxv3 (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.3%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

af_unix: Don't leave consecutive consumed OOB skbs.

Jann Horn reported a use-after-free in unix_stream_read_generic().

The following sequences reproduce the issue:

$ python3 from socket import * s1, s2 = socketpair(AF_UNIX, SOCK_STREAM) s1.send(b'x', MSG_OOB) s2.recv(1, MSG_OOB) # leave a consumed OOB skb s1.send(b'y', MSG_OOB) s2.recv(1, MSG_OOB) # leave a consumed OOB skb s1.send(b'z', MSG_OOB) s2.recv(1) # recv 'z' illegally s2.recv(1, MSG_OOB) # access 'z' skb (use-after-free)

Even though a user reads OOB data, the skb holding the data stays on the recv queue to mark the OOB boundary and break the next recv().

After the last send() in the scenario above, the sk2's recv queue has 2 leading consumed OOB skbs and 1 real OOB skb.

Then, the following happens during the next recv() without MSG_OOB

  • unix_stream_read_generic() peeks the first consumed OOB skb
  • manage_oob() returns the next consumed OOB skb
  • unix_stream_read_generic() fetches the next not-yet-consumed OOB skb
  • unix_stream_read_generic() reads and frees the OOB skb

, and the last recv(MSG_OOB) triggers KASAN splat.

The 3. above occurs because of the SO_PEEK_OFF code, which does not expect unix_skb_len(skb) to be 0, but this is true for such consumed OOB skbs.

while (skip >= unix_skb_len(skb)) { skip -= unix_skb_len(skb); skb = skb_peek_next(skb, &sk->sk_receive_queue); ... }

In addition to this use-after-free, there is another issue that ioctl(SIOCATMARK) does not function properly with consecutive consumed OOB skbs.

So, nothing good comes out of such a situation.

Instead of complicating manage_oob(), ioctl() handling, and the next ECONNRESET fix by introducing a loop for consecutive consumed OOB skbs, let's not leave such consecutive OOB unnecessarily.

Now, while receiving an OOB skb in unix_stream_recv_urg(), if its previous skb is a consumed OOB skb, it is freed.

[0]: BUG: KASAN: slab-use-after-free in unix_stream_read_actor (net/unix/af_unix.c:3027) Read of size 4 at addr ffff888106ef2904 by task python3/315

CPU: 2 UID: 0 PID: 315 Comm: python3 Not tainted 6.16.0-rc1-00407-gec315832f6f9 #8 PREEMPT(voluntary) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-4.fc42 04/01/2014 Call Trace: dump_stack_lvl (lib/dump_stack.c:122) print_report (mm/kasan/report.c:409 mm/kasan/report.c:521) kasan_report (mm/kasan/report.c:636) unix_stream_read_actor (net/unix/af_unix.c:3027) unix_stream_read_generic (net/unix/af_unix.c:2708 net/unix/af_unix.c:2847) unix_stream_recvmsg (net/unix/af_unix.c:3048) sock_recvmsg (net/socket.c:1063 (discriminator 20) net/socket.c:1085 (discriminator 20)) __sys_recvfrom (net/socket.c:2278) __x64_sys_recvfrom (net/socket.c:2291 (discriminator 1) net/socket.c:2287 (discriminator 1) net/socket.c:2287 (discriminator 1)) do_syscall_64 (arch/x86/entry/syscall_64.c:63 (discriminator 1) arch/x86/entry/syscall_64.c:94 (discriminator 1)) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130) RIP: 0033:0x7f8911fcea06 Code: 5d e8 41 8b 93 08 03 00 00 59 5e 48 83 f8 fc 75 19 83 e2 39 83 fa 08 75 11 e8 26 ff ff ff 66 0f 1f 44 00 00 48 8b 45 10 0f 05 <48> 8b 5d f8 c9 c3 0f 1f 40 00 f3 0f 1e fa 55 48 89 e5 48 83 ec 08 RSP: 002b:00007fffdb0dccb0 EFLAGS: 00000202 ORIG_RAX: 000000000000002d RAX: ffffffffffffffda RBX: 00007fffdb0dcdc8 RCX: 00007f8911fcea06 RDX: 0000000000000001 RSI: 00007f8911a5e060 RDI: 0000000000000006 RBP: 00007fffdb0dccd0 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000001 R11: 0000000000000202 R12: 00007f89119a7d20 R13: ffffffffc4653600 R14: 0000000000000000 R15: 0000000000000000

Allocated by task 315: kasan_save_stack (mm/kasan/common.c:48) kasan_save_track (mm/kasan/common.c:60 (discriminator 1) mm/kasan/common.c:69 (discriminator 1)) __kasan_slab_alloc (mm/kasan/common.c:348) kmem_cache_alloc_ ---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.3% × 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.3%
EPSS %ILE
22nd
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.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). 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 8, 2025

Last Modified

October 15, 2026

Advisory Details (9)

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

SSA-082556

https://cert-portal.siemens.com/productcert/html/ssa-082556.html
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 page

Project Zero

https://project-zero.issues.chromium.org/issues/423023990
Web page

af_unix: Don't leave consecutive consumed OOB skbs. - kernel/git/stable/linux.git - Linux kernel stable tree

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

af_unix: Don't leave consecutive consumed OOB skbs. - kernel/git/stable/linux.git - Linux kernel stable tree

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

af_unix: Don't leave consecutive consumed OOB skbs. - kernel/git/stable/linux.git - Linux kernel stable tree

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

af_unix: Don't leave consecutive consumed OOB skbs. - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/61a9ad7b69ce688697e5f63332f03e17725353bc
Web page

af_unix: Don't leave consecutive consumed OOB skbs. - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/523edfed4f68b7794d85b9ac828c5f8f4442e4c5
Web page

af_unix: Don't leave consecutive consumed OOB skbs. - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/32ca245464e1479bfea8592b9db227fdc1641705

Vendor Advisories for CVE-2025-38236(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-tools-aws-edge (5.15.0.1100.107~20.04.1) @ focal2026-10-28ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-100.100+fips1) @ noble2026-10-28ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1097.93) @ jammy2026-10-28ubuntu
ubuntulinux-tools-nvidia-tegra-igx-rt-5.15 (5.15.0.1041.43) @ jammy2026-10-28ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1095.95) @ jammy2026-10-28ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.14.0-1014.14~24.04.1) @ noble2026-10-28ubuntu
ubuntulinux-tools-aws-edge (6.14.0-1015.15~24.04.1) @ noble2026-10-28ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.14.0-34.34~24.04.1) @ noble2026-10-28ubuntu
ubuntulinux-virtual-6.8 (6.8.0-100.100) @ noble2026-10-28ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-100.100.1) @ noble2026-10-28ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1046.52) @ noble2026-10-28ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1023.24) @ noble2026-10-28ubuntu
ubuntulinux-tools-gke-64k-6.8 (6.8.0-1043.48) @ noble2026-10-28ubuntu
ubuntulinux-tools-ibm-lts-24.04 (6.8.0-1044.44) @ noble2026-10-28ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1046.49.1) @ noble2026-10-28ubuntu
ubuntulinux-tools-realtime-hwe-22.04 (6.8.1-1041.42~22.04.1) @ jammy2026-10-28ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1047.50~22.04.2) @ jammy2026-10-28ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1041.42) @ noble2026-10-28ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1043.44) @ noble2026-10-28ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1095.95) @ jammy2026-10-28ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1047.50+fips1) @ noble2026-10-28ubuntu
ubuntulinux-tools-gcp-edge (6.14.0-1018.19~24.04.1) @ noble2026-10-28ubuntu
ubuntulinux-tools-azure-6.14 (6.14.0-1014.14) @ plucky2026-10-28ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.14.0-34.34) @ plucky2026-10-28ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.170.159) @ jammy2026-10-28ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1109.94) @ jammy2026-10-28ubuntu
ubuntulinux-tools-realtime-5.15 (5.15.0.1099.103) @ jammy2026-10-28ubuntu
ubuntulinux-tools-intel-iotg-edge (5.15.0.1095.101~20.04.1) @ focal2026-10-28ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1046.52+fips1) @ noble2026-10-28ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-100.100~22.04.1) @ jammy2026-10-28ubuntu
linuxKernel @ 5.15.194 (fixes >=5.15.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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
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
—

Weakness Classification(1)

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

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-38236?
CVE-2025-38236 is a high-severity vulnerability; its CVE record was published on July 8, 2025. In the Linux kernel, the following vulnerability has been resolved: af_unix: Don't leave consecutive consumed OOB skbs. Jann Horn reported a use-after-free in unix_stream_read_generic(). The following sequences reproduce the issue: $ python3 from socket import * s1, s2 = socketpair(AF_UNIX,…
When was the CVE record for CVE-2025-38236 published?
The CVE record for CVE-2025-38236 was published on July 8, 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-38236 actively exploited?
CVE-2025-38236 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (22nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-38236?
CVE-2025-38236 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2025-38236?
A fix for CVE-2025-38236 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-38236 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-38236

Explore →

Is Your Infrastructure Affected by CVE-2025-38236?

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

Book a Demo →Browse All CVEs