CVE-2026-98222
KEYS: encrypted: fix integer overflow of datablob_len
No known exploitation. EPSS puts it in the 6th percentile. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- LinuxAffected: ≥ 7e70cb4978507cf31d76b90e4cfb4c28cad87f0c, < 1e720f63dbafc093a8f5d519f05b67724993edd4Upgrade to: 1e720f63dbafc093a8f5d519f05b67724993edd4Affected: ≥ 7e70cb4978507cf31d76b90e4cfb4c28cad87f0c, < a1a98eca102b1cbbc37ff9eaa197ae4e6a3ea4b0Upgrade to: a1a98eca102b1cbbc37ff9eaa197ae4e6a3ea4b0Affected: ≥ 7e70cb4978507cf31d76b90e4cfb4c28cad87f0c, < cca38f2102a4cd35eda8d48950df4817b4b24757Upgrade to: cca38f2102a4cd35eda8d48950df4817b4b24757Affected: ≥ 7e70cb4978507cf31d76b90e4cfb4c28cad87f0c, < 8697c431e297eb0d0ab13dda6bc172b48a34f05cUpgrade to: 8697c431e297eb0d0ab13dda6bc172b48a34f05cStated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
In the Linux kernel, the following vulnerability has been resolved: KEYS: encrypted: fix integer overflow of datablob_len encrypted_key_alloc() stores datablob_len in a u16. It is computed from multiple string and payload lengths. If the result exceeds U16_MAX, the assignment truncates the allocation size. KASAN reports a 32760-byte slab-out-of-bounds write when __ekey_init() copies the master key description into the undersized buffer. The total payload length stored in key->datalen is also a u16. Use check_add_overflow() to reject values that do not fit either destination, and use kzalloc_flex() for the flexible-array allocation.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.2% chance of exploitation activity in the next 30 days, which ranks it in the 6th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
2 events over 0 days, from the signal feeds we watch.
- Publishedrecord updated
Affected products
Sources
References in the record
- git.kernel.org/stable/c/1e720f63dbafc093a8f5d519f05b67724993edd4
- git.kernel.org/stable/c/8697c431e297eb0d0ab13dda6bc172b48a34f05c
- git.kernel.org/stable/c/a1a98eca102b1cbbc37ff9eaa197ae4e6a3ea4b0
And 1 more reference. See all after sign-in
In the news
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Linux, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI