Security readout for executives and security teams
Plain-English summary
A Linux kernel scheduling flaw can trigger an internal assertion when a netfilter BPF program runs during network transmission without CPU migration disabled. The supplied rating is high because successful exploitation is scored as potentially compromising confidentiality, integrity, and availability, although the public evidence only demonstrates a kernel fault found by syzbot.
Executive priority
Treat as a high-priority kernel update for exposed multi-user or BPF-enabled Linux systems. Schedule remediation through normal expedited patching, focusing first on internet-facing infrastructure with local user access. Emergency isolation is not supported by the supplied exploitation evidence.
Technical view
nf_hook_run_bpf() used bpf_prog_run() in a context that could migrate between CPUs. This violated __bpf_prog_run() assumptions and triggered a kernel diagnostic. The fix changes execution to bpf_prog_run_pin_on_cpu(), keeping the BPF program on one CPU while it runs.
Likely exposure
Exposure requires a Linux kernel containing the vulnerable implementation and use of netfilter BPF hooks in the network transmit path. The bundle lists affected version identifiers, but their boundaries are ambiguous; confirm applicability against the running distribution kernel and its backported patches.
Exploitation context
The supplied CVSS is 7.8 with local access and low privileges required. The bundle marks KEV false and provides no evidence of active exploitation or a public exploit. The documented trigger came from syzbot and produced an assertion failure; real-world exploitability beyond that evidence is not established.
Researcher notes
The evidence establishes an execution-context invariant violation, not a demonstrated privilege-escalation chain. Analysis should focus on affected-code reachability, distribution backports, and whether assertion behavior becomes denial of service or memory-safety impact in production configurations. The bundle provides no CWE classification or detailed affected-version ranges.
Mitigation direction
Upgrade to a vendor-supported kernel containing the applicable listed stable fix.
Check distribution advisories because vendor kernel versions may include backported patches.
Prioritize systems using netfilter BPF hooks or permitting low-privileged local access.
Restrict unnecessary local accounts and privileged BPF capabilities until patch status is confirmed.
Validation and detection
Record each system's kernel release, package revision, and distribution build.
Confirm whether the vendor kernel includes an applicable referenced stable commit.
Identify hosts using netfilter BPF programs in network transmission paths.
After upgrading, verify the new kernel is running and repeat normal network workload tests.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-38640 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
6Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.