CVERadar
HIGH · CVSS 3.1 7.8CISA KEV · added 2026-05-01Metasploit modulePublic PoCEPSS 3.44% (p89)Threat level 55

CVE-2026-31431: Linux Kernel Incorrect Resource Transfer Between Spheres Vulnerability

Linux · Kernel · NVD published 2026-04-22 · posted 2026-05-01 · last modified 2026-09-08

What it is

In the Linux kernel, the following vulnerability has been resolved: crypto: algif_aead - Revert to operating out-of-place This mostly reverts commit 72548b093ee3 except for the copying of the associated data. There is no benefit in operating in-place in algif_aead since the source and destination come from different mappings. Get rid of all the complexity added for in-place operation and just copy the AD directly.

WeaknessCWE-669CWE-1288
CVSS vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67)
CISA due date2026-05-15 (for US federal agencies under BOD; a good deadline for everyone)
ATT&CK tacticsn/a

Exploitation evidence

First exploit evidence seen: 2026-04-22 (earliest date across the sources below).

Exploited in the wild

  • CISA KEV: listed since 2026-05-01. Source

Public exploit code

Metasploit

GitHub proof-of-concept repositories

326 public repositories from 321 accounts, first seen 2026-04-22. Most starred: theori-io/copy-fail-CVE-2026-31431 (4081 stars), view repository.

Verify before running: public PoCs can be malicious. Read the code and only run it in an isolated lab. A PoC means exploit code is public, not that this CVE is exploited in the wild.

Sources: CISA KEV · Rapid7 Metasploit Framework module metadata · nomi-sec/PoC-in-GitHub.

No ATT&CK techniques could be mapped or inferred for this CVE yet.

How to fix it

CISA required action

"Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. (source: CISA KEV)

Fixed versions

  • linux linux kernel: upgrade to 5.10.254 or later (affected from 4.14)
  • linux linux kernel: upgrade to 5.15.204 or later (affected from 5.11)
  • linux linux kernel: upgrade to 6.1.170 or later (affected from 5.16)
  • linux linux kernel: upgrade to 6.6.137 or later (affected from 6.2)
  • linux linux kernel: upgrade to 6.12.85 or later (affected from 6.7)
  • linux linux kernel: upgrade to 6.18.22 or later (affected from 6.13)
  • linux linux kernel: upgrade to 6.19.12 or later (affected from 6.19)
  • redhat openshift container platform: upgrade to 4.12.89 or later (affected from 4.12)
  • redhat openshift container platform: upgrade to 4.13.66 or later (affected from 4.13)
  • redhat openshift container platform: upgrade to 4.14.65 or later (affected from 4.14)
  • redhat openshift container platform: upgrade to 4.15.64 or later (affected from 4.15)
  • redhat openshift container platform: upgrade to 4.16.61 or later (affected from 4.16)
  • redhat openshift container platform: upgrade to 4.17.53 or later (affected from 4.17)
  • redhat openshift container platform: upgrade to 4.18.40 or later (affected from 4.18)
  • redhat openshift container platform: upgrade to 4.19.30 or later (affected from 4.19)
  • redhat openshift container platform: upgrade to 4.20.21 or later (affected from 4.20)
  • redhat openshift container platform: upgrade to 4.21.14 or later (affected from 4.21)
  • nixos nixos: upgrade to 25.11 or later
  • arista netvisor os: upgrade to 7.1.0 or later
  • siemens simatic cn 4100 firmware: upgrade to 6.0 or later
  • siemens simatic hmi unified comfort panels firmware: upgrade to 21.0 or later

Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.

Vendor advisories and patches

Detection Generic guidance

    Response checklist Generic guidance

    1. Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
    2. Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
    3. Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
    4. Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.

    Sources