Skip to main content
Mallory
UnratedVulnerability

CVE-2026-98222: Integer overflow and heap buffer overflow in Linux kernel encrypted keys

Published Oct 6, 2026 · Updated 5 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days24 mentions · peak 5 in a dayToday
CVSS-Not scored
EPSS0.17%6th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Linux
IdentifiersCVE-2026-98222CWE-190

CVE-2026-98222 is an integer-overflow vulnerability in the Linux kernel's encrypted-key subsystem. encrypted_key_alloc() calculates datablob_len from multiple string and payload lengths but stores the result in a 16-bit unsigned integer. Values exceeding 65,535 are truncated, causing an undersized allocation. When __ekey_init() subsequently copies the master key description into this buffer, it writes beyond the allocation. KASAN detected a 32,760-byte slab-out-of-bounds write. The total payload length stored in key->datalen is also subject to a 16-bit size limit. The vulnerability can corrupt kernel heap memory and potentially cause denial of service.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful triggering corrupts kernel heap memory through an out-of-bounds write, potentially causing a kernel crash and system-wide denial of service. Arbitrary code execution, information disclosure, and privilege escalation are not established specifically for this CVE.

Mitigation

If you can’t patch tonight, do this now.

No vulnerability-specific temporary mitigation or workaround is currently available in the supplied technical information.

Remediation

Patch, then assume compromise.

Install a vendor-supported kernel update containing the fix 'KEYS: encrypted: fix integer overflow of datablob_len' and reboot into the updated kernel. The fix uses check_add_overflow() to reject lengths that cannot fit in datablob_len or key->datalen and uses kzalloc_flex() for the flexible-array allocation. RHEL 8 fixes are available in kernel 4.18.0-553.180.1.el8_10 under RHSA-2026:92209 and kernel-rt 4.18.0-553.180.1.rt7.521.el8_10 under RHSA-2026:92208. Use the applicable vendor advisory for other releases and kernel variants.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
LinuxLinux Kerneloperating_system
FAQ

Frequently asked questions

Is CVE-2026-98222 exploited in the wild?
As of Nov 12, 2026, Mallory has no reports of CVE-2026-98222 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-98222?
As of Nov 12, 2026, Mallory has found no public exploit for CVE-2026-98222.
Is there a patch for CVE-2026-98222?
Install a vendor-supported kernel update containing the fix 'KEYS: encrypted: fix integer overflow of datablob_len' and reboot into the updated kernel. The fix uses check_add_overflow() to reject lengths that cannot fit in datablob_len or key->datalen and uses kzalloc_flex() for the flexible-array allocation.
What products are affected by CVE-2026-98222?
Linux Kernel.
How severe is CVE-2026-98222?
CVE-2026-98222 has an EPSS score of 0.17% (6th percentile) as of Nov 12, 2026.
Activity feed

Recent activity

27 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+23 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.