CVE-2025-37860 — sfc: fix NULL dereferences in ef100_process_design_param()
In the Linux kernel, the following vulnerability has been resolved: sfc: fix NULL dereferences in ef100_process_design_param() Since cited commit, ef100_probe_main() and hence also ef100_check_design_params() run before efx->net_dev is created; consequently, we cannot netif_set_tso_max_size() or _segs() at this point. Move those netif calls to ef100_probe_netdev(), and also replace netif_err within the design params code with pci_err.
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.3% (30-day exploitation probability)+4
- 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)
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 (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 (memory corruption), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux | ≥ 98ff4c7c8ac7f5339aac6114105395fea19f992e and < a9703b006a475f474a571801ad3dd9b1bda35273≥ 98ff4c7c8ac7f5339aac6114105395fea19f992e and < f21623b8446735b5e2ac5f8ee69b8743177d7b19≥ 98ff4c7c8ac7f5339aac6114105395fea19f992e and < e56391011381d6d029da377a65ac314cb3d5def2≥ 98ff4c7c8ac7f5339aac6114105395fea19f992e and < 8241ecec1cdc6699ae197d52d58e76bddd995fa5version 6.0 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Linux | Linux Kernel | ≥ 6.0 and < 6.14.2 | 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 |
|---|---|---|---|---|---|
| 5.5 | CVSS 3.1 | Medium | 1.8 | 3.6 | nvd@nist.gov via NIST National Vulnerability Database |
| 5.5 | CVSS 3.1 | Medium | 1.8 | 3.6 | 134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database |
| 5.5 | CVSS 3.1 | Medium | — | — | GitHub, Inc. via GitHub Security Advisories |
| 5.5 | CVSS 3.1 | Medium | — | — | CISA-ADP via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:L/AC:L/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.
EPSS over time FIRST
Oct 20, 2026 → Oct 27, 2026 · 8 reading(s) · max 0.32%
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.
- Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- SSVC assessment updated
- Record published
- Fix documented
- Affected products added · linux/linux kernel
- CVSS changed · 5.5
- 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 21, 2026 – Oct 21, 2026
- 1× Official description updated · Oct 21, 2026 – Oct 21, 2026
References
6 on the record
- git.kernel.org/stable/c/8241ecec1cdc6699ae197d52d58e76bddd995fa5
- git.kernel.org/stable/c/e56391011381d6d029da377a65ac314cb3d5def2
- git.kernel.org/stable/c/a9703b006a475f474a571801ad3dd9b1bda35273
- nvd.nist.gov/vuln/detail/CVE-2025-37860
- github.com/advisories/GHSA-j5qc-xcfm-cq6p
- git.kernel.org/stable/c/f21623b8446735b5e2ac5f8ee69b8743177d7b19
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-99215 power: supply: core: prevent unregistering a power supply while a callback runs 10h
- Unknown CVE-2026-99216 Drivers: hv: Don't reset VMBus connection state on error/exit paths 10h
- Unknown CVE-2026-99213 vsock: treat TCP_CLOSING as once-established 10h
- Unknown CVE-2026-99207 scsi: target: Disable interrupts while holding delayed_cmd_lock 10h
- Unknown CVE-2026-99208 drm/xe/oa: Zero OA buffer at allocation 10h
- Unknown CVE-2026-99209 drm/xe: skip eviction of a BO with no resource 10h
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-37860 is "sfc: fix NULL dereferences in ef100_process_design_param()", rated Medium. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.5 describes technical severity. EPSS 0.32% 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.