CVE-2026-46010

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-05-27. the CNA's CVSS baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 5 sources updated this week
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.1Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

rxrpc: Fix error handling in rxgk_extract_token()

Fix a missing bit of error handling in rxgk_extract_token(): in the event that rxgk_decrypt_skb() returns -ENOMEM, it should just return that rather than continuing on (for anything else, it generates an abort).

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
41(Track)
EG Risk 41/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity81% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
34%
KEV
Not listed

Published

May 27, 2026

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Jun 3, 2026
No patch confirmed yet.
generic

rxrpc: Fix error handling in rxgk_extract_token() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c52803e925604e2a17962ab0c99dce2d3f7238db
generic

rxrpc: Fix error handling in rxgk_extract_token() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3476c8bb960f48e49355d6f93fb7673211e0163f
generic

rxrpc: Fix error handling in rxgk_extract_token() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/293095ef618818852bac5488c1bc223935e2ca17

Vendor Advisories for CVE-2026-46010(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(7)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-09-14ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-27.27) @ resolute2026-09-14ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1013.13) @ resolute2026-09-14ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-09-14ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1008.8) @ resolute2026-09-14ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1014.14) @ resolute2026-09-14ubuntu
linuxKernel @ 6.18.27—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.4-1~bpo13+1 (134 versions)7.0.4-1—

All Vendor Advisories

(6)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 10× in last 7d / 44× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 275 total refreshes for this CVE.

  1. 2026-09-16 05:15 UTCEPSS rescore
  2. 2026-09-14 08:37 UTCEG score recompute
  3. 2026-09-14 08:37 UTCVendor advisory
  4. 2026-09-14 08:37 UTCGHSA enrichment
  5. 2026-09-13 16:47 UTCEPSS rescore
  6. 2026-09-13 04:09 UTCOSV refresh
  7. 2026-09-12 15:01 UTCEPSS rescore
  8. 2026-09-11 14:53 UTCEPSS rescore
  9. 2026-09-11 09:37 UTCEPSS rescore
  10. 2026-09-10 09:34 UTCEPSS rescore
  11. 2026-09-08 22:00 UTCEPSS rescore
  12. 2026-09-07 16:01 UTCEPSS rescore
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-04 05:06 UTCEPSS rescore
  15. 2026-09-02 14:12 UTCEPSS rescore
  16. 2026-09-01 13:54 UTCEPSS rescore
  17. 2026-08-30 19:17 UTCEPSS rescore
  18. 2026-08-30 01:22 UTCEPSS rescore
  19. 2026-08-28 21:41 UTCEPSS rescore
  20. 2026-08-27 14:25 UTCEPSS rescore
  21. 2026-08-26 14:46 UTCEPSS rescore
  22. 2026-08-25 13:49 UTCEPSS rescore
  23. 2026-08-25 05:31 UTCEG score recompute
  24. 2026-08-25 05:31 UTCVendor advisory
  25. 2026-08-25 05:30 UTCGHSA enrichment
