CVE-2026-99283
Low 3.7No known exploitationFix availablenetfilter: conntrack: tcp: use UNACK timeout for non-closing RST packets
Record last updated
CVSS score
Low on a 0 to 10 scale
EPSS, chance of exploitation in 30 days
Higher than 11% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
Description
In the Linux kernel, the following vulnerability has been resolved: netfilter: conntrack: tcp: use UNACK timeout for non-closing RST packets Commit be0502a3f2e9 ("netfilter: conntrack: tcp: only close if RST matches exact sequence") keeps an established conntrack entry in ESTABLISHED when an in-window RST does not match the expected sequence number exactly, so the endpoint can validate the RST with a challenge ACK. The timeout selection nevertheless uses the CLOSE timeout for every RST packet. The bug is that timeout selection is based on the packet type, not on the state transition result: even when RST validation keeps new_state in ESTABLISHED, the timeout is still forced to TCP_CONNTRACK_CLOSE. Linux TCP independently rate limits challenge ACKs per socket. A second non-exact RST can therefore arrive after the first challenge ACK has restored the timeout but before the rate limit expires. The second RST lowers the timeout to 10 seconds again while the endpoint suppresses the second challenge ACK, allowing the conntrack entry to expire while both TCP endpoints remain established. Using the ESTABLISHED timeout for such RSTs would avoid this short expiration window, but it could also retain stale entries for the five-day default because conntrack cannot reliably match the endpoint's exact TCP state. Use the UNACK timeout for RST packets that leave the conntrack entry in TCP_CONNTRACK_ESTABLISHED. Exact-match RSTs and accepted RST packet trains still fall through to timeouts[new_state], which preserves the CLOSE timeout when conntrack accepts the RST as closing the flow. This avoids the aggressive 10-second expiration window for non-exact RSTs while preserving the short timeout for RSTs that conntrack accepts as closing the flow.
Patching and mitigation
- Patch status
- Fix available (source: Microsoft MSRC)
- Fix documented (source date)
- Mitigation
- None documented
- Vendor guidance
- msrc.microsoft.com (opens in a new tab)
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| Linux | Linux | from 4.19.34 before 4.20 | 4.20 | CVE Program |
| Linux | Linux | from 5.0.7 before 5.1 | 5.1 | CVE Program |
| Linux | Linux | from be0502a3f2e94211a8809a09ecbc3a017189b8fb before 0c6d33329960b2d884a399196c8403643d8a9de6 | 0c6d33329960b2d884a399196c8403643d8a9de6 | CVE Program |
| Linux | Linux | from be0502a3f2e94211a8809a09ecbc3a017189b8fb before bf80e6802273a900311b44e47c9b1a59c6d2473c | bf80e6802273a900311b44e47c9b1a59c6d2473c | CVE Program |
| Linux | Linux | from be0502a3f2e94211a8809a09ecbc3a017189b8fb before 4d39a039d0b7737f8475c2431f18572b3b186a3b | 4d39a039d0b7737f8475c2431f18572b3b186a3b | CVE Program |
| Linux | Linux | 5.1 | Not documented | CVE Program |
| Linux | Linux | b39898beee9da20b279c3daf073b42045b3d35d6 | Not documented | CVE Program |
| Linux | Linux | ca66f667189c39b9128c1fba5d0be23d933009d9 | Not documented | CVE Program |
| Microsoft | azl3 kernel 6.6.161.1-1 on Azure Linux 3.0 | Not documented | Not documented | Microsoft MSRC |
| Microsoft | azl4 kernel 6.18.57-1.12.azl4 on Azure Linux 4.0 | Not documented | 0:6.18.62-1.1.azl4 | Microsoft MSRC |
| Microsoft | azl4 kernel 6.18.57-1.6.azl4 on Azure Linux 4.0 | Not documented | Not documented | Microsoft MSRC |
| Linux | Linux (unaffected) | from 6.12.117 up to and including 6.12.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 6.18.61 up to and including 6.18.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | 7.3 | Not documented | CVE Program |
| Linux | Linux (unaffected) | all versions before 5.1 | Not documented | CVE Program |
Timeline
Disclosure
CVE record published by Linux
Source: CVE Program (opens in a new tab)
Advisory
Microsoft advisory published
Advisory change
Microsoft advisory revised (2.0): Information published.
Advisory change
Microsoft advisory revised (3.0): Information published.
Advisory change
Microsoft advisory revised (4.0): Information published.
Patch
Fix documented by Microsoft MSRC
Vendor guidance and references
- Microsoft Security Update Guide (opens in a new tab)vendor-advisory
- https://git.kernel.org/stable/c/0c6d33329960b2d884a399196c8403643d8a9de6 (opens in a new tab)
- https://git.kernel.org/stable/c/4d39a039d0b7737f8475c2431f18572b3b186a3b (opens in a new tab)
- https://git.kernel.org/stable/c/bf80e6802273a900311b44e47c9b1a59c6d2473c (opens in a new tab)