CVE-2023-53272: net: ena: fix shift-out-of-bounds in exponential backoff
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.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue affects the Amazon ENA network driver. During device reset, an exponential backoff calculation can shift too far and trigger undefined-behavior sanitizer failures, potentially causing a kernel panic. Business risk is strongest for cloud workloads using ENA-backed networking on affected kernels.
Executive priority
Treat as high priority for ENA-dependent production Linux fleets because failure can affect host availability. It is not currently supported as known exploited from the supplied evidence, so prioritize patching by exposure and service criticality.
Technical view
The ENA driver’s reset path can compute an excessive shift exponent in ena_delay_exponential_backoff_us, producing a shift-out-of-bounds condition. The source describes UBSAN reporting an exponent of 32 for a 32-bit unsigned value during ena_fw_reset_device. Stable fixes cap the exponent used for backoff.
Likely exposure
Likely exposure is Linux systems using the Amazon ENA driver, especially EC2-style environments where ENA adapters reset. The source lists Linux kernel affected version ranges and stable fix commits, but does not provide distribution-specific package status.
Exploitation context
No active exploitation is stated in the provided sources, and KEV is false. The CVSS vector indicates local access with low privileges and no user interaction. The public description shows the issue observed during adapter reset, not a remote exploitation workflow.
Researcher notes
The provided CWE entry says CWE-125, but the description centers on shift-out-of-bounds in ENA backoff logic. Avoid assuming remote reachability. Focus validation on kernel branch, ENA driver presence, reset-path logs, and whether stable commit fixes are present.
Mitigation direction
Inventory Linux hosts using the ENA network driver.
Map running kernel versions against vendor advisories and stable fix commits.
Prioritize cloud workloads where ENA resets affect availability.
Apply kernel or distribution updates that include the referenced stable fixes.
If no package fix is available, follow Linux or distribution vendor guidance.
Validation and detection
Check whether hosts load or depend on the ENA driver.
Confirm the running kernel includes one of the referenced stable fixes.
Review kernel logs for UBSAN shift-out-of-bounds reports in ena_com.c.
Validate distribution package advisories before marking systems remediated.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-125: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-125 · source CWE mapping
Out-of-bounds Read
Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.