CVE-2025-38617 — net/packet: fix a race in packet_set_ring() and packet_notifier()
In the Linux kernel, the following vulnerability has been resolved: net/packet: fix a race in packet_set_ring() and packet_notifier() When packet_set_ring() releases po->bind_lock, another thread can run packet_notifier() and process an NETDEV_UP event. This race and the fix are both similar to that of commit 15fe076edea7 ("net/packet: fix a race in packet_bind() and packet_notifier()"). There too the packet_notifier NETDEV_UP event managed to run while a po->bind_lock critical section had to be temporarily released. And the fix was similarly to temporarily set po->num to zero to keep the socket unhooked until the lock is retaken. The po->bind_lock in packet_set_ring and packet_notifier precede the introduction of git history.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.4% (30-day exploitation probability)+5
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Debian Debian Linux, Linux Linux, Linux Linux Kernel).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes matching the vulnerability class (logic error), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Debian | Debian Linux | version 11.0 | Vulnerable | NIST National Vulnerability Database |
| Linux | Linux |
version 2.6.12≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 01d3c8417b9c1b884a8a981a3b886da556512f36≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < f1791fd7b845bea0ce9674fcf2febee7bc87a893≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < e50ccfaca9e3c671cae917dcb994831a859cf588≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < f2e8fcfd2b1bc754920108b7f2cd75082c5a18df≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 88caf46db8239e6471413d28aabaa6b8bd552805≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 7de07705007c7e34995a5599aaab1d23e762d7ca≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < ba2257034755ae773722f15f4c3ad1dcdad15ca9 and 2 more≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 7da733f117533e9b2ebbd530a22ae4028713955c≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 18f13f2a83eb81be349a9757ba2141ff1da9ad73 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
| Linux | Linux Kernel |
version 2.6.12-rc4version 2.6.12-rc5version 2.6.12-rc3version 2.6.12-rc2version 2.6.12≥ 6.16 and < 6.16.1≥ 6.13 and < 6.15.10≥ 6.7 and < 6.12.42 and 5 more≥ 6.2 and < 6.6.102≥ 5.16 and < 6.1.148≥ 5.11 and < 5.15.190≥ 5.5 and < 5.10.241≥ 2.6.13 and < 5.4.297 |
Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.8 | CVSS 3.1 | High | 1.8 | 5.9 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database |
| 7.8 | CVSS 3.1 | High | — | — | Linux via CVE Program (cve.org) e CISA ADP |
| 4.7 | CVSS 3.1 | Medium | 1.0 | 3.6 | nvd@nist.gov via NIST National Vulnerability Database |
| 4.7 | CVSS 3.1 | Medium | — | — | GitHub, Inc. via GitHub Security Advisories |
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Timeline
What happened to this CVE, newest first.
- 2026
- SSVC assessment updated
- Affected products added · linux/linux
- Record published
- Fix documented
- Affected products added · linux/linux kernel, debian/debian linux
- CVSS changed · 4.7
- Source status changed · → Modified
- Record created in this database
- 2025
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 14, 2026 – Oct 14, 2026
- 1× Official description updated · Oct 14, 2026 – Oct 14, 2026
References
15 on the record
- git.kernel.org/stable/c/18f13f2a83eb81be349a9757ba2141ff1da9ad73
- git.kernel.org/stable/c/f1791fd7b845bea0ce9674fcf2febee7bc87a893
- git.kernel.org/stable/c/01d3c8417b9c1b884a8a981a3b886da556512f36
- git.kernel.org/stable/c/7de07705007c7e34995a5599aaab1d23e762d7ca
- git.kernel.org/stable/c/ba2257034755ae773722f15f4c3ad1dcdad15ca9
- git.kernel.org/stable/c/e50ccfaca9e3c671cae917dcb994831a859cf588
- git.kernel.org/stable/c/88caf46db8239e6471413d28aabaa6b8bd552805
- git.kernel.org/stable/c/f2e8fcfd2b1bc754920108b7f2cd75082c5a18df
- git.kernel.org/stable/c/7da733f117533e9b2ebbd530a22ae4028713955c
- github.com/advisories/GHSA-g6xr-fxvq-ffp4
- blog.calif.io/p/a-race-within-a-race-exploiting-cve
- lists.debian.org/debian-lts-announce/2025/10/msg00007.html
- nvd.nist.gov/vuln/detail/CVE-2025-38617
- lists.debian.org/debian-lts-announce/2025/10/msg00008.html
- github.com/google/security-research/pull/339
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 10h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 10h
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2025-38617 is "net/packet: fix a race in packet_set_ring() and packet_notifier()", rated Medium. It affects Debian Linux (Debian); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 4.7 describes technical severity. EPSS 0.40% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.