Security readout for executives and security teams
Plain-English summary
A remotely supplied RxRPC packet with a misaligned encrypted length can trigger unsafe kernel error handling and disrupt availability. No confidentiality or integrity impact is identified. Systems are most exposed when an affected Linux kernel uses the rxkad security mechanism and accepts untrusted RxRPC traffic.
Executive priority
Prioritize exposed systems using RxRPC/rxkad for prompt assessment and supported kernel updates. Other systems still require inventory confirmation, but urgency may be lower when the component is unused or unreachable. There is no supplied evidence of active exploitation, so response should be urgent and controlled rather than emergency incident declaration.
Technical view
The Linux RxRPC rxkad path mishandles packets whose crypto length is not aligned. The correction validates this condition, aborts on decryption errors other than memory exhaustion, and removes a remotely triggerable WARN_ON_ONCE. CVSS 3.1 is 7.5: network-accessible, low complexity, unauthenticated, no user interaction, with availability impact only.
Likely exposure
The supplied record marks Linux 7.0, 6.6.140, 6.12.86, 6.18.27, 7.0.4, and 7.1 as affected. Practical risk depends on whether RxRPC with rxkad is present, used, and reachable. Distribution kernel backports may make version-only conclusions unreliable, so confirm package-specific status with the distributor.
Exploitation context
The CVSS vector describes unauthenticated network reachability and low attack complexity. However, the supplied record is not in KEV and provides no evidence of active exploitation or public weaponization. Treat denial-of-service as plausible based on the stated remotely triggerable behavior, not as confirmed exploitation in the wild.
Researcher notes
The source bundle identifies availability impact but does not provide a CWE, affected distribution packages, crash mechanics, or exploitation telemetry. Its version lists include Git commit identifiers and upstream releases, so exact exposure requires build-level verification. Analysis should distinguish the misalignment check, decryption-error abort behavior, and removal of remotely triggerable warning handling.
Mitigation direction
- Apply a vendor-supported kernel update containing the referenced Linux stable correction.
- Confirm distribution advisories because vendors may backport fixes without changing upstream version numbering.
- Where operationally feasible, restrict untrusted network access to services using RxRPC and rxkad.
- Follow Linux or distribution guidance if an update is not immediately available.
Validation and detection
- Inventory running kernel builds and compare them with the supplied affected and unaffected statuses.
- Determine whether RxRPC and rxkad are enabled, actively used, and reachable from untrusted networks.
- Verify the installed kernel package includes the applicable referenced stable commit or vendor backport.
- Review kernel logs for RxRPC warnings, decryption failures, aborts, or unexplained availability events.
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-46085 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
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:N/I:N/A:H3.93.6LinuxVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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/f1c6bd0cc786a8fa74829ce3c4b3673944a308f4CVE reference, Linux
- https://git.kernel.org/stable/c/440d20d95e844b657a93a0b2dcc2aae155efdce6CVE reference, Linux
- https://git.kernel.org/stable/c/f0d3efd03b2a9e0f1ffa6df8fcb264af3d494286CVE reference, Linux
- https://git.kernel.org/stable/c/af9271eb666d07b6f65612dc160a47f7cb5220edCVE reference, Linux
- https://git.kernel.org/stable/c/def304aae2edf321d2671fd6ca766a93c21f877eCVE 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.