What is CVE-2026-22995?

CVE-2026-22995 is a High severity Linux kernel vulnerability with a CVSS score of 7.8 out of 10, classified as a Use After Free flaw (CWE-416), affecting Linux kernel versions from 6.18.4 onward and patched in 6.18.6. CVE-2026-22995 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

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

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

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

Yes, CVE-2026-22995 has been patched. Fixed versions include 6.18.6. If you are running Linux kernel 6.18.4 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2026-22995 actively exploited?

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

What is Use After Free (CWE-416)?

The product references memory after it has been freed, which may cause it to crash, use unexpected values, or execute code. See MITRE CWE for full details: https://cwe.mitre.org/data/definitions/416.html

CVE-2026-22995

High

In the Linux kernel, the following vulnerability has been resolved: ublk: fix use-after-free in ublk_partition_scan_work A race condition exists between the async partition scan work and device teardown that can lead to a use-after-free of ub->ub_disk: 1. ublk_ctrl_start_dev() schedules partition_scan_work after add_disk() 2. ublk_stop_dev() calls ublk_stop_dev_unlocked() which does: - del_gendisk(ub->ub_disk) - ublk_detach_disk() sets ub->ub_disk = NULL - put_disk() which may free the disk 3. The worker ublk_partition_scan_work() then dereferences ub->ub_disk leading to UAF Fix this by using ublk_get_disk()/ublk_put_disk() in the worker to hold a reference to the disk during the partition scan. The spinlock in ublk_get_disk() synchronizes with ublk_detach_disk() ensuring the worker either gets a valid reference or sees NULL and exits early. Also change flush_work() to cancel_work_sync() to avoid running the partition scan work unnecessarily when the disk is already detached.

Package Linux Kernel

Published 2026-01-23

Last modified 2026-02-26

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

7.8

out of 10

High

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Vector string

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

Weakness type

CWE-416

CVE-2026-22995 is a Use After Free vulnerability

What is Use After Free?

The product references memory after it has been freed, which may cause it to crash, use unexpected values, or execute code. Learn more on MITRE CWE

Affected versions

Linux kernel versions 6.18.4 and later are affected. Fixed in 6.18.6 and their respective stable series.

Affected from

≥ 6.18.4

Fixed in

✓ 6.18.6 6.18.x

References

2 total

Kernel Git
https://git.kernel.org/stable/c/72e28774e9644c2bdbb4920842fbf77103a15a85

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

Patch

Details

CVE ID CVE-2026-22995

Severity High

CVSS score 7.8 / 10

CVSS version 3.1

Published 2026-01-23

Modified 2026-02-26

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2026-22995?

CVE-2026-22995 is a High severity Linux kernel vulnerability with a CVSS score of 7.8 out of 10 , classified as an Use After Free flaw (CWE-416) . It affects Linux kernel versions from 6.18.4 onward and has been patched in 6.18.6. CVE-2026-22995 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2026-22995?

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

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

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