What is CVE-2026-23217?

CVE-2026-23217 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10, classified as a Improper Locking flaw (CWE-667), affecting Linux kernel versions from 6.10.10 onward and patched in 6.18.10 and 6.19. CVE-2026-23217 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

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

CVE-2026-23217 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-23217?

Yes, CVE-2026-23217 has been patched. Fixed versions include 6.18.10 and 6.19. If you are running Linux kernel 6.10.10 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2026-23217 actively exploited?

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

What is Improper Locking (CWE-667)?

The product does not properly acquire or release a lock, which can lead to unexpected behaviour. See MITRE CWE for full details: https://cwe.mitre.org/data/definitions/667.html

CVE-2026-23217

Medium

In the Linux kernel, the following vulnerability has been resolved: riscv: trace: fix snapshot deadlock with sbi ecall If sbi_ecall.c's functions are traceable, echo "__sbi_ecall:snapshot" > /sys/kernel/tracing/set_ftrace_filter may get the kernel into a deadlock. (Functions in sbi_ecall.c are excluded from tracing if CONFIG_RISCV_ALTERNATIVE_EARLY is set.) __sbi_ecall triggers a snapshot of the ringbuffer. The snapshot code raises an IPI interrupt, which results in another call to __sbi_ecall and another snapshot... All it takes to get into this endless loop is one initial __sbi_ecall. On RISC-V systems without SSTC extension, the clock events in timer-riscv.c issue periodic sbi ecalls, making the problem easy to trigger. Always exclude the sbi_ecall.c functions from tracing to fix the potential deadlock. sbi ecalls can easiliy be logged via trace events, excluding ecall functions from function tracing is not a big limitation.

Package Linux Kernel

Published 2026-02-18

Last modified 2026-03-18

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

Weakness type

CWE-667

CVE-2026-23217 is a Improper Locking vulnerability

What is Improper Locking?

The product does not properly acquire or release a lock, which can lead to unexpected behaviour. Learn more on MITRE CWE

Affected versions

Linux kernel versions 6.10.10, 6.11 and later are affected. Fixed in 6.18.10, 6.19 and their respective stable series.

Affected from

≥ 6.10.10 ≥ 6.11

Fixed in

✓ 6.18.10 6.18.x ✓ 6.19

References

2 total

Kernel Git
https://git.kernel.org/stable/c/b0d7f5f0c9f05f1b6d4ee7110f15bef9c11f9df0

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

Patch

Details

CVE ID CVE-2026-23217

Severity Medium

CVSS score 5.5 / 10

CVSS version 3.1

Published 2026-02-18

Modified 2026-03-18

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2026-23217?

CVE-2026-23217 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10 , classified as an Improper Locking flaw (CWE-667) . It affects Linux kernel versions from 6.10.10 onward and has been patched in 6.18.10 and 6.19. CVE-2026-23217 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2026-23217?

CVE-2026-23217 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-23217?

Yes. CVE-2026-23217 has been patched. Fixed versions include 6.18.10 and 6.19. If you are running Linux kernel 6.10.10 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2026-23217 actively exploited?

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