Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-22048LoongArch: BPF: Don't override subprog's return value

Description

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).

Timeline

  1. ID reserved

    By Linux

  2. · 4 months later

    Published

  3. · 19 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-22048, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.22% · top 87% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 8382e92f90b601acf6d426121e6f4991502e767d – < d99845f672cce0b610f7c51248ef95d7df63927e
    • affected 0c8d50501bc13cacecc19caaddc10db372592a39 – < 7df2696256a034405d3c5a71b3a4c54725de4404
    • affected d5d83242a1d778ceb6d8b07c6b491cf7483ca112 – < 223d565d8892481684091cfbaf3466f2b0e289d3
    • affected 73c359d1d356cf10236ccd358bd55edab33e9424 – < 780628a780b622759d9e5adc76d15432144da1a3
    • affected 73c359d1d356cf10236ccd358bd55edab33e9424 – < 996e90ab446641553e8e21707b38b9709605e0e0
    • affected 73c359d1d356cf10236ccd358bd55edab33e9424 – < 60f3caff1492e5b8616b9578c4bedb5c0a88ed14
    • affected 3b75f627b73d96787a493e2f1187543ba9c056a4
    • affected 6.1.120 – < 6.1.191
    • affected 6.6.64 – < 6.6.87
    • affected 6.12.2 – < 6.12.23
    • affected 6.11.11 – < 6.12
  • Linux · Linux

    • affected 6.13
    • unaffected < 6.13
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.87 – ≤ 6.6.*
    • unaffected 6.12.23 – ≤ 6.12.*
    • unaffected 6.13.11 – ≤ 6.13.*
    • unaffected 6.14.2 – ≤ 6.14.*
    • unaffected 6.15 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-22048 badge
[![CVE-2025-22048](https://cveledger.app/badge/CVE-2025-22048.svg)](https://cveledger.app/cve/CVE-2025-22048)

Record last updated .