UBUNTU-CVE-2022-49961: High severity ubuntu/linux-hwe-edge vulnerability

Q: What access would an attacker need to exploit this issue?

The supplied severity vector indicates local access and high privileges are required. Exploitation involves submitting a crafted BPF program that triggers incorrect verifier state pruning.

Q: What could successful exploitation allow?

An invalid BPF program can pass verifier checks and access memory beyond the memory size that should have applied in the explored state. The severity vector rates confidentiality, integrity, and availability impact as high.

Q: Which Ubuntu kernel packages are identified as affected?

The listed packages are ubuntu/linux-riscv, ubuntu/linux-realtime, ubuntu/linux-hwe-edge, ubuntu/linux-azure, ubuntu/linux-gcp, ubuntu/linux-azure-fde, ubuntu/linux-gke, and ubuntu/linux-gkeop.

Published Jun 18, 2025

Updated

In the Linux kernel, the following vulnerability has been resolved: bpf: Do markchainprecision for ARGCONSTALLOCSIZEORZERO Precision markers need to be propagated whenever we have an ARGCONST style argument, as the verifier cannot consider imprecise scalars to be equivalent for the purposes of statesequal check when such arguments refine the return value (in this case, set memsize for PTRTOMEM). The resultant memsize for the R0 is derived from the constant value, and if the verifier incorrectly prunes states considering them equivalent where such arguments exist (by seeing that both registers have reg->precise as false in regsafe), we can end up with invalid programs passing the verifier which can do access beyond what should have been the correct memsize in that explored state. To show a concrete example of the problem: 0000000000000000 <prog>: 0: r2 = (u32 )(r1 + 80) 1: r1 = (u32 )(r1 + 76) 2: r3 = r1 3: r3 += 4 4: if r3 > r2 goto +18 <LBB55> 5: w2 = 0 6: (u32 )(r1 + 0) = r2 7: r1 = (u32 )(r1 + 0) 8: r2 = 1 9: if w1 == 0 goto +1 <LBB53> 10: r2 = -1 0000000000000058 <LBB53>: 11: r1 = 0 ll 13: r3 = 0 14: call bpfringbufreserve 15: if r0 == 0 goto +7 <LBB55> 16: r1 = r0 17: r1 += 16777215 18: w2 = 0 19: (u8 )(r1 + 0) = r2 20: r1 = r0 21: r2 = 0 22: call bpfringbufsubmit 00000000000000b8 <LBB55>: 23: w0 = 0 24: exit For the first case, the single line execution's exploration will prune the search at insn 14 for the branch insn 9's second leg as it will be verified first using r2 = -1 (UINTMAX), while as w1 at insn 9 will always be 0 so at runtime we don't get error for being greater than UINTMAX/4 from bpfringbufreserve. The verifier during regsafe just sees reg->precise as false for both r2 registers in both states, hence considers them equal for purposes of statesequal. If we propagated precise markers using the backtracking support, we would use the precise marking to then ensure that old r2 (UINTMAX) was within the new r2 (1) and this would never be true, so the verification would rightfully fail. The end result is that the out of bounds access at instruction 19 would be permitted without this fix. Note that reg->precise is always set to true when user does not have CAPBPF (or when subprog count is greater than 1 (i.e. use of any static or global functions)), hence this is only a problem when precision marks need to be explicitly propagated (i.e. privileged users with CAPBPF). A simplified test case has been included in the next patch to prevent future regressions.

Affected Software

119 affected componentsFixes available

ubuntu/linux-hwe-edge*

ubuntu/linux-aws-5.0*

ubuntu/linux-aws-5.3*

ubuntu/linux-azure*

ubuntu/linux-azure-5.3*

ubuntu/linux-azure-edge*

ubuntu/linux-gcp*

ubuntu/linux-gcp-5.3*

ubuntu/linux-gke-4.15*

ubuntu/linux-gke-5.4*

ubuntu/linux-gkeop-5.4*

ubuntu/linux-hwe*

ubuntu/linux-hwe-edge*

ubuntu/linux-oem*

ubuntu/linux-oracle-5.0*

ubuntu/linux-oracle-5.3*

ubuntu/linux-aws-5.11*

