UBUNTU-CVE-2026-99016: High severity ubuntu/linux-hwe-edge vulnerability

Q: Which systems are exposed to this issue?

Exposure requires a RISC-V system using the tagged address ABI, with CONFIG_RISCV_ISA_SUPM enabled and a process using PR_SET_TAGGED_ADDR_CTRL with a nonzero PMLEN. The described kernel-address overlap scenario specifically uses Sv57 with PMLEN=16.

Q: What does an attacker need to exploit it?

An attacker needs local code execution as an unprivileged process and must be able to issue FUTEX_WAKE_OP operations using a tagged user pointer. The vulnerable atomic futex operations can then act on the raw tagged address rather than the address validated by access_ok().

Q: How can administrators determine whether the relevant feature is in use?

Check whether the kernel is built with CONFIG_RISCV_ISA_SUPM and whether processes enable tagged addresses through PR_SET_TAGGED_ADDR_CTRL with PMLEN set to a nonzero value. The higher-risk address construction described in the advisory depends on Sv57 with PMLEN=16.

Published Oct 23, 2026

Updated

In the Linux kernel, the following vulnerability has been resolved: riscv: futex: untag the user pointer before the atomic access accessok() checks untaggedaddr(uaddr), but archfutexatomicopinuser() and futexatomiccmpxchginatomic() hand the raw uaddr to the inline asm amoswap/amoadd/.../lr.w+sc.w through the "+m" (uaddr) operand. When the tagged address ABI is enabled (CONFIGRISCVISASUPM, prctl PRSETTAGGEDADDRCTRL with PMLEN != 0), those two addresses differ: a user pointer whose top PMLEN bits hold a tag passes accessok() after untagging, but the atomic is then performed on the still-tagged raw address. Supervisor-mode data accesses are not subject to the U-mode pointer masking (that is governed by menvcfg.PMM, which the kernel does not set), so hardware does not strip the tag for the kernel's own access. With Sv57 and PMLEN=16 the tag bits overlap the canonical-address bits, so a tagged pointer can name a canonical kernel virtual address (e.g. in the linear map) whose untagged form is a valid user address. An unprivileged process can thus make FUTEXWAKEOP perform an atomic read-modify-write on an arbitrary kernel address, with the matching FUTEXOPCMP result serving as a read oracle. getuser()/putuser()/rawcopy{to,from}user() already untag the pointer after the accessok() check; do the same in the futex helpers so the atomic operates on the address that was actually validated.

Affected Software

138 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.8*

ubuntu/linux-azure-5.11*

ubuntu/linux-azure-5.13*

ubuntu/linux-azure-5.8*

ubuntu/linux-azure-fde*

ubuntu/linux-gcp-5.11*

ubuntu/linux-gcp-5.13*

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.8*

ubuntu/linux-intel-5.13*

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.8*

ubuntu/linux-raspi2*

ubuntu/linux-riscv*

ubuntu/linux-riscv-5.11*

ubuntu/linux-riscv-5.8*

ubuntu/linux-allwinner-5.19*

ubuntu/linux-aws-5.19*

ubuntu/linux-aws-6.2*

ubuntu/linux-aws-6.5*

ubuntu/linux-azure-5.19*

ubuntu/linux-azure-6.2*

ubuntu/linux-azure-6.5*

ubuntu/linux-azure-fde-5.19*

ubuntu/linux-azure-fde-6.2*

ubuntu/linux-gcp-5.19*

ubuntu/linux-gcp-6.2*

ubuntu/linux-gcp-6.5*

ubuntu/linux-hwe-5.19*

ubuntu/linux-hwe-6.2*

ubuntu/linux-hwe-6.5*

ubuntu/linux-intel-iot-realtime*

ubuntu/linux-lowlatency-hwe-5.19*

ubuntu/linux-lowlatency-hwe-6.2*

ubuntu/linux-lowlatency-hwe-6.5*

ubuntu/linux-nvidia-6.2*

ubuntu/linux-nvidia-6.5*

ubuntu/linux-oem-5.17*

ubuntu/linux-oem-6.0*

ubuntu/linux-oem-6.1*

ubuntu/linux-oem-6.5*

ubuntu/linux-oracle-6.5*

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-aws-6.14*

ubuntu/linux-aws-6.17*

ubuntu/linux-aws-7.0<7.0.0-1017.18~24.04.1

7.0.0-1017.18~24.04.1

ubuntu/linux-azure-6.11*

ubuntu/linux-azure-6.14*

