{
  "cveId": "CVE-2026-68147",
  "url": "https://patchblox.com/security/cve/CVE-2026-68147",
  "summary": "CVE-2026-68147 is fixed in 2 products on 1 platform, first by DEBIAN-CVE-2026-68147, released August 11, 2026. It is not reported as exploited. Patch Radar priority: High.",
  "title": "fscrypt: Avoid dynamic allocation in fscrypt_get_devices()",
  "description": "In the Linux kernel, the following vulnerability has been resolved:  fscrypt: Avoid dynamic allocation in fscrypt_get_devices()  When a blk_crypto_key starts being used or is evicted, fs/crypto/ calls fscrypt_get_devices() to get the filesystem\u0027s list of block devices, then iterates over them and calls blk_crypto_config_supported(), blk_crypto_start_using_key(), or blk_crypto_evict_key() on each one.  Currently, the block device pointers are placed in a dynamically allocated array.  This dynamic allocation is problematic because:  - It can fail, especially at the fscrypt_destroy_inline_crypt_key() call   site when it\u0027s invoked for inode eviction under direct reclaim.  - fscrypt_destroy_inline_crypt_key() doesn\u0027t handle the failure.  It   just zeroizes and frees the blk_crypto_key without calling   blk_crypto_evict_key().  That causes a use-after-free.  For now, let\u0027s fix this in the straightforward and easily-backportable way by switching to an on-stack array.  Currently the fscrypt multi-device functionality is used only by f2fs, which has a hardcoded limit of 8 block devices.  An on-stack array works fine for that.  (Of course, this solution won\u0027t scale up to large number of block devices.  For that we\u0027d need a different solution, like moving the block device iteration into the filesystem.  Or in the case of btrfs, which will only support blk-crypto-fallback, we should make it just call blk-crypto-fallback directly, so the block devices won\u0027t be needed.)",
  "published": "2026-08-10T13:20:00Z",
  "severity": "Moderate",
  "cvss": 7.8,
  "cvssVector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
  "epss": 0.00135,
  "epssPercentile": 0.02982,
  "priority": "High",
  "priorityTier": 3,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "vendorAdvisory": "https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-68147",
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 12.15 (bookworm)",
      "fixedVersion": "6.1.187-1",
      "fix": "DEBIAN-CVE-2026-68147",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2026-68147",
      "released": "2026-08-11T16:03:09Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 13.5 (trixie)",
      "fixedVersion": "6.12.101-1",
      "fix": "DEBIAN-CVE-2026-68147",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2026-68147",
      "released": "2026-08-11T16:03:09Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "7.1.6-1",
      "fix": "DEBIAN-CVE-2026-68147",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2026-68147",
      "released": "2026-08-11T16:03:09Z"
    },
    {
      "platform": "linux",
      "product": "linux-6.12",
      "release": "Debian 12.15 (bookworm)",
      "fixedVersion": "6.12.101-1~deb12u1",
      "fix": "DEBIAN-CVE-2026-68147",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2026-68147",
      "released": "2026-08-11T16:03:09Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-08T06:59:42Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}