ubuntu/linux-aws-5.13*

ubuntu/linux-aws-5.15<5.15.0-1112.119~20.04.1

5.15.0-1112.119~20.04.1

ubuntu/linux-aws-5.8*

ubuntu/linux-azure-5.11*

ubuntu/linux-azure-5.13*

ubuntu/linux-azure-5.15<5.15.0-1117.126~20.04.1

5.15.0-1117.126~20.04.1

ubuntu/linux-azure-5.8*

ubuntu/linux-azure-fde*

ubuntu/linux-azure-fde-5.15<5.15.0-1117.126~20.04.2

5.15.0-1117.126~20.04.2

ubuntu/linux-gcp-5.11*

ubuntu/linux-gcp-5.13*

ubuntu/linux-gcp-5.15<5.15.0-1112.122~20.04.1

5.15.0-1112.122~20.04.1

ubuntu/linux-gcp-5.8*

ubuntu/linux-gke*

ubuntu/linux-gke-5.15*

ubuntu/linux-gkeop*

ubuntu/linux-gkeop-5.15*

ubuntu/linux-hwe-5.11*

ubuntu/linux-hwe-5.13*

ubuntu/linux-hwe-5.15<5.15.0-186.196~20.04.1

5.15.0-186.196~20.04.1

ubuntu/linux-hwe-5.8*

ubuntu/linux-ibm-5.15<5.15.0-1106.110~20.04.1

5.15.0-1106.110~20.04.1

ubuntu/linux-intel-5.13*

ubuntu/linux-intel-iotg-5.15<5.15.0-1107.113~20.04.1

5.15.0-1107.113~20.04.1

ubuntu/linux-lowlatency-hwe-5.15<5.15.0-184.194~20.04.1

5.15.0-184.194~20.04.1

ubuntu/linux-nvidia-tegra-5.15<5.15.0-1064.66~20.04.1

5.15.0-1064.66~20.04.1

ubuntu/linux-oem-5.10*

ubuntu/linux-oem-5.13*

ubuntu/linux-oem-5.6*

ubuntu/linux-oracle-5.11*

ubuntu/linux-oracle-5.13*

ubuntu/linux-oracle-5.15<5.15.0-1109.115~20.04.1

5.15.0-1109.115~20.04.1

ubuntu/linux-oracle-5.8*

ubuntu/linux-raspi2*

ubuntu/linux-riscv*

ubuntu/linux-riscv-5.11*

ubuntu/linux-riscv-5.15<5.15.0-1106.110~20.04.1

5.15.0-1106.110~20.04.1

ubuntu/linux-riscv-5.8*

ubuntu/linux<5.15.0-186.196

5.15.0-186.196

ubuntu/linux-allwinner-5.19*

ubuntu/linux-aws<5.15.0-1112.119

5.15.0-1112.119

ubuntu/linux-aws-5.19*

ubuntu/linux-aws-6.2*

ubuntu/linux-aws-6.5*

ubuntu/linux-azure<5.15.0-1117.126

5.15.0-1117.126

ubuntu/linux-azure-5.19*

ubuntu/linux-azure-6.2*

ubuntu/linux-azure-6.5*

ubuntu/linux-azure-fde<5.15.0-1117.126

5.15.0-1117.126

ubuntu/linux-azure-fde-5.19*

ubuntu/linux-azure-fde-6.2*

ubuntu/linux-gcp<5.15.0-1112.122

5.15.0-1112.122

ubuntu/linux-gcp-5.19*

ubuntu/linux-gcp-6.2*

ubuntu/linux-gcp-6.5*

ubuntu/linux-gke<5.15.0-1108.114

5.15.0-1108.114

ubuntu/linux-gkeop<5.15.0-1095.103

5.15.0-1095.103

ubuntu/linux-hwe-5.19*

ubuntu/linux-hwe-6.2*

ubuntu/linux-hwe-6.5*

ubuntu/linux-ibm<5.15.0-1106.110

5.15.0-1106.110

ubuntu/linux-intel-iot-realtime*

ubuntu/linux-intel-iotg<5.15.0-1107.113

5.15.0-1107.113

ubuntu/linux-kvm<5.15.0-1104.109

