LoongArch: BPF: Refactor jump offset calculation in tail call
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.6.160, 6.12.114, 6.2, 6.16, 6.17, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: LoongArch: BPF: Refactor jump offset calculation in tail call The old macro-based jmp_offset calculation derives the jump distance from a stale prior-pass code stride, which can lead to wrong branch offsets and soft lockups under extra JIT passes. Fix this by calculating the offset directly on the absolute target: "ctx->offset[insn + 1] - ctx->idx". To avoid a false 16-bit range check abort during size estimation, add a "ctx->image == NULL" guard to inject a safe dummy offset.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 17c010fe45def335fe03a0718935416b04c7f349 · fixed in 50fbc294e4e96246d60cd66f98acf043a362e3a0; From f83d469e16bb1f75991ca67c56786fb2aaa42bea · fixed in 89819868cde78cb2f748533785a46a3430873f20; From cd39d9e6b7e4c58fa77783e7aedf7ada51d02ea3 · fixed in 882b8912b7e92341fdb115ba0e2e5142a28684ff; From cd39d9e6b7e4c58fa77783e7aedf7ada51d02ea3 · fixed in 96f44d493c280ea161569c43d7ed0f3b0815803a; From cd39d9e6b7e4c58fa77783e7aedf7ada51d02ea3 · fixed in 37d545d12f21c4d50612ecaebd7ae1e5bf91b2d8; From 6.6.103 · fixed in 6.6.160; From 6.12.43 · fixed in 6.12.114; From 6.1.149 · fixed in 6.2; From 6.15.11 · fixed in 6.16; From 6.16.2 · fixed in 6.17
- Linux Linux
6.17
- KernelLinux
fixed in 6.6.160; From 6.7.0 · fixed in 6.12.114; From 6.13.0 · fixed in 6.18.51; From 6.17.0 · fixed in 7.2.5