CVE-2026-46010Network attack vector

Undecrypted token processing via ignored allocation failure

Published May 27, 2026 · Updated May 27, 2026

Improper error handling in Linux Kernel allows remote attackers to continue RxGK authentication after token decryption fails. In rxgk_extract_token(), an -ENOMEM return from rxgk_decrypt_skb() falls through to default_decode_ticket() instead of returning the allocation error. Reachability requires an RxGK connection and a decryption-time allocation failure; the flawed path passes a token that was not successfully decrypted into ticket decoding.

CVSS severity8.1
High
EPSS probability0.40%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper error handling in Linux Kernel allows remote attackers to continue RxGK authentication after token decryption fails. In rxgk_extract_token(), an -ENOMEM return from rxgk_decrypt_skb() falls through to default_decode_ticket() instead of returning the allocation error. Reachability requires an RxGK connection and a decryption-time allocation failure; the flawed path passes a token that was not successfully decrypted into ticket decoding.

The record

CVE
CVE-2026-46010
Published
May 27, 2026
Updated
May 27, 2026
Vendor
The Linux Kernel Organization
Product
Linux Kernel
Classifications
Unavailable
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. May 27, 2026CVE publishedPublication date reported by the CVE source.
  2. May 27, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=6.16.9 <6.17
  2. Affected versionversion=6.17
  3. Affected versionversion=64863f4ca4945bdb62ce2b30823f39ea9fe95415 <293095ef618818852bac5488c1bc223935e2ca17
  4. Affected versionversion=64863f4ca4945bdb62ce2b30823f39ea9fe95415 <3476c8bb960f48e49355d6f93fb7673211e0163f
  5. Affected versionversion=64863f4ca4945bdb62ce2b30823f39ea9fe95415 <c52803e925604e2a17962ab0c99dce2d3f7238db
  6. Affected versionversion=8ac99c57029e13ebb5fb0d634925abedef32b53a

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

The Linux Kernel Organization · Linux Kernelversion=6.16.9 <6.17; version=6.17; version=64863f4ca4945bdb62ce2b30823f39ea9fe95415 <293095ef618818852bac5488c1bc223935e2ca17; version=64863f4ca4945bdb62ce2b30823f39ea9fe95415 <3476c8bb960f48e49355d6f93fb7673211e0163f; version=64863f4ca4945bdb62ce2b30823f39ea9fe95415 <c52803e925604e2a17962ab0c99dce2d3f7238db; version=8ac99c57029e13ebb5fb0d634925abedef32b53a

Published CVSS scores

8.1kernel.orgCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

No sourced classifications are available.

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo