What is CVE-2026-68148?

CVE-2026-68148 is a High severity Linux kernel vulnerability with a CVSS score of 7.8 out of 10, affecting Linux kernel versions from 6.1 onward and patched in 6.1.183, 6.6.148, 6.12.101 and others. CVE-2026-68148 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

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

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

Yes, CVE-2026-68148 has been patched. Fixed versions include 6.1.183, 6.6.148, 6.12.101 and others. If you are running Linux kernel 6.1 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2026-68148 actively exploited?

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

CVE-2026-68148

High

In the Linux kernel, the following vulnerability has been resolved: fscrypt: Add missing superblock check in find_or_insert_direct_key() The legacy 'fscrypt_direct_keys' table caches master keys that are used by v1 encryption policies that have FSCRYPT_POLICY_FLAG_DIRECT_KEY. It's just a global table for all filesystems (since the keys can be provided by the legacy process-subscribed keyrings mechanism, which makes it difficult to reuse super_block::s_master_keys). The entries in it ('struct fscrypt_direct_key') do contain a super_block pointer, though, for passing to fscrypt_destroy_inline_crypt_key() when the last inode that references the key is evicted. However, when finding the fscrypt_direct_key for an inode, we weren't actually comparing the super_block pointer. As a result, inodes with different super_blocks could point to the same fscrypt_direct_key. That could extend the lifetime of a fscrypt_direct_key beyond the super_block it points to, causing a use-after-free later. Fix this by creating distinct fscrypt_direct_key structs for distinct super_block structs. Note that this problem doesn't exist in the v2 policy equivalent ("per-mode keys"), since the data structures there are per super_block.

Package Linux Kernel

Published 2026-08-10

Last modified 2026-08-19

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

Affected versions

Linux kernel versions 6.1 and later are affected. Fixed in 6.1.183, 6.6.148, 6.12.101, 6.18.42, 7.1.6, 7.2 and their respective stable series.

Affected from

≥ 6.1

Fixed in

✓ 6.1.183 6.1.x ✓ 6.6.148 6.6.x ✓ 6.12.101 6.12.x ✓ 6.18.42 6.18.x ✓ 7.1.6 7.1.x ✓ 7.2

References

6 total

Showing 5 of 6 references View all on NVD

Details

CVE ID CVE-2026-68148

Severity High

CVSS score 7.8 / 10

CVSS version 3.1

Published 2026-08-10

Modified 2026-08-19

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2026-68148?

CVE-2026-68148 is a High severity Linux kernel vulnerability with a CVSS score of 7.8 out of 10 . It affects Linux kernel versions from 6.1 onward and has been patched in 6.1.183, 6.6.148, 6.12.101 and others. CVE-2026-68148 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2026-68148?

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

Yes. CVE-2026-68148 has been patched. Fixed versions include 6.1.183, 6.6.148, 6.12.101 and others. If you are running Linux kernel 6.1 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2026-68148 actively exploited?

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