Vulnerability · Published Sep 16, 2025 · Assigned by Linux
CVE-2023-53272net: ena: fix shift-out-of-bounds in exponential backoff
High 7.1
In plain English
A high-severity out-of-bounds read in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 6% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
In the Linux kernel, the following vulnerability has been resolved: net: ena: fix shift-out-of-bounds in exponential backoff The ENA adapters on our instances occasionally reset. Once recently logged a UBSAN failure to console in the process: UBSAN: shift-out-of-bounds in build/linux/drivers/net/ethernet/amazon/ena/ena_com.c:540:13 shift exponent 32 is too large for 32-bit type 'unsigned int' CPU: 28 PID: 70012 Comm: kworker/u72:2 Kdump: loaded not tainted 5.15.117 Hardware name: Amazon EC2 c5d.9xlarge/, BIOS 1.0 10/16/2017 Workqueue: ena ena_fw_reset_device [ena] Call Trace: <TASK> dump_stack_lvl+0x4a/0x63 dump_stack+0x10/0x16 ubsan_epilogue+0x9/0x36 __ubsan_handle_shift_out_of_bounds.cold+0x61/0x10e ? __const_udelay+0x43/0x50 ena_delay_exponential_backoff_us.cold+0x16/0x1e [ena] wait_for_reset_state+0x54/0xa0 [ena] ena_com_dev_reset+0xc8/0x110 [ena] ena_down+0x3fe/0x480 [ena] ena_destroy_device+0xeb/0xf0 [ena] ena_fw_reset_device+0x30/0x50 [ena] process_one_work+0x22b/0x3d0 worker_thread+0x4d/0x3f0 ? process_one_work+0x3d0/0x3d0 kthread+0x12a/0x150 ? set_kthread_struct+0x50/0x50 ret_from_fork+0x22/0x30 </TASK> Apparently, the reset delays are getting so large they can trigger a UBSAN panic. Looking at the code, the current timeout is capped at 5000us. Using a base value of 100us, the current code will overflow after (1<<29). Even at values before 32, this function wraps around, perhaps unintentionally. Cap the value of the exponent used for this backoff at (1<<16) which is larger than currently necessary, but large enough to support bigger values in the future.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.1.52-1 | DEBIAN-CVE-2023-53272 |
| Debian:13 | linux | 6.4.11-1 | DEBIAN-CVE-2023-53272 |
| Debian:14 | linux | 6.4.11-1 | DEBIAN-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux | 5.15.0-86.96 | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1047.52 | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1049.56 | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2023-53272 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1049.56.1 | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1044.52 | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2023-53272 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1044.49 | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1030.35 | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2023-53272 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1040.43 | UBUNTU-CVE-2023-53272 |
| Ubuntu:24.04:LTS | linux-intel | no fix listed | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1043.49 | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1044.49 | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-86.95 | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2023-53272 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1037.37 | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1018.18 | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1005.5 | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2023-53272 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2023-53272 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1045.51 | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1040.43 | UBUNTU-CVE-2023-53272 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2023-53272 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2023-53272 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2023-53272 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1025.29 | UBUNTU-CVE-2023-53272 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 4bb7f4cf60e38a00965d22aa5979ab143193d41f – before 1e760b2d18bf129b3da052c2946c02758e97d15e4bb7f4cf60e38a00965d22aa5979ab143193d41f – before 3e36cc94d6e60a27f27498adf1c71eeba769ab334bb7f4cf60e38a00965d22aa5979ab143193d41f – before 90947ebf8794e3c229fb2e16e37f1bfea6877f144bb7f4cf60e38a00965d22aa5979ab143193d41f – before 0939c264729d4a081ff88efce2ffdf85dc5331e04bb7f4cf60e38a00965d22aa5979ab143193d41f – before 1e9cb763e9bacf0c932aa948f50dcfca6f519a26 |
| Linux | Linux | 5.8 |
Weakness: CWE-125 · Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
References
- https://git.kernel.org/stable/c/1e760b2d18bf129b3da052c2946c02758e97d15e
- https://git.kernel.org/stable/c/3e36cc94d6e60a27f27498adf1c71eeba769ab33
- https://git.kernel.org/stable/c/90947ebf8794e3c229fb2e16e37f1bfea6877f14
- https://git.kernel.org/stable/c/0939c264729d4a081ff88efce2ffdf85dc5331e0
- https://git.kernel.org/stable/c/1e9cb763e9bacf0c932aa948f50dcfca6f519a26