5.15.0-1104.109

ubuntu/linux-lowlatency<5.15.0-184.194

5.15.0-184.194

ubuntu/linux-lowlatency-hwe-5.19*

ubuntu/linux-lowlatency-hwe-6.2*

ubuntu/linux-lowlatency-hwe-6.5*

ubuntu/linux-nvidia<5.15.0-1107.108

5.15.0-1107.108

ubuntu/linux-nvidia-6.2*

ubuntu/linux-nvidia-6.5*

ubuntu/linux-nvidia-tegra<5.15.0-1064.66

5.15.0-1064.66

ubuntu/linux-nvidia-tegra-igx<5.15.0-1053.53

5.15.0-1053.53

ubuntu/linux-oem-5.17*

ubuntu/linux-oem-6.0*

ubuntu/linux-oem-6.1*

ubuntu/linux-oem-6.5*

ubuntu/linux-oracle<5.15.0-1109.115

5.15.0-1109.115

ubuntu/linux-oracle-6.5*

ubuntu/linux-raspi<5.15.0-1106.109

5.15.0-1106.109

ubuntu/linux-realtime*

ubuntu/linux-riscv*

ubuntu/linux-riscv-5.19*

ubuntu/linux-riscv-6.5*

ubuntu/linux-starfive-5.19*

ubuntu/linux-starfive-6.2*

ubuntu/linux-starfive-6.5*

ubuntu/linux-xilinx-zynqmp<5.15.0-1075.79

5.15.0-1075.79

ubuntu/linux-bluefield<5.15.0-1096.98

5.15.0-1096.98

ubuntu/linux-intel-iot-realtime<5.15.0-1104.106

5.15.0-1104.106

ubuntu/linux-realtime<5.15.0-1111.120

5.15.0-1111.120

ubuntu/linux-aws-fips*

ubuntu/linux-azure-fips*

ubuntu/linux-fips*

ubuntu/linux-gcp-fips*

ubuntu/linux-aws-fips<5.15.0-1112.119+fips1

5.15.0-1112.119+fips1

ubuntu/linux-azure-fips<5.15.0-1117.126+fips1

5.15.0-1117.126+fips1

ubuntu/linux-fips<5.15.0-186.196+fips1

5.15.0-186.196+fips1

ubuntu/linux-gcp-fips<5.15.0-1112.122+fips1

5.15.0-1112.122+fips1

ubuntu/linux-raspi-realtime*

ubuntu/linux-realtime*

