{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:13",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.12.85-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "7.0.3-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  f2fs: fix to avoid memory leak in f2fs_rename()  syzbot reported a f2fs bug as below:  BUG: memory leak unreferenced object 0xffff888127f70830 (size 16):   comm \"syz.0.23\", pid 6144, jiffies 4294943712   hex dump (first 16 bytes):     3c af 57 72 5b e6 8f ad 6e 8e fd 33 42 39 03 ff  \u003c.Wr[...n..3B9..   backtrace (crc 925f8a80):     kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]     slab_post_alloc_hook mm/slub.c:4520 [inline]     slab_alloc_node mm/slub.c:4844 [inline]     __do_kmalloc_node mm/slub.c:5237 [inline]     __kmalloc_noprof+0x3bd/0x560 mm/slub.c:5250     kmalloc_noprof include/linux/slab.h:954 [inline]     fscrypt_setup_filename+0x15e/0x3b0 fs/crypto/fname.c:364     f2fs_setup_filename+0x52/0xb0 fs/f2fs/dir.c:143     f2fs_rename+0x159/0xca0 fs/f2fs/namei.c:961     f2fs_rename2+0xd5/0xf20 fs/f2fs/namei.c:1308     vfs_rename+0x7ff/0x1250 fs/namei.c:6026     filename_renameat2+0x4f4/0x660 fs/namei.c:6144     __do_sys_renameat2 fs/namei.c:6173 [inline]     __se_sys_renameat2 fs/namei.c:6168 [inline]     __x64_sys_renameat2+0x59/0x80 fs/namei.c:6168     do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]     do_syscall_64+0xe2/0xf80 arch/x86/entry/syscall_64.c:94     entry_SYSCALL_64_after_hwframe+0x77/0x7f  The root cause is in commit 40b2d55e0452 (\"f2fs: fix to create selinux label during whiteout initialization\"), we added a call to f2fs_setup_filename() without a matching call to f2fs_free_filename(), fix it.",
  "id": "DEBIAN-CVE-2026-31714",
  "modified": "2026-09-14T16:47:32.919617029Z",
  "published": "2026-05-01T14:16:21.493Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-31714"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ],
  "upstream": [
    "CVE-2026-31714"
  ]
}