ubuntu/linux-azure-6.17*

ubuntu/linux-azure-7.0*

ubuntu/linux-azure-fde-6.14*

ubuntu/linux-azure-fde-6.17*

ubuntu/linux-azure-fde-7.0<7.0.0-1019.19~24.04.1

7.0.0-1019.19~24.04.1

ubuntu/linux-azure-nvidia-6.14*

ubuntu/linux-gcp-6.11*

ubuntu/linux-gcp-6.14*

ubuntu/linux-gcp-7.0<7.0.0-1017.19~24.04.1

7.0.0-1017.19~24.04.1

ubuntu/linux-hwe-6.11*

ubuntu/linux-hwe-6.14*

ubuntu/linux-hwe-6.17*

ubuntu/linux-hwe-7.0*

ubuntu/linux-lowlatency-hwe-6.11*

ubuntu/linux-nvidia-6.11*

ubuntu/linux-nvidia-6.17*

ubuntu/linux-nvidia-7.0*

ubuntu/linux-oem-6.11*

ubuntu/linux-oem-6.14*

ubuntu/linux-oem-6.17*

ubuntu/linux-oem-6.8*

ubuntu/linux-oracle-6.14*

ubuntu/linux-oracle-6.17*

ubuntu/linux-oracle-7.0<7.0.0-1016.18~24.04.1

7.0.0-1016.18~24.04.1

ubuntu/linux-raspi-realtime*

ubuntu/linux-realtime*

ubuntu/linux-riscv*

ubuntu/linux-riscv-6.14*

ubuntu/linux-riscv-6.17*

ubuntu/linux-riscv-7.0<7.0.0-43.43.1~24.04.2

7.0.0-43.43.1~24.04.2

ubuntu/linux-realtime-6.14*

ubuntu/linux-realtime-6.17*

ubuntu/linux<7.3.0-10.10

7.3.0-10.10

ubuntu/linux-aws<7.3.0-1004.4

7.3.0-1004.4

ubuntu/linux-azure<7.3.0-1004.4

7.3.0-1004.4

ubuntu/linux-azure-fde<7.3.0-1004.5

7.3.0-1004.5

ubuntu/linux-gcp<7.3.0-1004.4

7.3.0-1004.4

ubuntu/linux-oracle<7.3.0-1004.4

7.3.0-1004.4

ubuntu/linux-raspi<7.3.0-1004.4

7.3.0-1004.4

ubuntu/linux-realtime<7.3.0-10.10.1

7.3.0-10.10.1

ubuntu/linux-riscv<7.3.0-10.10.1

7.3.0-10.10.1

ubuntu/linux<7.0.0-43.43

7.0.0-43.43

ubuntu/linux-aws<7.0.0-1017.18

7.0.0-1017.18

ubuntu/linux-azure<7.0.0-1020.21

7.0.0-1020.21

ubuntu/linux-azure-fde<7.0.0-1019.19

7.0.0-1019.19

ubuntu/linux-gcp<7.0.0-1017.19

7.0.0-1017.19

ubuntu/linux-gke<7.0.0-1010.11

7.0.0-1010.11

ubuntu/linux-ibm<7.0.0-1018.18

7.0.0-1018.18

ubuntu/linux-nvidia*

ubuntu/linux-nvidia-bos*

ubuntu/linux-oem-7.0<7.0.0-1018.18

7.0.0-1018.18

ubuntu/linux-oracle<7.0.0-1016.18

7.0.0-1016.18

ubuntu/linux-raspi*

ubuntu/linux-realtime<7.0.0-43.43.1

7.0.0-43.43.1

ubuntu/linux-riscv*