ubuntu/linux-riscv*

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade ubuntu/linux-aws-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1112.119~20.04.1
Upgrade
Upgrade ubuntu/linux-azure-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1117.126~20.04.1
Upgrade
Upgrade ubuntu/linux-azure-fde-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1117.126~20.04.2
Upgrade
Upgrade ubuntu/linux-gcp-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1112.122~20.04.1
Upgrade
Upgrade ubuntu/linux-hwe-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-186.196~20.04.1
Upgrade
Upgrade ubuntu/linux-ibm-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1106.110~20.04.1
Upgrade
Upgrade ubuntu/linux-intel-iotg-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1107.113~20.04.1
Upgrade
Upgrade ubuntu/linux-lowlatency-hwe-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-184.194~20.04.1
Upgrade
Upgrade ubuntu/linux-nvidia-tegra-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1064.66~20.04.1
Upgrade
Upgrade ubuntu/linux-oracle-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1109.115~20.04.1
Upgrade
Upgrade ubuntu/linux-riscv-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1106.110~20.04.1
Upgrade
Upgrade ubuntu/linux to a version that resolves this vulnerability.
Fixed in 5.15.0-186.196
Upgrade
Upgrade ubuntu/linux-aws to a version that resolves this vulnerability.
Fixed in 5.15.0-1112.119
Upgrade
Upgrade ubuntu/linux-azure to a version that resolves this vulnerability.
Fixed in 5.15.0-1117.126
Upgrade
Upgrade ubuntu/linux-azure-fde to a version that resolves this vulnerability.
Fixed in 5.15.0-1117.126
Upgrade
Upgrade ubuntu/linux-gcp to a version that resolves this vulnerability.
Fixed in 5.15.0-1112.122
Upgrade
Upgrade ubuntu/linux-gke to a version that resolves this vulnerability.
Fixed in 5.15.0-1108.114
Upgrade
Upgrade ubuntu/linux-gkeop to a version that resolves this vulnerability.
Fixed in 5.15.0-1095.103
Upgrade
Upgrade ubuntu/linux-ibm to a version that resolves this vulnerability.
Fixed in 5.15.0-1106.110
Upgrade
Upgrade ubuntu/linux-intel-iotg to a version that resolves this vulnerability.
Fixed in 5.15.0-1107.113
Upgrade
Upgrade ubuntu/linux-kvm to a version that resolves this vulnerability.
Fixed in 5.15.0-1104.109
Upgrade
Upgrade ubuntu/linux-lowlatency to a version that resolves this vulnerability.
Fixed in 5.15.0-184.194
Upgrade
Upgrade ubuntu/linux-nvidia to a version that resolves this vulnerability.
Fixed in 5.15.0-1107.108
Upgrade
Upgrade ubuntu/linux-nvidia-tegra to a version that resolves this vulnerability.
Fixed in 5.15.0-1064.66
Upgrade
Upgrade ubuntu/linux-nvidia-tegra-igx to a version that resolves this vulnerability.
Fixed in 5.15.0-1053.53
Upgrade
Upgrade ubuntu/linux-oracle to a version that resolves this vulnerability.
Fixed in 5.15.0-1109.115
Upgrade
Upgrade ubuntu/linux-raspi to a version that resolves this vulnerability.
Fixed in 5.15.0-1106.109
Upgrade
Upgrade ubuntu/linux-xilinx-zynqmp to a version that resolves this vulnerability.
Fixed in 5.15.0-1075.79
Upgrade
Upgrade ubuntu/linux-bluefield to a version that resolves this vulnerability.
Fixed in 5.15.0-1096.98
Upgrade
Upgrade ubuntu/linux-intel-iot-realtime to a version that resolves this vulnerability.
Fixed in 5.15.0-1104.106
Upgrade
Upgrade ubuntu/linux-realtime to a version that resolves this vulnerability.
Fixed in 5.15.0-1111.120
Upgrade
Upgrade ubuntu/linux-aws-fips to a version that resolves this vulnerability.
Fixed in 5.15.0-1112.119+fips1
Upgrade
Upgrade ubuntu/linux-azure-fips to a version that resolves this vulnerability.
Fixed in 5.15.0-1117.126+fips1
Upgrade
Upgrade ubuntu/linux-fips to a version that resolves this vulnerability.
Fixed in 5.15.0-186.196+fips1
Upgrade
Upgrade ubuntu/linux-gcp-fips to a version that resolves this vulnerability.
Fixed in 5.15.0-1112.122+fips1

Event History

Jun 18, 2025

CVE Published

via OSV·11:15 AM

Data Sourced

via OSV·11:15 AM

DescriptionSeverityAffected Software

Frequently Asked Questions

What access would an attacker need to exploit this issue?

The supplied severity vector indicates local access and high privileges are required. Exploitation involves submitting a crafted BPF program that triggers incorrect verifier state pruning.

What could successful exploitation allow?

An invalid BPF program can pass verifier checks and access memory beyond the memory size that should have applied in the explored state. The severity vector rates confidentiality, integrity, and availability impact as high.

Which Ubuntu kernel packages are identified as affected?

The listed packages are ubuntu/linux-riscv, ubuntu/linux-realtime, ubuntu/linux-hwe-edge, ubuntu/linux-azure, ubuntu/linux-gcp, ubuntu/linux-azure-fde, ubuntu/linux-gke, and ubuntu/linux-gkeop.

UBUNTU-CVE-2022-49961: High severity ubuntu/linux-hwe-edge vulnerability

Affected Software

Remediation

Event History

Frequently Asked Questions

What access would an attacker need to exploit this issue?

What could successful exploitation allow?

Which Ubuntu kernel packages are identified as affected?

Company

Resources

Contact

Frequently Asked Questions

What access would an attacker need to exploit this issue?

What could successful exploitation allow?

Which Ubuntu kernel packages are identified as affected?