What is CVE-2026-46059?

CVE-2026-46059 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10, affecting Linux kernel versions from 5.8 onward and patched in 6.18.27, 7.0.4 and 7.1. CVE-2026-46059 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2026-46059?

CVE-2026-46059 has a CVSS score of 5.5 out of 10, rated Medium severity. The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.

Is there a patch available for CVE-2026-46059?

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

Is CVE-2026-46059 actively exploited?

CVE-2026-46059 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

CVE-2026-46059

Medium

In the Linux kernel, the following vulnerability has been resolved: KVM: nSVM: Always use NextRIP as vmcb02's NextRIP after first L2 VMRUN For guests with NRIPS disabled, L1 does not provide NextRIP when running an L2 with an injected soft interrupt, instead it advances the current RIP before running it. KVM uses the current RIP as the NextRIP in vmcb02 to emulate a CPU without NRIPS. However, after L2 runs the first time, NextRIP will be updated by the CPU and/or KVM, and the current RIP is no longer the correct value to use in vmcb02. Hence, after save/restore, use the current RIP if and only if a nested run is pending, otherwise use NextRIP. Give soft_int_next_rip the same treatment, as it's the same logic, just for a narrower use case. [sean: give soft_int_next_rip the same treatment]

Package Linux Kernel

Published 2026-05-27

Last modified 2026-06-16

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

5.5

out of 10

Medium

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

High

Vector string

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected versions

Linux kernel versions 5.8 and later are affected. Fixed in 6.18.27, 7.0.4, 7.1 and their respective stable series.

Affected from

≥ 5.8

Fixed in

✓ 6.18.27 6.18.x ✓ 7.0.4 7.0.x ✓ 7.1

References

3 total

Kernel Git
https://git.kernel.org/stable/c/3428ed1529a1af4cce5aff6c5bd2fcc39ad726bb

Patch
Kernel Git
https://git.kernel.org/stable/c/69fe1411a5ce678b4da6489b5d2282b4e1d13acf

Patch
Kernel Git
https://git.kernel.org/stable/c/8d397582f6b5e9fbcf09781c7c934b4910e94a50

Patch

Details

CVE ID CVE-2026-46059

Severity Medium

CVSS score 5.5 / 10

CVSS version 3.1

Published 2026-05-27

Modified 2026-06-16

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2026-46059?

CVE-2026-46059 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10 . It affects Linux kernel versions from 5.8 onward and has been patched in 6.18.27, 7.0.4 and 7.1. CVE-2026-46059 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2026-46059?

CVE-2026-46059 has a CVSS score of 5.5 out of 10, rated Medium severity (CVSS 3.1). The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
Is there a patch available for CVE-2026-46059?

Yes. CVE-2026-46059 has been patched. Fixed versions include 6.18.27, 7.0.4 and 7.1. If you are running Linux kernel 5.8 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2026-46059 actively exploited?

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