Skip to main content
VulnerabilityPublished Updated

CVE-2026-23005: Linux kernel · Improper Input Validation

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in f577508cc8a0adb8b4ebe9480bba7683b6149930 : patch Linux kernel soon.

Data as of 26 Oct 2026, 17:30 UTC

Severity
High

Rated High by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

EPSS
0.2% chance of exploitation in 30 days – higher than 12% 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 cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-06-10.

Patch
Available – fixed in f577508cc8a0adb8b4ebe9480bba7683b6149930, eea6f395ca502c4528314c8112da9b5d65f685eb, b5995c01ba53d84182ecb9492fc4d91cfe8a362d +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Jan 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
  • ≥ 820a6ee944e74e57255ac2e90916ecdaade57b95, < f577508cc8a0adb8b4ebe9480bba7683b6149930
Fixed in
  • f577508cc8a0adb8b4ebe9480bba7683b6149930
LinuxLinuxAffected
  • ≥ 820a6ee944e74e57255ac2e90916ecdaade57b95, < eea6f395ca502c4528314c8112da9b5d65f685eb
Fixed in
  • eea6f395ca502c4528314c8112da9b5d65f685eb
LinuxLinuxAffected
  • ≥ 820a6ee944e74e57255ac2e90916ecdaade57b95, < b5995c01ba53d84182ecb9492fc4d91cfe8a362d
Fixed in
  • b5995c01ba53d84182ecb9492fc4d91cfe8a362d
LinuxLinuxAffected
  • ≥ 820a6ee944e74e57255ac2e90916ecdaade57b95, < b45f721775947a84996deb5c661602254ce25ce6
Fixed in
  • b45f721775947a84996deb5c661602254ce25ce6
LinuxLinuxAffected
  • ≥ 820a6ee944e74e57255ac2e90916ecdaade57b95, < 1e2848bda819af569dfe7ab186223855e092a2cb
Fixed in
  • 1e2848bda819af569dfe7ab186223855e092a2cb
LinuxLinuxAffected
  • =5.17
Fixed in–

AI-suggested

A fix for this vulnerability has been implemented in the Linux kernel. Systems running affected versions should apply the official kernel updates containing the fix. No additional mitigation steps are required beyond applying the patch.

Description

A Linux kernel vulnerability in the x86/fpu subsystem was fixed by ensuring that the guest XSAVE state clears XSTATE_BV bits for features disabled via the guest's XFD. Without this fix, loading guest XSAVE state with mismatched XFD and XSTATE_BV bits could cause the kernel to execute XRSTOR with invalid state, leading to a #NM exception and kernel panic. This issue occurs in KVM virtualization environments when guest WRMSR instructions update XFD and userspace sets XSTATE_BV inconsistently. The fix aligns behavior with Intel's architecture specification by clearing XSTATE_BV bits for disabled features, preventing kernel crashes.

References

Community reviews

Loading reviews…