CVE-2025-71270: LoongArch: Enable exception fixup for specific ADE subcode
In the Linux kernel, the following vulnerability has been resolved:
LoongArch: Enable exception fixup for specific ADE subcode
This patch allows the LoongArch BPF JIT to handle recoverable memory
access errors generated by BPF_PROBE_MEM* instructions.
When a BPF program performs memory access operations, the instructions
it executes may trigger ADEM exceptions. The kernel’s built-in BPF
exception table mechanism (EX_TYPE_BPF) will generate corresponding
exception fixup entries in the JIT compilation phase; however, the
architecture-specific trap handling function needs to proactively call
the common fixup routine to achieve exception recovery.
do_ade(): fix EX_TYPE_BPF memory access exceptions for BPF programs,
ensure safe execution.
Relevant test cases: illegal address access tests in module_attach and
subprogs_extable of selftests/bpf.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue affects LoongArch systems where BPF programs can trigger recoverable memory-access exceptions that were not being handled correctly. The published record does not provide a severity score, exploit evidence, or business-impact detail. Treat it as a kernel maintenance item for LoongArch fleets until vendor guidance adds more urgency.
Executive priority
Prioritize for organizations operating LoongArch Linux systems, especially custom kernels or environments using BPF. For most enterprises without LoongArch exposure, business urgency is low. Escalate if a vendor assigns severity, confirms broader impact, or reports exploitation.
Technical view
The LoongArch BPF JIT generated EX_TYPE_BPF exception-table entries for BPF_PROBE_MEM* memory access, but do_ade() did not call the common fixup path for specific ADEM exceptions. The fix enables exception recovery so illegal probe-memory accesses can be handled safely. Kernel BPF selftests module_attach and subprogs_extable are cited as relevant.
Likely exposure
Exposure appears limited to Linux kernels on LoongArch using the BPF JIT. The CVE record lists Linux as affected with version entries including 6.2, 6.6.124, 6.12.70, 6.18.10, and 6.19, but it does not map distribution packages or configurations.
Exploitation context
The provided sources do not report active exploitation, public exploit code, or KEV listing. They describe a correctness and safety fix for BPF exception handling. Practical exploitability and privilege requirements are not established in the source bundle.
Researcher notes
Key evidence is limited to the CVE description and stable kernel commit references. The defect is architecture-specific and tied to BPF JIT exception fixup. No CVSS, CWE, distribution advisory, or exploit status is provided in the supplied bundle.
Mitigation direction
Inventory LoongArch Linux hosts and their running kernel versions.
Review distribution or kernel vendor guidance for fixed packages.
Apply kernel updates containing the referenced stable fixes when available.
Maintain existing controls limiting untrusted BPF use where operationally feasible.
Validation and detection
Confirm whether each LoongArch host runs an affected kernel version.
Check vendor changelogs for the listed stable commit references.
Verify updated kernels are booted after maintenance.
Run relevant BPF regression tests if you build custom kernels.
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-71270 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.
0CVSS vectors
3Timeline events
0ADP providers
5Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Mar 18, 2026, 17:40 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.