CyberSecBulletin
CVE-2026-68479NVD status: Received

Linux: Integer Overflow or Wraparound

Published Updated By the CyberSecBulletin desk

CVE-2026-68479 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 39e01b4addfbbe177567d6ed1dfb81f9cccb19e6, bda3c598ade6ea03884074b91e31608326684921, a4cb830e0b55ac76c849fd7840afb251f4c028fa 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.17% 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 39e01b4addfbbe177567d6ed1dfb81f9cccb19e6 or bda3c598ade6ea03884074b91e31608326684921 or a4cb830e0b55ac76c849fd7840afb251f4c028fa or 68c5a2a19987c035eb129e627e579adafb04f637, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinuxdb33c77dddc2ed2cff3061d0b096a9f5ab0c3647 up to, but not including, 39e01b4addfbbe177567d6ed1dfb81f9cccb19e6; db33c77dddc2ed2cff3061d0b096a9f5ab0c3647 up to, but not including, bda3c598ade6ea03884074b91e31608326684921; db33c77dddc2ed2cff3061d0b096a9f5ab0c3647 up to, but not including, a4cb830e0b55ac76c849fd7840afb251f4c028fa; db33c77dddc2ed2cff3061d0b096a9f5ab0c3647 up to, but not including, 68c5a2a19987c035eb129e627e579adafb04f637; db33c77dddc2ed2cff3061d0b096a9f5ab0c3647 up to, but not including, 83534891c058ed71e251135072640911670869aa; db33c77dddc2ed2cff3061d0b096a9f5ab0c3647 up to, but not including, 6744ab60dfac55d1df5733960aad5be300984301; db33c77dddc2ed2cff3061d0b096a9f5ab0c3647 up to, but not including, f1ca750c0510bdbb504bf084d2f196ef2af92ea6; db33c77dddc2ed2cff3061d0b096a9f5ab0c3647 up to, but not including, 609c5b04a28dc1b0f3af6a7bc93055135b2d2059; and 1 more ranges39e01b4addfbbe177567d6ed1dfb81f9cccb19e6, bda3c598ade6ea03884074b91e31608326684921, a4cb830e0b55ac76c849fd7840afb251f4c028fa, 68c5a2a19987c035eb129e627e579adafb04f637, 83534891c058ed71e251135072640911670869aa, 6744ab60dfac55d1df5733960aad5be300984301

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: Bluetooth: btrtl: validate firmware patch bounds rtlbt_parse_firmware() copies patch_length - 4 bytes before appending the firmware version. A malformed firmware patch shorter than the version field can make this subtraction underflow and turn the copy into an oversized read and write during Bluetooth setup. The existing patch_offset + patch_length check can also wrap on 32-bit architectures. Validate the patch length and range without arithmetic overflow before allocating or copying the patch.

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.