In the Linux kernel, the following vulnerability has been resolved: powerpc/bpf: Fix detecting BPF atomic instructions Commit 91c960b0056672 ("bpf: Rename BPF_XADD and prepare to encode other atomics in .imm") converted BPF_XADD to BPF_ATOMIC and added a way to distinguish instructions based on the immediate field. Existing JIT implementations were updated to check for the immediate field and to reject programs utilizing anything more than BPF_ADD (such as BPF_FETCH) in the immediate field. However, the check added to powerpc64 JIT did not look at the correct BPF instruction. Due to this, such programs would be accepted and incorrectly JIT'ed resulting in soft lockups, as seen with the atomic bounds test. Fix this by looking at the correct immediate value.
Update Linux/Linux to 7284dab07e4d51d453cc42851fae9ec4fac6ef2f if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanpowerpc/bpf: Fix detecting BPF atomic instructions affects Linux/Linux (generic), Linux/Linux (generic). Severity is high. In the Linux kernel, the following vulnerability has been resolved: powerpc/bpf: Fix detecting BPF atomic instructions Commit 91c960b0056672 ("bpf: Rename BPF_XADD and prepare to encode other atomics in .imm") converted BPF_XADD to BPF_ATOMIC and added a way to distinguish instructions based on the immediate field. Existing JIT implementations were updated to check for the immediate field and to reject programs utilizing anything more than BPF_ADD (such as BPF_FETCH) in the immediate field. However, the check added to powerpc64 JIT did not look at the correct BPF instruction. Due to this, such programs would be accepted and incorrectly JIT'ed resulting in soft lockups, as seen with the atomic bounds test. Fix this by looking at the correct immediate value.
AI coding agents often install or upgrade packages automatically in generic. A high vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|
In the Linux kernel, the following vulnerability has been resolved: powerpc/bpf: Fix detecting BPF atomic instructions Commit 91c960b0056672 ("bpf: Rename BPF_XADD and prepare to encode other atomics in .imm") converted BPF_XADD to BPF_ATOMIC and added a way to distinguish instructions based on the immediate field. Existing JIT implementations were updated to check for the immediate field and to reject programs utilizing anything more than BPF_ADD (such as BPF_FETCH) in the immediate field. However, the check added to powerpc64 JIT did not look at the correct BPF instruction. Due to this, such programs would be accepted and incorrectly JIT'ed resulting in soft lockups, as seen with the atomic bounds test. Fix this by looking at the correct immediate value.
Update Linux/Linux to 7284dab07e4d51d453cc42851fae9ec4fac6ef2f if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanpowerpc/bpf: Fix detecting BPF atomic instructions affects Linux/Linux (generic), Linux/Linux (generic). Severity is high. In the Linux kernel, the following vulnerability has been resolved: powerpc/bpf: Fix detecting BPF atomic instructions Commit 91c960b0056672 ("bpf: Rename BPF_XADD and prepare to encode other atomics in .imm") converted BPF_XADD to BPF_ATOMIC and added a way to distinguish instructions based on the immediate field. Existing JIT implementations were updated to check for the immediate field and to reject programs utilizing anything more than BPF_ADD (such as BPF_FETCH) in the immediate field. However, the check added to powerpc64 JIT did not look at the correct BPF instruction. Due to this, such programs would be accepted and incorrectly JIT'ed resulting in soft lockups, as seen with the atomic bounds test. Fix this by looking at the correct immediate value.
AI coding agents often install or upgrade packages automatically in generic. A high vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|
| Linux/Linuxgeneric | >=91c960b0056672e74627776655c926388350fa30 <7284dab07e4d51d453cc42851fae9ec4fac6ef2f || >=91c960b0056672e74627776655c926388350fa30 <0d435b6d94b05dcfd836d758a63145aa566618e2 || >=91c960b0056672e74627776655c926388350fa30 <419ac821766cbdb9fd85872bb3f1a589df05c94c | 7284dab07e4d51d453cc42851fae9ec4fac6ef2f, 0d435b6d94b05dcfd836d758a63145aa566618e2, 419ac821766cbdb9fd85872bb3f1a589df05c94c |
|---|
| Linux/Linuxgeneric | 5.12 | Not reported |
|---|
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by CVE List V5 (cvelist).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard| Linux/Linuxgeneric | >=91c960b0056672e74627776655c926388350fa30 <7284dab07e4d51d453cc42851fae9ec4fac6ef2f || >=91c960b0056672e74627776655c926388350fa30 <0d435b6d94b05dcfd836d758a63145aa566618e2 || >=91c960b0056672e74627776655c926388350fa30 <419ac821766cbdb9fd85872bb3f1a589df05c94c | 7284dab07e4d51d453cc42851fae9ec4fac6ef2f, 0d435b6d94b05dcfd836d758a63145aa566618e2, 419ac821766cbdb9fd85872bb3f1a589df05c94c |
|---|
| Linux/Linuxgeneric | 5.12 | Not reported |
|---|
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by CVE List V5 (cvelist).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard