CyberSecBulletin
CVE-2026-53182NVD status: Modified

Linux: Integer Overflow or Wraparound

Published Updated By the CyberSecBulletin desk

CVE-2026-53182 is a high-severity integer overflow or wraparound vulnerability in Linux, with a CVSS 3.1 base score of 7.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 fc0ec2fc02dfe52c5821f36fbccf6a45df43f508, 688fcac7054abc680c0eef753f2bb772cfaf8cf7, 30c3fa80f423613efdda3deca4af52ff7d20e4e2 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 fc0ec2fc02dfe52c5821f36fbccf6a45df43f508 or 688fcac7054abc680c0eef753f2bb772cfaf8cf7 or 30c3fa80f423613efdda3deca4af52ff7d20e4e2 or 265c07c09c837621730d35f02975207a1224bf05, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 6.1.176 or 6.6.143 or 6.12.94 or 6.18.36, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux56189d7bc30531def6b999f27940ee43c6ff2569 up to, but not including, fc0ec2fc02dfe52c5821f36fbccf6a45df43f508; dbbb27e183b1568d5a907ace1cd144b0709ea52a up to, but not including, 688fcac7054abc680c0eef753f2bb772cfaf8cf7; dbbb27e183b1568d5a907ace1cd144b0709ea52a up to, but not including, 30c3fa80f423613efdda3deca4af52ff7d20e4e2; dbbb27e183b1568d5a907ace1cd144b0709ea52a up to, but not including, 265c07c09c837621730d35f02975207a1224bf05; dbbb27e183b1568d5a907ace1cd144b0709ea52a up to, but not including, ecbf3c45add30a0857414e156bdb9c79906f0ff6; dbbb27e183b1568d5a907ace1cd144b0709ea52a up to, but not including, 4cd92957e8f8cc4ebfe8a5d4203c14c592fde6b1; 6.1.160 up to, but not including, 6.1.176; 6.4fc0ec2fc02dfe52c5821f36fbccf6a45df43f508, 688fcac7054abc680c0eef753f2bb772cfaf8cf7, 30c3fa80f423613efdda3deca4af52ff7d20e4e2, 265c07c09c837621730d35f02975207a1224bf05, ecbf3c45add30a0857414e156bdb9c79906f0ff6, 4cd92957e8f8cc4ebfe8a5d4203c14c592fde6b1
LinuxLinux Kernel6.1.160 up to, but not including, 6.1.176; 6.4 up to, but not including, 6.6.143; 6.7 up to, but not including, 6.12.94; 6.13 up to, but not including, 6.18.36; 6.19 up to, but not including, 7.0.13; 7.16.1.176, 6.6.143, 6.12.94, 6.18.36, 7.0.13

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
UnchangedImpact stays within the vulnerable component.
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:U/C:H/I:H/A:H. Scored by CNA.

Official description

In the Linux kernel, the following vulnerability has been resolved: wifi: nl80211: reject oversized EMA RNR lists nl80211_parse_rnr_elems() stores the parsed element count in a u8-backed cfg80211_rnr_elems::cnt field and uses that count to size the flexible array allocation. Reject nested NL80211_ATTR_EMA_RNR_ELEMS input once the count reaches 255, before incrementing it again. This keeps the parser aligned with the data structure it fills and matches the existing bound check used by nl80211_parse_mbssid_elems().

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

The underlying weakness: Integer Overflow or Wraparound

The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.

How developers prevent this class of flaw

  • Ensure that all protocols are strictly defined, such that all out-of-bounds behavior can be identified simply, and require strict conformance to the protocol.
  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. If possible, choose a language or compiler that performs automatic bounds checking.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Use libraries or frameworks that make it easier to handle numbers without unexpected consequences. Examples include safe integer handling packages such as SafeInt (C++) or IntegerLib (C or C++).

More Integer Overflow or Wraparound vulnerabilities (CWE-190)

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 Integer Overflow or Wraparound vulnerabilities

Spotted an error? Tell us.