Answer in brief
CVE-2026-45988 records a Critical severity (CVSS 9.8) vulnerability in rxrpc: Fix re-decryption of RESPONSE packets. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 9.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=17926a79320afa9b95df6b977b40cca6d8713cea <d61482be4aae1835b78875761206241835a7510e || >=17926a79320afa9b95df6b977b40cca6d8713cea <7b89868305052b94a91b708c462bc2281fa42a4a || >=17926a79320afa9b95df6b977b40cca6d8713cea <76cb9a2d252274adfae6e293a292434631a7d472 || >=17926a79320afa9b95df6b977b40cca6d8713cea <f55b383070170e988e4dec28be2af1714d258521 || >=17926a79320afa9b95df6b977b40cca6d8713cea <0422e7a4883f25101903f3e8105c0808aa5f4ce9 | d61482be4aae1835b78875761206241835a7510e, 7b89868305052b94a91b708c462bc2281fa42a4a, 76cb9a2d252274adfae6e293a292434631a7d472, f55b383070170e988e4dec28be2af1714d258521, 0422e7a4883f25101903f3e8105c0808aa5f4ce9 |
| Linux/Linuxgeneric | 2.6.22 | Not reported |
Published upstream
May 27, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix re-decryption of RESPONSE packets If a RESPONSE packet gets a temporary failure during processing, it may end up in a partially decrypted state - and then get requeued for a retry. Fix this by just discarding the packet; we will send another CHALLENGE packet and thereby elicit a further response. Similarly, discard an incoming CHALLENGE packet if we get an error whilst generating a RESPONSE; the server will send another CHALLENGE.
Quoted source text, attributed separately from HOL analysis.