Security readout for executives and security teams
Plain-English summary
A Linux kernel bug on RISC-V can corrupt a pointer returned by a BPF struct_ops program, causing invalid memory access and a kernel panic. The supplied severity is high, but the evidence demonstrates a crash rather than confirmed code execution or real-world attacks.
Executive priority
Prioritize supported RISC-V systems that permit local users or use BPF-based networking. Schedule prompt kernel updates, while treating other architectures as outside the evidence supplied. Escalate immediately if matching kernel crashes appear; current sources do not establish active exploitation.
Technical view
The RISC-V BPF JIT incorrectly handles struct_ops return-value extension. A pointer returned by the documented bpf_fifo_dequeue test is treated as a 32-bit value and sign-extended to 64 bits, producing an invalid address. The referenced stable-kernel commits correct return handling according to the function model and RISC-V ABI.
Likely exposure
Exposure is limited to RISC-V systems running an affected Linux kernel with relevant BPF struct_ops functionality reachable. The bundle lists 6.6, 6.12.53, 6.17.3, and 6.18 among affected version data, but does not clearly define complete ranges. Confirm status with the kernel or distribution vendor.
Exploitation context
The CVSS vector describes a local, low-privileged attack requiring no user interaction. The supplied record is not in KEV and provides no evidence of active exploitation. It documents a reproducible kernel panic during a BPF self-test; confidentiality and integrity impact are scored high but not demonstrated in the description.
Researcher notes
The demonstrated failure occurs when bpf_fifo_dequeue returns an skb pointer that is mishandled by the RISC-V BPF epilogue. The record supplies three stable-tree corrections but lacks clear affected-range semantics, prerequisite analysis, CWE classification, and evidence that exploitation extends beyond denial of service.
Mitigation direction
Apply a vendor-supported kernel update containing the referenced stable-kernel correction.
Map distribution kernel builds to the upstream fix commits before declaring systems remediated.
Restrict unnecessary local access while affected RISC-V systems await updates.
Review vendor guidance before disabling BPF features, because no configuration workaround is documented.
Validation and detection
Inventory RISC-V hosts and record their exact kernel and distribution build versions.
Confirm the installed build includes an applicable referenced stable-kernel fix.
Determine whether BPF struct_ops functionality is enabled or used on affected hosts.
Review kernel logs for paging faults or panics involving BPF, qdisc, or __qdisc_run.
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-40079 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
4Source 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.