Security readout for executives and security teams
Plain-English summary
A Linux kernel error-handling flaw may cause unsafe processing when RxGK token decryption runs out of memory. The supplied CVSS score is 8.1, indicating potentially serious confidentiality, integrity, and availability impact, although practical exploitability and affected configurations are not documented in the bundle.
Executive priority
Prioritize verification promptly because the supplied severity is high and the flaw is described as network-reachable. Expedite patching where affected kernels and reachable RxRPC/RxGK use are confirmed. Avoid declaring an emergency solely from the CVSS score because active exploitation and practical attack conditions are not established.
Technical view
In rxgk_extract_token(), an -ENOMEM return from rxgk_decrypt_skb() was not immediately propagated, allowing execution to continue. The kernel fix returns the memory-allocation error directly; other decryption errors generate an abort. The supplied sources do not explain the subsequent unsafe state or demonstrate exploitation.
Likely exposure
The bundle marks Linux 6.17, 6.18.27, 7.0.4, and 7.1 as affected, but also contains an unexplained version entry of 0. Exposure likely depends on whether the deployed kernel includes vulnerable RxRPC/RxGK code and whether that token-processing path is reachable. Confirm status against distribution advisories and the referenced stable commits.
Exploitation context
The CVSS vector describes unauthenticated network reachability with high attack complexity and no user interaction. However, the bundle provides no proof of concept, exploitation report, or evidence of active exploitation, and the CVE is not listed as KEV. Treat the impact ratings as risk indicators, not confirmation of a practical attack.
Researcher notes
Important unknowns include the exact post-error execution consequence, required kernel configuration, protocol reachability, and reliable fixed-version boundaries. The affected-version data is internally unusual, including duplicate commit identifiers and version 0. Use commit-level comparison and distributor backport information rather than version-string matching alone.
Mitigation direction
- Update to a vendor-supported kernel containing the applicable referenced stable fix.
- Consult the Linux distribution advisory to map packaged kernels to fixed upstream commits.
- Prioritize systems using or exposing RxRPC/RxGK functionality.
- Restrict unnecessary network exposure while updates are evaluated.
Validation and detection
- Record kernel and distribution package versions across potentially exposed systems.
- Determine whether RxRPC/RxGK functionality is configured, loaded, or operationally required.
- Compare vendor patches against the three referenced stable kernel commits.
- Retest relevant RxRPC/RxGK workloads after updating for functional regressions.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2026-46010 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H2.25.9LinuxVulnerability scoring details
Base CVSS 3.1 score
8.1HighVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/293095ef618818852bac5488c1bc223935e2ca17CVE reference, Linux
- https://git.kernel.org/stable/c/c52803e925604e2a17962ab0c99dce2d3f7238dbCVE reference, Linux
- https://git.kernel.org/stable/c/3476c8bb960f48e49355d6f93fb7673211e0163fCVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.