CVE-2025-22048: LoongArch: BPF: Don't override subprog's return value
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 223d565d8892481684091cfbaf3466f2b0e289d3, 6.1.191, 6.12.
- Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 5.5.
Low priority for now. Upgrade to Linux Linux 223d565d8892481684091cfbaf3466f2b0e289d3, 6.1.191, 6.12 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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).
- Published
- Apr 16, 2025
- Updated
- Oct 30, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CNA vs NVD score
- NVD
- 5.5
- CNA · Linux
- 7.8
- 2.3 point gap
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.1.120 and later · before 6.2
- linux linux kernel6.6.64 and later · before 6.6.87
- linux linux kernel6.11.11 and later · before 6.12
- linux linux kernel6.12.2 and later · before 6.12.23
- linux linux kernel6.13 and later · before 6.13.11
- linux linux kernel6.14 and later · before 6.14.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3b75f627b73d96787a493e2f1187543ba9c056a4, 6.13affected
- 8382e92f90b601acf6d426121e6f4991502e767d and later · before d99845f672cce0b610f7c51248ef95d7df63927eaffected · git
- 0c8d50501bc13cacecc19caaddc10db372592a39 and later · before 7df2696256a034405d3c5a71b3a4c54725de4404affected · git
- d5d83242a1d778ceb6d8b07c6b491cf7483ca112 and later · before 223d565d8892481684091cfbaf3466f2b0e289d3affected · git
- 73c359d1d356cf10236ccd358bd55edab33e9424 and later · before 780628a780b622759d9e5adc76d15432144da1a3affected · git
- 73c359d1d356cf10236ccd358bd55edab33e9424 and later · before 996e90ab446641553e8e21707b38b9709605e0e0affected · git
- 73c359d1d356cf10236ccd358bd55edab33e9424 and later · before 60f3caff1492e5b8616b9578c4bedb5c0a88ed14affected · git
- 6.1.120 and later · before 6.1.191affected · semver
- 6.6.64 and later · before 6.6.87affected · semver
- 6.12.2 and later · before 6.12.23affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:13 | linux | before 6.12.25-1 | 6.12.25-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-22044Apr 16, 2025 · acpi: nfit: fix narrowing conversion in acpi_nfit_ctl22Monitor
- ← EarlierCVE-2025-22045Apr 16, 2025 · x86/mm: Fix flush_tlb_range() when used for zapping normal PMDs22Monitor
- Later →CVE-2025-22050Apr 16, 2025 · usbnet:fix NPE during rx_complete18Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 223d565d8892481684091cfbaf3466f2b0e289d3 | Vendor (CNA) |
| Linux Linux | 6.1.191 | Vendor (CNA) |
| Linux Linux | 6.12 | Vendor (CNA) |
| Linux Linux | 6.12.23 | Vendor (CNA) |
| Linux Linux | 6.6.87 | Vendor (CNA) |
| Linux Linux | 60f3caff1492e5b8616b9578c4bedb5c0a88ed14 | Vendor (CNA) |
| Linux Linux | 780628a780b622759d9e5adc76d15432144da1a3 | Vendor (CNA) |
| Linux Linux | 7df2696256a034405d3c5a71b3a4c54725de4404 | Vendor (CNA) |
| Linux Linux | 996e90ab446641553e8e21707b38b9709605e0e0 | Vendor (CNA) |
| Linux Linux | d99845f672cce0b610f7c51248ef95d7df63927e | Vendor (CNA) |
| debian:linux | 6.12.25-1 · Debian:13 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/60f3caff1492e5b8616b9578c4bedb5c0a88ed14
- git.kernel.org/stable/c/780628a780b622759d9e5adc76d15432144da1a3
- git.kernel.org/stable/c/7df2696256a034405d3c5a71b3a4c54725de4404
- git.kernel.org/stable/c/996e90ab446641553e8e21707b38b9709605e0e0
- git.kernel.org/stable/c/d99845f672cce0b610f7c51248ef95d7df63927e
Vendor advisories and official records. Exploit/PoC links are deliberately left out.