CVE-2026-46010

High

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).

Package Linux Kernel
Published 2026-05-27
Last modified 2026-05-30
CVSS version 3.1
Patch available
Yes

CVSS 3.1 score

8.1

out of 10
High
Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High
Vector string
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected versions

Linux kernel versions 6.16.9, 6.17 and later are affected. Fixed in 6.18.27, 7.0.4, 7.1-rc1 and their respective stable series.

Affected from
≥ 6.16.9 ≥ 6.17
Fixed in
✓ 6.18.27 6.18.x ✓ 7.0.4 7.0.x ✓ 7.1-rc1

References

The following references provide additional information about CVE-2026-46010 including vendor advisories, patch commits, exploit details, and third-party analysis. Links are sourced from the NIST NVD database.

Frequently asked questions

  • What is CVE-2026-46010?

    CVE-2026-46010 is a High severity Linux kernel vulnerability with a CVSS score of 8.1 out of 10 . It affects Linux kernel versions from 6.16.9 onward and has been patched in 6.18.27, 7.0.4 and 7.1-rc1. CVE-2026-46010 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

  • What is the CVSS score for CVE-2026-46010?

    CVE-2026-46010 has a CVSS score of 8.1 out of 10, rated High severity (CVSS 3.1). The vector string is CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H .

  • Is there a patch available for CVE-2026-46010?

    Yes — CVE-2026-46010 has been patched. Fixed versions include 6.18.27, 7.0.4 and 7.1-rc1. If you are running Linux kernel 6.16.9 or later up to the fix versions, apply the relevant patch for your kernel branch.

  • Is CVE-2026-46010 actively exploited?

    No — CVE-2026-46010 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.