CVE-2026-99675 in Linux
Summary
by MITRE • 11/20/2026
In the Linux kernel, the following vulnerability has been resolved:
nvmet: reject keep-alive timeouts that would overflow
nvmet_set_feat_kato() and nvmet_alloc_ctrl() convert the 32-bit millisecond KATO from the host to seconds with DIV_ROUND_UP(kato, 1000). The addition in DIV_ROUND_UP() is done in 32 bits, so any KATO above 4294966296 ms wraps around and rounds to 0 seconds. A Set Features command with KATO 0xffffffff then succeeds but disables the keep-alive timer: Get Features returns 0 and Keep Alive fails with Keep Alive Timeout Invalid. A Connect command with such a KATO creates a controller without a keep-alive timer.
The converted value has more consumers that can overflow. Get Features multiplies it by 1000, and the timer paths multiply it by HZ in 32 bits and arm a delay that must not exceed MAX_JIFFY_OFFSET.
Reject a KATO whose rounded value does not fit all of these. Return Keep Alive Timeout Invalid from both Set Features and Connect. Validate Set Features before stopping the current timer so a failed update leaves its timeout unchanged. Round in 64 bits. A KATO of 0 keeps its current meaning.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Analysis
by VulDB Data Team • 11/21/2026
The Linux kernel NVMe target subsystem contains an integer overflow vulnerability within the keep-alive timeout handling logic, specifically affecting the nvmet_set_feat_kato and nvmet_alloc_ctrl functions. This flaw arises from the conversion of a thirty-two-bit millisecond Keep Alive Timeout (KATO) value provided by the host into seconds using the DIV_ROUND_UP macro with a divisor of one thousand. The mathematical operation performed within this macro is executed in thirty-two bits, which creates a critical boundary condition where any KATO value exceeding 4294966296 milliseconds will wrap around due to integer overflow and round down to zero seconds. This behavior allows an attacker or misconfigured host to submit a Set Features command with a maximum unsigned three-bit value of four billion two hundred ninety-four million nine hundred sixty-six thousand eight hundred twenty-seven, which the kernel incorrectly interprets as a timeout of zero.
The operational impact of this vulnerability is significant because it effectively disables the keep-alive mechanism for NVMe controllers managed by the target subsystem. When such an invalid KATO value is processed, subsequent Get Features commands return zero, indicating no timeout period, and any attempt to send Keep Alive messages fails with a Keep Alive Timeout Invalid error code. Furthermore, establishing a connection with this specific KATO configuration results in the creation of a controller instance that lacks a functional keep-alive timer entirely. This disruption compromises the reliability of storage connections, as the target system cannot properly monitor host liveness or enforce timeout policies, potentially leading to resource exhaustion if stale controllers are not cleaned up appropriately by other subsystems relying on these timers.
Beyond the immediate conversion error, the vulnerability extends to downstream consumers that utilize this corrupted value without adequate validation. The Get Features implementation multiplies the already flawed second-based value by one thousand, and internal timer paths multiply it by HZ, which represents the system clock frequency in ticks per second. These multiplications are also performed using thirty-two-bit arithmetic, creating additional opportunities for integer overflow before the delay is armed via standard kernel timer APIs that require values not to exceed MAX_JIFFY_OFFSET. This chain of unchecked operations means that even if the initial conversion were handled correctly, subsequent calculations could still result in undefined behavior or system instability due to wrapping around negative numbers or exceeding maximum allowable jiffy offsets.
To remediate this issue, the kernel developers have implemented strict validation logic that rejects any KATO value whose rounded representation cannot fit within all required downstream constraints. The fix ensures that both Set Features and Connect commands return a Keep Alive Timeout Invalid status when an overflow would occur during conversion or subsequent usage. Crucially, the patch validates the new timeout setting before stopping the current timer to prevent race conditions where a failed update might inadvertently leave the system in an inconsistent state with no active timer. The arithmetic operations are now performed using sixty-four-bit integers to eliminate the possibility of wrapping around at thirty-two bits. This approach maintains backward compatibility by preserving the existing meaning of a KATO value of zero, which typically indicates that keep-alive messages should not be sent or that the timeout is infinite depending on specific NVMe specification interpretations, while strictly enforcing bounds for all other valid inputs to ensure system stability and security compliance with CWE-190 Integer Overflow or Wraparound standards.