Show 75 more
  1. 2026-08-23 15:16 UTCEG score recompute
  2. 2026-08-23 15:16 UTCVendor advisory
  3. 2026-08-23 15:16 UTCGHSA enrichment
  4. 2026-08-23 00:19 UTCEPSS rescore
  5. 2026-08-21 23:49 UTCEPSS rescore
  6. 2026-08-21 20:42 UTCEG score recompute
  7. 2026-08-21 20:42 UTCVendor advisory
  8. 2026-08-21 20:42 UTCGHSA enrichment
  9. 2026-08-20 22:55 UTCEPSS rescore
  10. 2026-08-20 22:37 UTCVendor advisory
  11. 2026-08-20 22:37 UTCGHSA enrichment
  12. 2026-08-20 11:36 UTCEG score recompute
  13. 2026-08-20 11:36 UTCVendor advisory
  14. 2026-08-20 11:36 UTCGHSA enrichment
  15. 2026-08-19 17:04 UTCEPSS rescore
  16. 2026-08-18 13:48 UTCEPSS rescore
  17. 2026-08-17 13:47 UTCEPSS rescore
  18. 2026-08-17 09:19 UTCVendor advisory
  19. 2026-08-17 09:19 UTCGHSA enrichment
  20. 2026-08-16 15:35 UTCEG score recompute
  21. 2026-08-16 15:35 UTCVendor advisory
  22. 2026-08-16 15:35 UTCGHSA enrichment
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 02:52 UTCEG score recompute
  25. 2026-08-16 02:52 UTCVendor advisory
  26. 2026-08-16 02:52 UTCGHSA enrichment
  27. 2026-08-16 02:14 UTCEPSS rescore
  28. 2026-08-15 01:30 UTCEPSS rescore
  29. 2026-08-14 23:13 UTCVendor advisory
  30. 2026-08-14 23:13 UTCGHSA enrichment
  31. 2026-08-14 12:20 UTCVendor advisory
  32. 2026-08-14 12:20 UTCGHSA enrichment
  33. 2026-08-14 01:29 UTCEG score recompute
  34. 2026-08-14 01:29 UTCVendor advisory
  35. 2026-08-14 01:28 UTCGHSA enrichment
  36. 2026-08-13 22:00 UTCEPSS rescore
  37. 2026-08-13 09:14 UTCVendor advisory
  38. 2026-08-13 09:14 UTCGHSA enrichment
  39. 2026-08-12 22:22 UTCEG score recompute
  40. 2026-08-12 22:22 UTCVendor advisory
  41. 2026-08-12 22:22 UTCGHSA enrichment
  42. 2026-08-12 13:51 UTCEPSS rescore
  43. 2026-08-12 11:29 UTCVendor advisory
  44. 2026-08-12 11:29 UTCGHSA enrichment
  45. 2026-08-12 00:28 UTCEG score recompute
  46. 2026-08-12 00:28 UTCVendor advisory
  47. 2026-08-12 00:28 UTCGHSA enrichment
  48. 2026-08-11 13:36 UTCVendor advisory
  49. 2026-08-11 13:36 UTCGHSA enrichment
  50. 2026-08-11 00:13 UTCEG score recompute
  51. 2026-08-11 00:13 UTCVendor advisory
  52. 2026-08-11 00:13 UTCGHSA enrichment
  53. 2026-08-11 00:00 UTCEPSS rescore
  54. 2026-08-10 06:23 UTCVendor advisory
  55. 2026-08-10 06:23 UTCGHSA enrichment
  56. 2026-08-09 19:31 UTCEG score recompute
  57. 2026-08-09 19:31 UTCVendor advisory
  58. 2026-08-09 19:31 UTCGHSA enrichment
  59. 2026-08-09 13:46 UTCEPSS rescore
  60. 2026-08-09 08:39 UTCVendor advisory
  61. 2026-08-09 08:39 UTCGHSA enrichment
  62. 2026-08-08 21:47 UTCEG score recompute
  63. 2026-08-08 21:47 UTCVendor advisory
  64. 2026-08-08 21:47 UTCGHSA enrichment
  65. 2026-08-08 16:37 UTCEPSS rescore
  66. 2026-08-08 09:06 UTCVendor advisory
  67. 2026-08-08 09:06 UTCGHSA enrichment
  68. 2026-08-07 22:14 UTCEG score recompute
  69. 2026-08-07 22:14 UTCVendor advisory
  70. 2026-08-07 22:14 UTCGHSA enrichment
  71. 2026-08-07 11:21 UTCVendor advisory
  72. 2026-08-07 11:21 UTCGHSA enrichment
  73. 2026-08-07 00:29 UTCEG score recompute
  74. 2026-08-07 00:29 UTCVendor advisory
  75. 2026-08-07 00:29 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-46010?
CVE-2026-46010 is a high vulnerability published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix error handling in rxgkextracttoken() Fix a missing bit of error handling in rxgkextracttoken(): in the event that rxgkdecryptskb() returns -ENOMEM, it should just return that rather than continuing on (for anything else,…
When was CVE-2026-46010 disclosed?
CVE-2026-46010 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46010 actively exploited?
CVE-2026-46010 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 66.0% of all scored CVEs.
What is the CVSS score of CVE-2026-46010?
CVE-2026-46010 has a CVSS v4.0 base score of 8.1 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-46010?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46010, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-46010

Explore →

Is Your Infrastructure Affected by CVE-2026-46010?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs