CVE-2025-22048
What it is
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).
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 7.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Record status
- Modified
Affected
- Linux Kernel < 6.2
- Linux Kernel < 6.6.87
- Linux Kernel < 6.12
- Linux Kernel < 6.12.23
- Linux Kernel < 6.13.11
- Linux Kernel < 6.14.2
Attack profile CVSS 3.1 · 7.8
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2025-22048.md and follow it. Check whether this project is affected by CVE-2025-22048. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/223d565d8892481684091cfbaf3466f2b0e289d3
- https://git.kernel.org/stable/c/60f3caff1492e5b8616b9578c4bedb5c0a88ed14
- https://git.kernel.org/stable/c/780628a780b622759d9e5adc76d15432144da1a3
- https://git.kernel.org/stable/c/7df2696256a034405d3c5a71b3a4c54725de4404
- https://git.kernel.org/stable/c/996e90ab446641553e8e21707b38b9709605e0e0
References
- https://git.kernel.org/stable/c/223d565d8892481684091cfbaf3466f2b0e289d3
- https://git.kernel.org/stable/c/60f3caff1492e5b8616b9578c4bedb5c0a88ed14
- https://git.kernel.org/stable/c/780628a780b622759d9e5adc76d15432144da1a3
- https://git.kernel.org/stable/c/7df2696256a034405d3c5a71b3a4c54725de4404
- https://git.kernel.org/stable/c/996e90ab446641553e8e21707b38b9709605e0e0
- https://git.kernel.org/stable/c/d99845f672cce0b610f7c51248ef95d7df63927e