CVE-2025-38470

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Score 5.5 from GitHub Security Advisory published 2025-07-28. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2025-22892 (ENISA EUVD) · GHSA-wcqx-2f73-xqmx (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

net: vlan: fix VLAN 0 refcount imbalance of toggling filtering during runtime

Assuming the "rx-vlan-filter" feature is enabled on a net device, the 8021q module will automatically add or remove VLAN 0 when the net device is put administratively up or down, respectively. There are a couple of problems with the above scheme.

The first problem is a memory leak that can happen if the "rx-vlan-filter" feature is disabled while the device is running:

# ip link add bond1 up type bond mode 0 # ethtool -K bond1 rx-vlan-filter off # ip link del dev bond1

When the device is put administratively down the "rx-vlan-filter" feature is disabled, so the 8021q module will not remove VLAN 0 and the memory will be leaked [1].

Another problem that can happen is that the kernel can automatically delete VLAN 0 when the device is put administratively down despite not adding it when the device was put administratively up since during that time the "rx-vlan-filter" feature was disabled. null-ptr-unref or bug_on[2] will be triggered by unregister_vlan_dev() for refcount imbalance if toggling filtering during runtime:

$ ip link add bond0 type bond mode 0 $ ip link add link bond0 name vlan0 type vlan id 0 protocol 802.1q $ ethtool -K bond0 rx-vlan-filter off $ ifconfig bond0 up $ ethtool -K bond0 rx-vlan-filter on $ ifconfig bond0 down $ ip link del vlan0

Root cause is as below: step1: add vlan0 for real_dev, such as bond, team. register_vlan_dev vlan_vid_add(real_dev,htons(ETH_P_8021Q),0) //refcnt=1 step2: disable vlan filter feature and enable real_dev step3: change filter from 0 to 1 vlan_device_event vlan_filter_push_vids ndo_vlan_rx_add_vid //No refcnt added to real_dev vlan0 step4: real_dev down vlan_device_event vlan_vid_del(dev, htons(ETH_P_8021Q), 0); //refcnt=0 vlan_info_rcu_free //free vlan0 step5: delete vlan0 unregister_vlan_dev BUG_ON(!vlan_info); //vlan_info is null

Fix both problems by noting in the VLAN info whether VLAN 0 was automatically added upon NETDEV_UP and based on that decide whether it should be deleted upon NETDEV_DOWN, regardless of the state of the "rx-vlan-filter" feature.

[1] unreferenced object 0xffff8880068e3100 (size 256): comm "ip", pid 384, jiffies 4296130254 hex dump (first 32 bytes): 00 20 30 0d 80 88 ff ff 00 00 00 00 00 00 00 00 . 0............. 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace (crc 81ce31fa): __kmalloc_cache_noprof+0x2b5/0x340 vlan_vid_add+0x434/0x940 vlan_device_event.cold+0x75/0xa8 notifier_call_chain+0xca/0x150 __dev_notify_flags+0xe3/0x250 rtnl_configure_link+0x193/0x260 rtnl_newlink_create+0x383/0x8e0 __rtnl_newlink+0x22c/0xa40 rtnl_newlink+0x627/0xb00 rtnetlink_rcv_msg+0x6fb/0xb70 netlink_rcv_skb+0x11f/0x350 netlink_unicast+0x426/0x710 netlink_sendmsg+0x75a/0xc20 __sock_sendmsg+0xc1/0x150 ____sys_sendmsg+0x5aa/0x7b0 ___sys_sendmsg+0xfc/0x180

[2] kernel BUG at net/8021q/vlan.c:99! Oops: invalid opcode: 0000 [#1] SMP KASAN PTI CPU: 0 UID: 0 PID: 382 Comm: ip Not tainted 6.16.0-rc3 #61 PREEMPT(voluntary) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:unregister_vlan_dev (net/8021q/vlan.c:99 (discriminator 1)) RSP: 0018:ffff88810badf310 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffff88810da84000 RCX: ffffffffb47ceb9a RDX: dffffc0000000000 RSI: 0000000000000008 RDI: ffff88810e8b43c8 RBP: 0000000000000000 R08: 0000000000000000 R09: fffffbfff6cefe80 R10: ffffffffb677f407 R11: ffff88810badf3c0 R12: ffff88810e8b4000 R13: 0000000000000000 R14: ffff88810642a5c0 R15: 000000000000017e FS: 00007f1ff68c20c0(0000) GS:ffff888163a24000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f1ff5dad240 CR3: 0000000107e56000 CR4: 00000000000006f0 Call Trace:

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/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)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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
10th
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 (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-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. 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 (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)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 Vulnrichment) · Technical impact total (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 28, 2025

Last Modified

October 15, 2026

Advisory Details (10)

Auto-updated Aug 2, 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: vlan: fix VLAN 0 refcount imbalance of toggling filtering during runtime - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: vlan: fix VLAN 0 refcount imbalance of toggling filtering during runtime - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: vlan: fix VLAN 0 refcount imbalance of toggling filtering during runtime - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: vlan: fix VLAN 0 refcount imbalance of toggling filtering during runtime - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/93715aa2d80e6c5cea1bb486321fc4585076928b
Web page

net: vlan: fix VLAN 0 refcount imbalance of toggling filtering during runtime - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8984bcbd1edf5bee5be06ad771d157333b790c33
Web page

net: vlan: fix VLAN 0 refcount imbalance of toggling filtering during runtime - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/579d4f9ca9a9a605184a9b162355f6ba131f678d
Web page

net: vlan: fix VLAN 0 refcount imbalance of toggling filtering during runtime - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/35142b3816832889e50164d993018ea5810955ae
Web page

net: vlan: fix VLAN 0 refcount imbalance of toggling filtering during runtime - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/047b61a24d7c866c502aeeea482892969a68f216

Vendor Advisories for CVE-2025-38470(3)

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-raspi-6.14 (6.14.0-1018.18) @ plucky2026-05-21ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1091.89) @ jammy2026-05-21ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1101.86) @ jammy2026-05-21ubuntu
ubuntulinux-tools-realtime-5.15 (5.15.0.1096.100) @ jammy2026-05-21ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1101.99) @ jammy2026-05-21ubuntu
ubuntulinux-virtual-6.8 (6.8.0-100.100) @ noble2026-05-21ubuntu
ubuntulinux-tools-gkeop-5.15 (5.15.0.1080.79) @ jammy2026-05-21ubuntu
ubuntulinux-tools-azure-6.14 (6.14.0-1017.17) @ plucky2026-05-21ubuntu
ubuntulinux-tools-realtime-hwe-22.04 (6.8.1-1041.42~22.04.1) @ jammy2026-05-21ubuntu
ubuntulinux-tools-kvm-5.15 (5.15.0.1089.85) @ jammy2026-05-21ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1102.111~20.04.1) @ focal2026-05-21ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-100.100+fips1) @ noble2026-05-21ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1047.50~22.04.2) @ jammy2026-05-21ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1047.50+fips1) @ noble2026-05-21ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-100.100~22.04.1) @ jammy2026-05-21ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1041.42) @ noble2026-05-21ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1043.44~22.04.1) @ jammy2026-05-21ubuntu
ubuntulinux-tools-gke-64k-6.8 (6.8.0-1043.48) @ noble2026-05-21ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-100.100.1) @ noble2026-05-21ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1046.49.1) @ noble2026-05-21ubuntu
ubuntulinux-tools-ibm-lts-24.04 (6.8.0-1044.44) @ noble2026-05-21ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1023.24) @ noble2026-05-21ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1046.52) @ noble2026-05-21ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1046.52+fips1) @ noble2026-05-21ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1051.57~22.04.1) @ jammy2026-05-21ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.14.0-36.36) @ plucky2026-05-21ubuntu
ubuntulinux-tools-oracle-edge (6.14.0-1017.17~24.04.1) @ noble2026-05-21ubuntu
ubuntulinux-tools-oem-6.14 (6.14.0-1016.16) @ noble2026-05-21ubuntu
redhatkernel-0:6.12.0-211.7.1.el10_22026-05-19redhat
redhatkernel-0:5.14.0-687.5.1.el9_82026-05-19redhat
linuxKernel @ 5.4.297 (fixes >=2.6.36)—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
linux6.12.38-1
  • every version up to 6.12.41-1: fixed in 6.12.41-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.16~rc7-1~exp1 (62 versions)
  • every version up to 6.16.3-1: fixed in 6.16.3-1
—

Additional Vendor Advisories

(22)

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 8× 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 230 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 132 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2025-38470?
CVE-2025-38470 is a medium-severity vulnerability; its CVE record was published on July 28, 2025. In the Linux kernel, the following vulnerability has been resolved: net: vlan: fix VLAN 0 refcount imbalance of toggling filtering during runtime Assuming the "rx-vlan-filter" feature is enabled on a net device, the 8021q module will automatically add or remove VLAN 0 when the net device is put…
When was the CVE record for CVE-2025-38470 published?
The CVE record for CVE-2025-38470 was published on July 28, 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-38470 actively exploited?
CVE-2025-38470 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-38470?
CVE-2025-38470 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-38470?
A fix for CVE-2025-38470 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-38470 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-38470

Explore →

Is Your Infrastructure Affected by CVE-2025-38470?

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

Book a Demo →Browse All CVEs