CVE-2025-39817 — efivarfs: Fix slab-out-of-bounds in efivarfs_d_compare
In the Linux kernel, the following vulnerability has been resolved: efivarfs: Fix slab-out-of-bounds in efivarfs_d_compare Observed on kernel 6.6 (present on master as well): BUG: KASAN: slab-out-of-bounds in memcmp+0x98/0xd0 Call trace: kasan_check_range+0xe8/0x190 __asan_loadN+0x1c/0x28 memcmp+0x98/0xd0 efivarfs_d_compare+0x68/0xd8 __d_lookup_rcu_op_compare+0x178/0x218 __d_lookup_rcu+0x1f8/0x228 d_alloc_parallel+0x150/0x648 lookup_open.isra.0+0x5f0/0x8d0 open_last_lookups+0x264/0x828 path_openat+0x130/0x3f8 do_filp_open+0x114/0x248 do_sys_openat2+0x340/0x3c0 __arm64_sys_openat+0x120/0x1a0 If dentry->d_name.len < EFI_VARIABLE_GUID_LEN , 'guid' can become negative, leadings to oob. The issue can be triggered by parallel lookups using invalid filename: T1 T2 lookup_open ->lookup simple_lookup d_add // invalid dentry is added to hash list lookup_open d_alloc_parallel __d_lookup_rcu __d_lookup_rcu_op_compare hlist_bl_for_each_entry_rcu // invalid dentry can be retrieved ->d_compare efivarfs_d_compare // oob Fix it by checking 'guid' before cmp.
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.2% (30-day exploitation probability)+1
- Technical severity (high)+6
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)
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 (memory corruption), 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 |
≥ da27a24383b2b10bf6ebd0db29b325548aafecb4 and < 0f63fbabeaaaaaaf5b742a2f4c1b4590d50bf1f6version 3.9≥ 3.8.2 and < 3.9version 688289c4b745c018b3449b4b4c5a2030083c8eaf≥ da27a24383b2b10bf6ebd0db29b325548aafecb4 and < a6358f8cf64850f3f27857b8ed8c1b08cfc4685c≥ da27a24383b2b10bf6ebd0db29b325548aafecb4 and < 71581a82f38e5a4d807d71fc1bb59aead80ccf95≥ da27a24383b2b10bf6ebd0db29b325548aafecb4 and < c2925cd6207079c3f4d040d082515db78d63afbf≥ da27a24383b2b10bf6ebd0db29b325548aafecb4 and < 925599eba46045930b850a98ae594d2e3028ac40 and 3 more≥ da27a24383b2b10bf6ebd0db29b325548aafecb4 and < d7f5e35e70507d10cbaff5f9e194ed54c4ee14f7≥ da27a24383b2b10bf6ebd0db29b325548aafecb4 and < 568e7761279b99c6daa3002290fd6d8047ddb6d2≥ da27a24383b2b10bf6ebd0db29b325548aafecb4 and < 794399019301944fd6d2e0d7a51b3327e26c410e |
Vulnerable | CVE Program (cve.org) e CISA ADP |
| Linux | Linux Kernel |
version 6.17-rc3version 6.17-rc2version 6.17-rc1≥ 6.13 and < 6.16.5≥ 6.7 and < 6.12.45≥ 6.2 and < 6.6.104≥ 5.16 and < 6.1.150≥ 5.11 and < 5.15.191 and 2 more≥ 5.5 and < 5.10.242≥ 3.8.2 and < 5.4.298 |
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.1 | CVSS 3.1 | High | 1.8 | 5.2 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database |
| 7.1 | CVSS 3.1 | High | 1.8 | 5.2 | nvd@nist.gov via NIST National Vulnerability Database |
| 7.1 | CVSS 3.1 | High | — | — | GitHub, Inc. via GitHub Security Advisories |
| 7.1 | CVSS 3.1 | High | — | — | Linux via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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.
- 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, debian/debian linux
- CVSS changed · 7.1
- 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 19, 2026 – Oct 19, 2026
- 1× Official description updated · Oct 19, 2026 – Oct 19, 2026
References
13 on the record
- git.kernel.org/stable/c/0f63fbabeaaaaaaf5b742a2f4c1b4590d50bf1f6
- git.kernel.org/stable/c/c2925cd6207079c3f4d040d082515db78d63afbf
- git.kernel.org/stable/c/568e7761279b99c6daa3002290fd6d8047ddb6d2
- git.kernel.org/stable/c/a6358f8cf64850f3f27857b8ed8c1b08cfc4685c
- git.kernel.org/stable/c/794399019301944fd6d2e0d7a51b3327e26c410e
- git.kernel.org/stable/c/925599eba46045930b850a98ae594d2e3028ac40
- git.kernel.org/stable/c/71581a82f38e5a4d807d71fc1bb59aead80ccf95
- git.kernel.org/stable/c/d7f5e35e70507d10cbaff5f9e194ed54c4ee14f7
- cert-portal.siemens.com/productcert/html/ssa-032379.html
- github.com/advisories/GHSA-m685-84xg-fvfj
- lists.debian.org/debian-lts-announce/2025/10/msg00007.html
- nvd.nist.gov/vuln/detail/CVE-2025-39817
- lists.debian.org/debian-lts-announce/2025/10/msg00008.html
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-98868 dm-pcache: reject a kset that overruns its segment 1d
- Unknown CVE-2026-98866 sched/cache: Introduce task_struct->sched_cache_grp to fix UAF 1d
- Unknown CVE-2026-98867 dm-pcache: bound the logical key offset from persistent memory 1d
- Unknown CVE-2026-98865 sched_ext: Don't run ops.dequeue() with a DSQ lock held 1d
- Unknown CVE-2026-98864 sched_ext: Wait for SCX_OPSS_DISPATCHING before reenqueueing a task 1d
- Unknown CVE-2026-98863 KVM: x86: Re-pend GET_NESTED_STATE_PAGES if getting said pages fails 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-39817 is "efivarfs: Fix slab-out-of-bounds in efivarfs_d_compare", rated High. It affects Debian Linux (Debian); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.1 describes technical severity. EPSS 0.17% 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.