Skip to main content
VulnerabilityPublished

CVE-2026-99675: Linux kernel · nvmet: reject keep-alive timeouts that would overflow

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-99675· Medium

Not known to be exploited · fixed in 884b47ced96c01e2689ee45dc42902d888c4b7f2 : update Linux kernel when convenient.

Data as of 20 Nov 2026, 07:34 UTC

Severity
Medium

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 884b47ced96c01e2689ee45dc42902d888c4b7f2, 96ae13f40ce5930cd58c43128e385131476f2a66, 69d4f0ace16c7ff00ff525152aed1383f82b1192

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade Linux kernel to 884b47ced96c01e2689ee45dc42902d888c4b7f2, 96ae13f40ce5930cd58c43128e385131476f2a66 or 69d4f0ace16c7ff00ff525152aed1383f82b1192.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ a07b4970f464f13640e28e16dad6cfa33647cc99, < 884b47ced96c01e2689ee45dc42902d888c4b7f2
Fixed in
  • 884b47ced96c01e2689ee45dc42902d888c4b7f2
LinuxLinuxAffected
  • ≥ a07b4970f464f13640e28e16dad6cfa33647cc99, < 96ae13f40ce5930cd58c43128e385131476f2a66
Fixed in
  • 96ae13f40ce5930cd58c43128e385131476f2a66
LinuxLinuxAffected
  • ≥ a07b4970f464f13640e28e16dad6cfa33647cc99, < 69d4f0ace16c7ff00ff525152aed1383f82b1192
Fixed in
  • 69d4f0ace16c7ff00ff525152aed1383f82b1192
LinuxLinuxAffected
  • =4.8
Fixed in–

Description

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.

References

Community reviews

Loading reviews…