GHSA-48WQ-5H48-MWQQ

Vulnerability from github – Published: 2026-05-01 15:30 – Updated: 2026-05-06 21:31
VLAI?
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 <.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.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-31714"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-401"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-05-01T14:16:21Z",
    "severity": "MODERATE"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix to avoid memory leak in f2fs_rename()\n\nsyzbot reported a f2fs bug as below:\n\nBUG: memory leak\nunreferenced object 0xffff888127f70830 (size 16):\n  comm \"syz.0.23\", pid 6144, jiffies 4294943712\n  hex dump (first 16 bytes):\n    3c af 57 72 5b e6 8f ad 6e 8e fd 33 42 39 03 ff  \u003c.Wr[...n..3B9..\n  backtrace (crc 925f8a80):\n    kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]\n    slab_post_alloc_hook mm/slub.c:4520 [inline]\n    slab_alloc_node mm/slub.c:4844 [inline]\n    __do_kmalloc_node mm/slub.c:5237 [inline]\n    __kmalloc_noprof+0x3bd/0x560 mm/slub.c:5250\n    kmalloc_noprof include/linux/slab.h:954 [inline]\n    fscrypt_setup_filename+0x15e/0x3b0 fs/crypto/fname.c:364\n    f2fs_setup_filename+0x52/0xb0 fs/f2fs/dir.c:143\n    f2fs_rename+0x159/0xca0 fs/f2fs/namei.c:961\n    f2fs_rename2+0xd5/0xf20 fs/f2fs/namei.c:1308\n    vfs_rename+0x7ff/0x1250 fs/namei.c:6026\n    filename_renameat2+0x4f4/0x660 fs/namei.c:6144\n    __do_sys_renameat2 fs/namei.c:6173 [inline]\n    __se_sys_renameat2 fs/namei.c:6168 [inline]\n    __x64_sys_renameat2+0x59/0x80 fs/namei.c:6168\n    do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n    do_syscall_64+0xe2/0xf80 arch/x86/entry/syscall_64.c:94\n    entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nThe root cause is in commit 40b2d55e0452 (\"f2fs: fix to create selinux\nlabel during whiteout initialization\"), we added a call to\nf2fs_setup_filename() without a matching call to f2fs_free_filename(),\nfix it.",
  "id": "GHSA-48wq-5h48-mwqq",
  "modified": "2026-05-06T21:31:32Z",
  "published": "2026-05-01T15:30:33Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-31714"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/047c0aef6af37a2a35181aa085c616ad286386f1"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/369eb2016d8e2f01931b3bad1cb9cefa83f44003"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/3cf11e6f36c170050c12171dd6fd3142711478fc"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/a76c1cad4e80a9802ef8048662255417e3ce5b79"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/c78206dcb912ab60b8ee3cbe8c48d749a9a12e1e"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…