Answer in brief
CVE-2025-22048 records a Unknown severity vulnerability in LoongArch: BPF: Don't override subprog's return value. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=0c8d50501bc13cacecc19caaddc10db372592a39 <7df2696256a034405d3c5a71b3a4c54725de4404 || >=d5d83242a1d778ceb6d8b07c6b491cf7483ca112 <223d565d8892481684091cfbaf3466f2b0e289d3 || >=73c359d1d356cf10236ccd358bd55edab33e9424 <780628a780b622759d9e5adc76d15432144da1a3 || >=73c359d1d356cf10236ccd358bd55edab33e9424 <996e90ab446641553e8e21707b38b9709605e0e0 || >=73c359d1d356cf10236ccd358bd55edab33e9424 <60f3caff1492e5b8616b9578c4bedb5c0a88ed14 || 8382e92f90b601acf6d426121e6f4991502e767d || 3b75f627b73d96787a493e2f1187543ba9c056a4 || >=6.6.64 <6.6.87 || >=6.12.2 <6.12.23 || >=6.1.120 <6.2 || >=6.11.11 <6.12 | 7df2696256a034405d3c5a71b3a4c54725de4404, 223d565d8892481684091cfbaf3466f2b0e289d3, 780628a780b622759d9e5adc76d15432144da1a3, 996e90ab446641553e8e21707b38b9709605e0e0, 60f3caff1492e5b8616b9578c4bedb5c0a88ed14, 6.6.87, 6.12.23, 6.2, 6.12 |
| Linux/Linuxgeneric | 6.13 | Not reported |
Published upstream
Apr 16, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: LoongArch: BPF: Don't override subprog's return value The verifier test `calls: div by 0 in subprog` triggers a panic at the ld.bu instruction. The ld.bu insn is trying to load byte from memory address returned by the subprog. The subprog actually set the correct address at the a5 register (dedicated register for BPF return values). But at commit 73c359d1d356 ("LoongArch: BPF: Sign-extend return values") we also sign extended a5 to the a0 register (return value in LoongArch). For function call insn, we later propagate the a0 register back to a5 register. This is right for native calls but wrong for bpf2bpf calls which expect zero-extended return value in a5 register. So only move a0 to a5 for native calls (i.e. non-BPF_PSEUDO_CALL).
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2025-22048 records a Unknown severity vulnerability in LoongArch: BPF: Don't override subprog's return value. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=0c8d50501bc13cacecc19caaddc10db372592a39 <7df2696256a034405d3c5a71b3a4c54725de4404 || >=d5d83242a1d778ceb6d8b07c6b491cf7483ca112 <223d565d8892481684091cfbaf3466f2b0e289d3 || >=73c359d1d356cf10236ccd358bd55edab33e9424 <780628a780b622759d9e5adc76d15432144da1a3 || >=73c359d1d356cf10236ccd358bd55edab33e9424 <996e90ab446641553e8e21707b38b9709605e0e0 || >=73c359d1d356cf10236ccd358bd55edab33e9424 <60f3caff1492e5b8616b9578c4bedb5c0a88ed14 || 8382e92f90b601acf6d426121e6f4991502e767d || 3b75f627b73d96787a493e2f1187543ba9c056a4 || >=6.6.64 <6.6.87 || >=6.12.2 <6.12.23 || >=6.1.120 <6.2 || >=6.11.11 <6.12 | 7df2696256a034405d3c5a71b3a4c54725de4404, 223d565d8892481684091cfbaf3466f2b0e289d3, 780628a780b622759d9e5adc76d15432144da1a3, 996e90ab446641553e8e21707b38b9709605e0e0, 60f3caff1492e5b8616b9578c4bedb5c0a88ed14, 6.6.87, 6.12.23, 6.2, 6.12 |
| Linux/Linuxgeneric | 6.13 | Not reported |
Published upstream
Apr 16, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: LoongArch: BPF: Don't override subprog's return value The verifier test `calls: div by 0 in subprog` triggers a panic at the ld.bu instruction. The ld.bu insn is trying to load byte from memory address returned by the subprog. The subprog actually set the correct address at the a5 register (dedicated register for BPF return values). But at commit 73c359d1d356 ("LoongArch: BPF: Sign-extend return values") we also sign extended a5 to the a0 register (return value in LoongArch). For function call insn, we later propagate the a0 register back to a5 register. This is right for native calls but wrong for bpf2bpf calls which expect zero-extended return value in a5 register. So only move a0 to a5 for native calls (i.e. non-BPF_PSEUDO_CALL).
Quoted source text, attributed separately from HOL analysis.