CVE-2026-99675: nvmet: reject keep-alive timeouts that would overflow
In the Linux kernel, the following vulnerability has been resolved:
nvmet: reject keep-alive timeouts that would overflow
nvmetsetfeatkato() and nvmetallocctrl() convert the 32-bit millisecond KATO from the host to seconds with DIVROUNDUP(kato, 1000). The addition in DIVROUNDUP() 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 MAXJIFFYOFFSET.
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.64 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.5 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.3.5-1 - Compensating control
In nvmet, validate KATO values from both Connect and Set Features before changing the current timer. Perform DIV_ROUND_UP() rounding in 64 bits, reject values whose converted timeout would overflow any consumer or exceed MAX_JIFFY_OFFSET, and leave the existing timer unchanged if validation fails.
Event History
Frequently Asked Questions
Who can trigger the vulnerable behavior?
A host that can send NVMe-oF Connect or Set Features commands to an nvmet target can supply an oversized keep-alive timeout value. The affected input is the 32-bit millisecond KATO provided by the host.
What happens when an oversized keep-alive timeout is accepted?
Values above 4294966296 ms can wrap during conversion to seconds and become 0. A Set Features request with KATO 0xffffffff can disable the keep-alive timer, while a Connect request can create a controller without one.
How does the fix change request handling?
The fix rejects KATO values whose rounded value cannot safely fit the required timer and conversion paths, returning Keep Alive Timeout Invalid for both Set Features and Connect. Failed Set Features updates are validated before the current timer is stopped, so the existing timeout remains unchanged.
Is a keep-alive timeout of zero rejected?
No. A KATO of 0 retains its existing meaning.