Skip to main content
VulnerabilityPublished Updated

CVE-2026-45988: Linux kernel · rxrpc: Fix re-decryption of RESPONSE packets

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical · fixed in f55b383070170e988e4dec28be2af1714d258521 : patch Linux kernel as a priority.

Data as of 26 Oct 2026, 10:24 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers can reliably automate steps 1–4 of the kill chain
Technical impact
Total control over the software or total information disclosure

CISA SSVC assessment, 2026-10-16.

Patch
Available – fixed in f55b383070170e988e4dec28be2af1714d258521, d61482be4aae1835b78875761206241835a7510e, 0422e7a4883f25101903f3e8105c0808aa5f4ce9 +2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 17926a79320afa9b95df6b977b40cca6d8713cea, < f55b383070170e988e4dec28be2af1714d258521
Fixed in
  • f55b383070170e988e4dec28be2af1714d258521
LinuxLinuxAffected
  • ≥ 17926a79320afa9b95df6b977b40cca6d8713cea, < d61482be4aae1835b78875761206241835a7510e
Fixed in
  • d61482be4aae1835b78875761206241835a7510e
LinuxLinuxAffected
  • ≥ 17926a79320afa9b95df6b977b40cca6d8713cea, < 0422e7a4883f25101903f3e8105c0808aa5f4ce9
Fixed in
  • 0422e7a4883f25101903f3e8105c0808aa5f4ce9
LinuxLinuxAffected
  • ≥ 17926a79320afa9b95df6b977b40cca6d8713cea, < 76cb9a2d252274adfae6e293a292434631a7d472
Fixed in
  • 76cb9a2d252274adfae6e293a292434631a7d472
LinuxLinuxAffected
  • ≥ 17926a79320afa9b95df6b977b40cca6d8713cea, < 7b89868305052b94a91b708c462bc2281fa42a4a
Fixed in
  • 7b89868305052b94a91b708c462bc2281fa42a4a
LinuxLinuxAffected
  • =2.6.22
Fixed in–

Description

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.

References

Community reviews

Loading reviews…