Security readout for executives and security teams
Plain-English summary
A Linux kernel ticket-length check can overflow while processing rxgk data, potentially causing an unsafe length value to pass validation. The supplied CVSS rating is 9.8, indicating potentially severe confidentiality, integrity, and availability consequences. Actual exploit mechanics and practical impact are not documented in the supplied sources.
Executive priority
Treat this as an urgent validation and patching priority because the supplied rating is critical and describes unauthenticated network attack potential. Focus first on externally exposed or high-value Linux systems. Escalate unresolved version ambiguity to distribution vendors; the source bundle does not establish active exploitation.
Technical view
The flaw is in rxgk_extract_token(). Its ticket-length validation rounded up the tested value, which could overflow. The kernel fix instead rounds down the available-data size. The supplied CVSS vector describes network reachability, low complexity, no privileges, no user interaction, unchanged scope, and high impact across confidentiality, integrity, and availability.
Likely exposure
The record identifies Linux kernel versions 6.17, 6.18.27, 7.0.4, and 7.1 as affected; it also lists an anomalous version "0." Exposure depends on the exact kernel build and whether the rxgk code path is present and reachable. The supplied version and commit mapping is incomplete.
Exploitation context
The supplied bundle says this CVE is not in KEV and provides no evidence of active exploitation or a public proof of concept. That does not establish absence of exploitation. The critical CVSS vector indicates a remotely reachable, unauthenticated scenario, but the sources do not explain prerequisites or demonstrate exploitability.
Researcher notes
The core issue is arithmetic wraparound during ticket-length validation in rxgk_extract_token(). Review should focus on the changed boundary calculation and applicable stable-tree backports. The record contains unusual and duplicated version data, including "0," so conclusions require commit- or package-level confirmation. No CWE, exploit evidence, prerequisites, or named workaround is supplied.
Mitigation direction
- Apply a vendor-supported kernel update incorporating the applicable referenced stable fix.
- Prioritize exposed systems where the rxgk code path is present or used.
- If immediate updating is impossible, consult the Linux distribution vendor for supported mitigations.
- Avoid inferring safety from version strings alone; verify distribution backports and build provenance.
Validation and detection
- Inventory each system's running kernel version, distribution package, and build identifier.
- Check vendor advisories for affected and fixed package mappings.
- Verify the installed kernel incorporates the applicable referenced fix commit or vendor backport.
- Confirm the updated kernel is running after remediation.
- Document whether rxgk functionality is present and reachable in each environment.
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-46039 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
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/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:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9LinuxVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/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/43222ac484f93b3ec2d240a7575e1cedd31f5fa4CVE reference, Linux
- https://git.kernel.org/stable/c/183d37f12d1c8ed24a5bfc7addad05510da22a94CVE reference, Linux
- https://git.kernel.org/stable/c/6929350080f4da292d111a3b33e53138fee51cecCVE 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.