ubuntu/linux-vmware*

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade ubuntu/linux-aws-7.0 to a version that resolves this vulnerability.
Fixed in 7.0.0-1017.18~24.04.1
Upgrade
Upgrade ubuntu/linux-azure-fde-7.0 to a version that resolves this vulnerability.
Fixed in 7.0.0-1019.19~24.04.1
Upgrade
Upgrade ubuntu/linux-gcp-7.0 to a version that resolves this vulnerability.
Fixed in 7.0.0-1017.19~24.04.1
Upgrade
Upgrade ubuntu/linux-oracle-7.0 to a version that resolves this vulnerability.
Fixed in 7.0.0-1016.18~24.04.1
Upgrade
Upgrade ubuntu/linux-riscv-7.0 to a version that resolves this vulnerability.
Fixed in 7.0.0-43.43.1~24.04.2
Upgrade
Upgrade ubuntu/linux to a version that resolves this vulnerability.
Fixed in 7.3.0-10.10
Upgrade
Upgrade ubuntu/linux-aws to a version that resolves this vulnerability.
Fixed in 7.3.0-1004.4
Upgrade
Upgrade ubuntu/linux-azure to a version that resolves this vulnerability.
Fixed in 7.3.0-1004.4
Upgrade
Upgrade ubuntu/linux-azure-fde to a version that resolves this vulnerability.
Fixed in 7.3.0-1004.5
Upgrade
Upgrade ubuntu/linux-gcp to a version that resolves this vulnerability.
Fixed in 7.3.0-1004.4
Upgrade
Upgrade ubuntu/linux-oracle to a version that resolves this vulnerability.
Fixed in 7.3.0-1004.4
Upgrade
Upgrade ubuntu/linux-raspi to a version that resolves this vulnerability.
Fixed in 7.3.0-1004.4
Upgrade
Upgrade ubuntu/linux-realtime to a version that resolves this vulnerability.
Fixed in 7.3.0-10.10.1
Upgrade
Upgrade ubuntu/linux-riscv to a version that resolves this vulnerability.
Fixed in 7.3.0-10.10.1
Upgrade
Upgrade ubuntu/linux to a version that resolves this vulnerability.
Fixed in 7.0.0-43.43
Upgrade
Upgrade ubuntu/linux-aws to a version that resolves this vulnerability.
Fixed in 7.0.0-1017.18
Upgrade
Upgrade ubuntu/linux-azure to a version that resolves this vulnerability.
Fixed in 7.0.0-1020.21
Upgrade
Upgrade ubuntu/linux-azure-fde to a version that resolves this vulnerability.
Fixed in 7.0.0-1019.19
Upgrade
Upgrade ubuntu/linux-gcp to a version that resolves this vulnerability.
Fixed in 7.0.0-1017.19
Upgrade
Upgrade ubuntu/linux-gke to a version that resolves this vulnerability.
Fixed in 7.0.0-1010.11
Upgrade
Upgrade ubuntu/linux-ibm to a version that resolves this vulnerability.
Fixed in 7.0.0-1018.18
Upgrade
Upgrade ubuntu/linux-oem-7.0 to a version that resolves this vulnerability.
Fixed in 7.0.0-1018.18
Upgrade
Upgrade ubuntu/linux-oracle to a version that resolves this vulnerability.
Fixed in 7.0.0-1016.18
Upgrade
Upgrade ubuntu/linux-realtime to a version that resolves this vulnerability.
Fixed in 7.0.0-43.43.1
Compensating control
Update the RISC-V futex helpers so they untag the user pointer after the access_ok() check and before the atomic access, including arch_futex_atomic_op_inuser() and futex_atomic_cmpxchg_inatomic(), ensuring the atomic operates on the validated untagged address.

Event History

Oct 23, 2026

CVE Published

via OSV·01:17 PM

Data Sourced

via OSV·01:17 PM

DescriptionSeverityAffected Software

Frequently Asked Questions

Which systems are exposed to this issue?

Exposure requires a RISC-V system using the tagged address ABI, with CONFIG_RISCV_ISA_SUPM enabled and a process using PR_SET_TAGGED_ADDR_CTRL with a nonzero PMLEN. The described kernel-address overlap scenario specifically uses Sv57 with PMLEN=16.

What does an attacker need to exploit it?

An attacker needs local code execution as an unprivileged process and must be able to issue FUTEX_WAKE_OP operations using a tagged user pointer. The vulnerable atomic futex operations can then act on the raw tagged address rather than the address validated by access_ok().

How can administrators determine whether the relevant feature is in use?

Check whether the kernel is built with CONFIG_RISCV_ISA_SUPM and whether processes enable tagged addresses through PR_SET_TAGGED_ADDR_CTRL with PMLEN set to a nonzero value. The higher-risk address construction described in the advisory depends on Sv57 with PMLEN=16.

UBUNTU-CVE-2026-99016: High severity ubuntu/linux-hwe-edge vulnerability

Affected Software

Remediation

Event History

Frequently Asked Questions

Which systems are exposed to this issue?

What does an attacker need to exploit it?

How can administrators determine whether the relevant feature is in use?

Company

Resources

Contact

Frequently Asked Questions

Which systems are exposed to this issue?

What does an attacker need to exploit it?

How can administrators determine whether the relevant feature is in use?