Skip to content
Heist/ feed
Back to feed
HighFix available

fscrypt: Add missing superblock check in find_or_insert_direct_key()

Type: advisorySources: OSV

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.

Products
Kernel
Affected versions
Not specified
Fixed versions
6.1.183, 6.12.101, 6.18.42, 6.6.148, 7.1.6
CVEs
CVE-2026-68148
Confirmed fixed CVEs
Not specified
Updated in this feed
3 Nov 2026, 07:59 UTC · Revision 1

Source evidence

fscrypt: Add missing superblock check in find_or_insert_direct_key()

core-osv · Original source

Published 10 Aug 2026, 11:59 UTC

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.

osv:CVE-2026-68148

Kernel

Fixed versions: 6.1.183, 6.6.148, 6.12.101, 6.18.42, 7.1.6

Complete source record
{
  "id": "35710c22d1a4c6c6d9e94933c4e36741524b1826c9f5527ef9dee7fe9ae9e93b",
  "url": "https://osv.dev/vulnerability/CVE-2026-68148",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "fscrypt: Add missing superblock check in find_or_insert_direct_key()",
    "summary": "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.",
    "evidence": "osv:CVE-2026-68148",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "6.1.183",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.6.148",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.12.101",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.18.42",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "7.1.6",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "high",
    "structured": {
      "id": "CVE-2026-68148",
      "aliases": [
        "CVE-2026-68148"
      ],
      "metrics": [
        {
          "type": "CVSS_V3",
          "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "22e9947a4b2ba255888541bd0111cf00b9b16586"
                },
                {
                  "fixed": "965b5bc8cf5031225e057979ce660fec2bd5fbfc"
                },
                {
                  "fixed": "330249609b70778094a7a36f5b6bcfa6362121d4"
                },
                {
                  "fixed": "deff41898a5ae3a47db5fa1896a494aa95efda5d"
                },
                {
                  "fixed": "95376fe9c145be35566991df99c53134943d992f"
                },
                {
                  "fixed": "466f187b501a5ac8e1ea2ccf3ccd5c46108d8830"
                },
                {
                  "fixed": "b5fa40226e71c17847b9ff2816c6ca4133d0d994"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-68148.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.1.0"
                },
                {
                  "fixed": "6.1.183"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.2.0"
                },
                {
                  "fixed": "6.6.148"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.7.0"
                },
                {
                  "fixed": "6.12.101"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.13.0"
                },
                {
                  "fixed": "6.18.42"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.19.0"
                },
                {
                  "fixed": "7.1.6"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-68148.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:26.902217270Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/330249609b70778094a7a36f5b6bcfa6362121d4",
        "https://git.kernel.org/stable/c/466f187b501a5ac8e1ea2ccf3ccd5c46108d8830",
        "https://git.kernel.org/stable/c/95376fe9c145be35566991df99c53134943d992f",
        "https://git.kernel.org/stable/c/965b5bc8cf5031225e057979ce660fec2bd5fbfc",
        "https://git.kernel.org/stable/c/b5fa40226e71c17847b9ff2816c6ca4133d0d994",
        "https://git.kernel.org/stable/c/deff41898a5ae3a47db5fa1896a494aa95efda5d",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/68xxx/CVE-2026-68148.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-68148",
        "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
      ],
      "provider_metadata": {
        "cna_assigner": "Linux",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/68xxx/CVE-2026-68148.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-68148",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 493568,
  "published_at": "2026-08-10T11:59:13.413+00:00"
}