CyberSecBulletin
CVE-2026-53053NVD status: Modified

Linux: Incorrect Conversion between Numeric Types

Published Updated By the CyberSecBulletin desk

CVE-2026-53053 is a high-severity incorrect conversion between numeric types vulnerability in Linux, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions 880a2e6c887c8f51870c0a00dfba3c8519178b65, 166a08644aa509e5d27e154d7fa774f4181df9e0, dbd76a537d8cb814e7f5b795ab21ecb7949c821d as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.13% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Linux to 880a2e6c887c8f51870c0a00dfba3c8519178b65 or 166a08644aa509e5d27e154d7fa774f4181df9e0 or dbd76a537d8cb814e7f5b795ab21ecb7949c821d or 20b3c566e2702e5d4d0545be8a97029a2eebcc0e, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 6.12.91 or 6.18.33 or 7.0.10, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux3332364e4ebc0581d133a334645a20fd13b580f1 up to, but not including, 880a2e6c887c8f51870c0a00dfba3c8519178b65; 3332364e4ebc0581d133a334645a20fd13b580f1 up to, but not including, 166a08644aa509e5d27e154d7fa774f4181df9e0; 3332364e4ebc0581d133a334645a20fd13b580f1 up to, but not including, dbd76a537d8cb814e7f5b795ab21ecb7949c821d; 3332364e4ebc0581d133a334645a20fd13b580f1 up to, but not including, 20b3c566e2702e5d4d0545be8a97029a2eebcc0e; 3332364e4ebc0581d133a334645a20fd13b580f1 up to, but not including, dae251ff11d2d2208a029f98923756831cefec46; 3332364e4ebc0581d133a334645a20fd13b580f1 up to, but not including, faad224fe0f0857a04ff2eb3c90f0de57f47d0f3; 1f03a258f20f1699ede29bb40804074db9398a0d; 5.4.17 up to, but not including, 5.5; and 1 more ranges880a2e6c887c8f51870c0a00dfba3c8519178b65, 166a08644aa509e5d27e154d7fa774f4181df9e0, dbd76a537d8cb814e7f5b795ab21ecb7949c821d, 20b3c566e2702e5d4d0545be8a97029a2eebcc0e, dae251ff11d2d2208a029f98923756831cefec46, faad224fe0f0857a04ff2eb3c90f0de57f47d0f3
LinuxLinux Kernel5.4.17 up to, but not including, 6.12.91; 6.13 up to, but not including, 6.18.33; 6.19 up to, but not including, 7.0.106.12.91, 6.18.33, 7.0.10

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
ChangedThe attack can reach beyond the vulnerable component into other systems.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H. Scored by CNA.

Official description

In the Linux kernel, the following vulnerability has been resolved: iommu/amd: Fix clone_alias() to use the original device's devid Currently clone_alias() assumes first argument (pdev) is always the original device pointer. This function is called by pci_for_each_dma_alias() which based on topology decides to send original or alias device details in first argument. This meant that the source devid used to look up and copy the DTE may be incorrect, leading to wrong or stale DTE entries being propagated to alias device. Fix this by passing the original pdev as the opaque data argument to both the direct clone_alias() call and pci_for_each_dma_alias(). Inside clone_alias(), retrieve the original device from data and compute devid from it.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Incorrect Conversion between Numeric Types

When converting from one data type to another, such as long to integer, data can be omitted or translated in a way that produces unexpected values. If the resulting values are used in a sensitive context, then dangerous behaviors may occur.

How developers prevent this class of flaw

  • Avoid making conversion between numeric types. Always check for the allowed ranges.

More Incorrect Conversion between Numeric Types vulnerabilities (CWE-681)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Incorrect Conversion between Numeric Types vulnerabilities

Spotted an error? Tell us.