CVE-2024-56779 (GCVE-0-2024-56779)

Vulnerability from cvelistv5 – Published: 2025-01-08 17:49 – Updated: 2026-08-05 11:46
VLAI
Title
nfsd: fix nfs4_openowner leak when concurrent nfsd4_open occur
Summary
In the Linux kernel, the following vulnerability has been resolved: nfsd: fix nfs4_openowner leak when concurrent nfsd4_open occur The action force umount(umount -f) will attempt to kill all rpc_task even umount operation may ultimately fail if some files remain open. Consequently, if an action attempts to open a file, it can potentially send two rpc_task to nfs server. NFS CLIENT thread1 thread2 open("file") ... nfs4_do_open _nfs4_do_open _nfs4_open_and_get_state _nfs4_proc_open nfs4_run_open_task /* rpc_task1 */ rpc_run_task rpc_wait_for_completion_task umount -f nfs_umount_begin rpc_killall_tasks rpc_signal_task rpc_task1 been wakeup and return -512 _nfs4_do_open // while loop ... nfs4_run_open_task /* rpc_task2 */ rpc_run_task rpc_wait_for_completion_task While processing an open request, nfsd will first attempt to find or allocate an nfs4_openowner. If it finds an nfs4_openowner that is not marked as NFS4_OO_CONFIRMED, this nfs4_openowner will released. Since two rpc_task can attempt to open the same file simultaneously from the client to server, and because two instances of nfsd can run concurrently, this situation can lead to lots of memory leak. Additionally, when we echo 0 to /proc/fs/nfsd/threads, warning will be triggered. NFS SERVER nfsd1 nfsd2 echo 0 > /proc/fs/nfsd/threads nfsd4_open nfsd4_process_open1 find_or_alloc_open_stateowner // alloc oo1, stateid1 nfsd4_open nfsd4_process_open1 find_or_alloc_open_stateowner // find oo1, without NFS4_OO_CONFIRMED release_openowner unhash_openowner_locked list_del_init(&oo->oo_perclient) // cannot find this oo // from client, LEAK!!! alloc_stateowner // alloc oo2 nfsd4_process_open2 init_open_stateid // associate oo1 // with stateid1, stateid1 LEAK!!! nfs4_get_vfs_file // alloc nfsd_file1 and nfsd_file_mark1 // all LEAK!!! nfsd4_process_open2 ... write_threads ... nfsd_destroy_serv nfsd_shutdown_net nfs4_state_shutdown_net nfs4_state_destroy_net destroy_client __destroy_client // won't find oo1!!! nfsd_shutdown_generic nfsd_file_cache_shutdown kmem_cache_destroy for nfsd_file_slab and nfsd_file_mark_slab // bark since nfsd_file1 // and nfsd_file_mark1 // still alive ======================================================================= BUG nfsd_file (Not tainted): Objects remaining in nfsd_file on __kmem_cache_shutdown() ----------------------------------------------------------------------- Slab 0xffd4000004438a80 objects=34 used=1 fp=0xff11000110e2ad28 flags=0x17ffffc0000240(workingset|head|node=0|zone=2|lastcpupid=0x1fffff) CPU: 4 UID: 0 PID: 757 Comm: sh Not tainted 6.12.0-rc6+ #19 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.1-2.fc37 04/01/2014 Call Trace: <TASK> dum ---truncated---
Severity
9.8 (Critical)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
5.5 (Medium)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
SSVC
Exploitation: none Automatable: no Technical Impact: partial
CISA Coordinator (v2.0.3)
CWE
  • CWE-401 - Missing Release of Memory after Effective Lifetime
Assigner
References
Impacted products
Vendor Product Version
Linux Linux Affected: 3234975f477f746c22d076ea178a79ea104b2ca7 , < a85364f0d30dee01c5d5b4afa55a9629a8f36d8e (git)
Affected: 3234975f477f746c22d076ea178a79ea104b2ca7 , < 2d505a801e57428057563762f67a5a62009b2600 (git)
Affected: 3234975f477f746c22d076ea178a79ea104b2ca7 , < 0ab0a3ad24e970e894abcac58f85c332d1726749 (git)
Affected: 3234975f477f746c22d076ea178a79ea104b2ca7 , < 45abb68c941ebc9a35c6d3a7b08196712093c636 (git)
Affected: 3234975f477f746c22d076ea178a79ea104b2ca7 , < 37dfc81266d3a32294524bfadd3396614f8633ee (git)
Affected: 3234975f477f746c22d076ea178a79ea104b2ca7 , < 6f73f920b7ad0084373e46121d7ac34117aed652 (git)
Affected: 3234975f477f746c22d076ea178a79ea104b2ca7 , < 98100e88dd8865999dc6379a3356cd799795fe7b (git)
Create a notification for this product.
Linux Linux Affected: 3.17
Unaffected: 0 , < 3.17 (semver)
Unaffected: 5.4.287 , ≤ 5.4.* (semver)
Unaffected: 5.10.231 , ≤ 5.10.* (semver)
Unaffected: 5.15.174 , ≤ 5.15.* (semver)
Unaffected: 6.1.120 , ≤ 6.1.* (semver)
Unaffected: 6.6.64 , ≤ 6.6.* (semver)
Unaffected: 6.12.4 , ≤ 6.12.* (semver)
Unaffected: 6.13 , ≤ * (original_commit_for_fix)
Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "cvssV3_1": {
              "attackComplexity": "LOW",
              "attackVector": "LOCAL",
              "availabilityImpact": "HIGH",
              "baseScore": 5.5,
              "baseSeverity": "MEDIUM",
              "confidentialityImpact": "NONE",
              "integrityImpact": "NONE",
              "privilegesRequired": "LOW",
              "scope": "UNCHANGED",
              "userInteraction": "NONE",
              "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
              "version": "3.1"
            }
          },
          {
            "other": {
              "content": {
                "id": "CVE-2024-56779",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2025-10-01T19:56:28.713212Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "problemTypes": [
          {
            "descriptions": [
              {
                "cweId": "CWE-401",
                "description": "CWE-401 Missing Release of Memory after Effective Lifetime",
                "lang": "en",
                "type": "CWE"
              }
            ]
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2025-10-01T19:57:24.125Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      },
      {
        "providerMetadata": {
          "dateUpdated": "2025-11-03T20:54:16.750Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "url": "https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html"
          },
          {
            "url": "https://lists.debian.org/debian-lts-announce/2025/03/msg00002.html"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "fs/nfsd/nfs4state.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "a85364f0d30dee01c5d5b4afa55a9629a8f36d8e",
              "status": "affected",
              "version": "3234975f477f746c22d076ea178a79ea104b2ca7",
              "versionType": "git"
            },
            {
              "lessThan": "2d505a801e57428057563762f67a5a62009b2600",
              "status": "affected",
              "version": "3234975f477f746c22d076ea178a79ea104b2ca7",
              "versionType": "git"
            },
            {
              "lessThan": "0ab0a3ad24e970e894abcac58f85c332d1726749",
              "status": "affected",
              "version": "3234975f477f746c22d076ea178a79ea104b2ca7",
              "versionType": "git"
            },
            {
              "lessThan": "45abb68c941ebc9a35c6d3a7b08196712093c636",
              "status": "affected",
              "version": "3234975f477f746c22d076ea178a79ea104b2ca7",
              "versionType": "git"
            },
            {
              "lessThan": "37dfc81266d3a32294524bfadd3396614f8633ee",
              "status": "affected",
              "version": "3234975f477f746c22d076ea178a79ea104b2ca7",
              "versionType": "git"
            },
            {
              "lessThan": "6f73f920b7ad0084373e46121d7ac34117aed652",
              "status": "affected",
              "version": "3234975f477f746c22d076ea178a79ea104b2ca7",
              "versionType": "git"
            },
            {
              "lessThan": "98100e88dd8865999dc6379a3356cd799795fe7b",
              "status": "affected",
              "version": "3234975f477f746c22d076ea178a79ea104b2ca7",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "fs/nfsd/nfs4state.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "3.17"
            },
            {
              "lessThan": "3.17",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "5.4.*",
              "status": "unaffected",
              "version": "5.4.287",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "5.10.*",
              "status": "unaffected",
              "version": "5.10.231",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "5.15.*",
              "status": "unaffected",
              "version": "5.15.174",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.1.*",
              "status": "unaffected",
              "version": "6.1.120",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.64",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.4",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.13",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.4.287",
                  "versionStartIncluding": "3.17",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.10.231",
                  "versionStartIncluding": "3.17",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.15.174",
                  "versionStartIncluding": "3.17",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.1.120",
                  "versionStartIncluding": "3.17",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.6.64",
                  "versionStartIncluding": "3.17",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.4",
                  "versionStartIncluding": "3.17",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.13",
                  "versionStartIncluding": "3.17",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnfsd: fix nfs4_openowner leak when concurrent nfsd4_open occur\n\nThe action force umount(umount -f) will attempt to kill all rpc_task even\numount operation may ultimately fail if some files remain open.\nConsequently, if an action attempts to open a file, it can potentially\nsend two rpc_task to nfs server.\n\n                   NFS CLIENT\nthread1                             thread2\nopen(\"file\")\n...\nnfs4_do_open\n _nfs4_do_open\n  _nfs4_open_and_get_state\n   _nfs4_proc_open\n    nfs4_run_open_task\n     /* rpc_task1 */\n     rpc_run_task\n     rpc_wait_for_completion_task\n\n                                    umount -f\n                                    nfs_umount_begin\n                                     rpc_killall_tasks\n                                      rpc_signal_task\n     rpc_task1 been wakeup\n     and return -512\n _nfs4_do_open // while loop\n    ...\n    nfs4_run_open_task\n     /* rpc_task2 */\n     rpc_run_task\n     rpc_wait_for_completion_task\n\nWhile processing an open request, nfsd will first attempt to find or\nallocate an nfs4_openowner. If it finds an nfs4_openowner that is not\nmarked as NFS4_OO_CONFIRMED, this nfs4_openowner will released. Since\ntwo rpc_task can attempt to open the same file simultaneously from the\nclient to server, and because two instances of nfsd can run\nconcurrently, this situation can lead to lots of memory leak.\nAdditionally, when we echo 0 to /proc/fs/nfsd/threads, warning will be\ntriggered.\n\n                    NFS SERVER\nnfsd1                  nfsd2       echo 0 \u003e /proc/fs/nfsd/threads\n\nnfsd4_open\n nfsd4_process_open1\n  find_or_alloc_open_stateowner\n   // alloc oo1, stateid1\n                       nfsd4_open\n                        nfsd4_process_open1\n                        find_or_alloc_open_stateowner\n                        // find oo1, without NFS4_OO_CONFIRMED\n                         release_openowner\n                          unhash_openowner_locked\n                          list_del_init(\u0026oo-\u003eoo_perclient)\n                          // cannot find this oo\n                          // from client, LEAK!!!\n                         alloc_stateowner // alloc oo2\n\n nfsd4_process_open2\n  init_open_stateid\n  // associate oo1\n  // with stateid1, stateid1 LEAK!!!\n  nfs4_get_vfs_file\n  // alloc nfsd_file1 and nfsd_file_mark1\n  // all LEAK!!!\n\n                         nfsd4_process_open2\n                         ...\n\n                                    write_threads\n                                     ...\n                                     nfsd_destroy_serv\n                                      nfsd_shutdown_net\n                                       nfs4_state_shutdown_net\n                                        nfs4_state_destroy_net\n                                         destroy_client\n                                          __destroy_client\n                                          // won\u0027t find oo1!!!\n                                     nfsd_shutdown_generic\n                                      nfsd_file_cache_shutdown\n                                       kmem_cache_destroy\n                                       for nfsd_file_slab\n                                       and nfsd_file_mark_slab\n                                       // bark since nfsd_file1\n                                       // and nfsd_file_mark1\n                                       // still alive\n\n=======================================================================\nBUG nfsd_file (Not tainted): Objects remaining in nfsd_file on\n__kmem_cache_shutdown()\n-----------------------------------------------------------------------\n\nSlab 0xffd4000004438a80 objects=34 used=1 fp=0xff11000110e2ad28\nflags=0x17ffffc0000240(workingset|head|node=0|zone=2|lastcpupid=0x1fffff)\nCPU: 4 UID: 0 PID: 757 Comm: sh Not tainted 6.12.0-rc6+ #19\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS\n1.16.1-2.fc37 04/01/2014\nCall Trace:\n \u003cTASK\u003e\n dum\n---truncated---"
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 9.8,
            "baseSeverity": "CRITICAL",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:N - The vulnerable code is nfsd\u0027s NFSv4 OPEN handler, reached from `svc_process()` \u2192 `nfsd_dispatch()` \u2192 `nfsd4_proc_compound()` \u2192 `nfsd4_open()` on data received from a remote NFS client over routable TCP port 2049. No local access or network adjacency is required.\nAC:L - The attacker owns both sides of the race \u2014 it simply opens two TCP connections under one clientid and issues two concurrent NFSv4.0 COMPOUND OPENs carrying the same fresh (unconfirmed) open_owner, and the default 8 nfsd threads guarantee parallel service. The window spans all of `nfsd4_process_open2()` including the VFS open and disk I/O, and a failed attempt costs nothing and can be retried indefinitely.\nPR:N - NFS with the default AUTH_SYS flavour performs no authentication whatsoever \u2014 the client self-asserts its uid \u2014 so any host permitted by the export list (routinely a whole subnet or `*`) can issue SETCLIENTID, PUTROOTFH/LOOKUP and OPEN with no credentials verified. Nothing on the path to `find_or_alloc_open_stateowner()` checks any capability or privilege.\nUI:N - The attacker\u0027s own client issues both concurrent OPEN requests and the later conflicting OPEN entirely on its own initiative; no action by a local user or administrator is needed to trigger the leak or reach the stale stateid.\nS:U - The leaked objects, the dangling `nfs4_client` pointer and any resulting panic all remain inside the kernel\u0027s own security authority on the NFS server host. No VM, IOMMU or sandbox boundary is crossed.\nC:H - The leak breaks the invariant that all stateids are destroyed before `free_client()`, leaving `stp-\u003est_stid.sc_client` dangling after routine lease expiry while `stp` keeps `fp` hashed in the global `nfs4_file_rhltable`; a later OPEN with a conflicting share mode reads that freed `nfs4_client` in `nfs4_resolve_deny_conflicts_locked()`. Unauthenticated SETCLIENTID lets the attacker spray `client_slab` to control and observe the reclaimed object, and per kernel guidance a use-after-free is scored High.\nI:H - `try_to_expire_client()` performs a `cmpxchg()` on `clp-\u003ecl_state` of the freed, attacker-groomable `nfs4_client`, giving a write primitive into reclaimed heap memory. Additionally the leaked `nfsd_file_mark` survives `nfsd_file_cache_shutdown()` as a live fsnotify mark whose group ops point into nfsd module text, corrupting control flow if the module is later unloaded.\nA:H - Each won race permanently leaks an openowner, stateid, `nfs4_file`, `nfsd_file`, `nfsd_file_mark` and an open `struct file` that pins the inode, dentry and mount, so a remote client looping the race exhausts kernel memory and file references and makes the exported filesystem unmountable. On top of that, `kmem_cache_destroy()` fires `WARN(err, \"Slab cache still has objects\u2026\")` at nfsd shutdown \u2014 an immediate panic under `panic_on_warn=1` \u2014 and the use-after-free itself crashes the server."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T11:46:27.780Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/a85364f0d30dee01c5d5b4afa55a9629a8f36d8e"
        },
        {
          "url": "https://git.kernel.org/stable/c/2d505a801e57428057563762f67a5a62009b2600"
        },
        {
          "url": "https://git.kernel.org/stable/c/0ab0a3ad24e970e894abcac58f85c332d1726749"
        },
        {
          "url": "https://git.kernel.org/stable/c/45abb68c941ebc9a35c6d3a7b08196712093c636"
        },
        {
          "url": "https://git.kernel.org/stable/c/37dfc81266d3a32294524bfadd3396614f8633ee"
        },
        {
          "url": "https://git.kernel.org/stable/c/6f73f920b7ad0084373e46121d7ac34117aed652"
        },
        {
          "url": "https://git.kernel.org/stable/c/98100e88dd8865999dc6379a3356cd799795fe7b"
        }
      ],
      "title": "nfsd: fix nfs4_openowner leak when concurrent nfsd4_open occur",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2024-56779",
    "datePublished": "2025-01-08T17:49:17.070Z",
    "dateReserved": "2024-12-29T11:26:39.767Z",
    "dateUpdated": "2026-08-05T11:46:27.780Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2024-56779",
      "date": "2026-08-09",
      "epss": "0.00531",
      "percentile": "0.42013"
    },
    "fkie_nvd": {
      "configurations": "[{\"nodes\": [{\"operator\": \"OR\", \"negate\": false, \"cpeMatch\": [{\"vulnerable\": true, \"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"versionEndExcluding\": \"5.4.287\", \"matchCriteriaId\": \"DC7D5C80-B677-4131-A399-3366D7F3961C\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"versionStartIncluding\": \"5.5\", \"versionEndExcluding\": \"5.10.231\", \"matchCriteriaId\": \"B5C644CC-2BD7-4E32-BC54-8DCC7ABE9935\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"versionStartIncluding\": \"5.11\", \"versionEndExcluding\": \"5.15.174\", \"matchCriteriaId\": \"419FD073-1517-4FD5-8158-F94BC68A1E89\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"versionStartIncluding\": \"5.16\", \"versionEndExcluding\": \"6.1.120\", \"matchCriteriaId\": \"09AC6122-E2A4-40FE-9D33-268A1B2EC265\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"versionStartIncluding\": \"6.2\", \"versionEndExcluding\": \"6.6.64\", \"matchCriteriaId\": \"CA16DEE3-ABEC-4449-9F4A-7A3DC4FC36C7\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"versionStartIncluding\": \"6.7\", \"versionEndExcluding\": \"6.12.4\", \"matchCriteriaId\": \"04756810-D093-4B43-B1D9-CF5035968061\"}]}]}]",
      "descriptions": "[{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\nnfsd: fix nfs4_openowner leak when concurrent nfsd4_open occur\\n\\nThe action force umount(umount -f) will attempt to kill all rpc_task even\\numount operation may ultimately fail if some files remain open.\\nConsequently, if an action attempts to open a file, it can potentially\\nsend two rpc_task to nfs server.\\n\\n                   NFS CLIENT\\nthread1                             thread2\\nopen(\\\"file\\\")\\n...\\nnfs4_do_open\\n _nfs4_do_open\\n  _nfs4_open_and_get_state\\n   _nfs4_proc_open\\n    nfs4_run_open_task\\n     /* rpc_task1 */\\n     rpc_run_task\\n     rpc_wait_for_completion_task\\n\\n                                    umount -f\\n                                    nfs_umount_begin\\n                                     rpc_killall_tasks\\n                                      rpc_signal_task\\n     rpc_task1 been wakeup\\n     and return -512\\n _nfs4_do_open // while loop\\n    ...\\n    nfs4_run_open_task\\n     /* rpc_task2 */\\n     rpc_run_task\\n     rpc_wait_for_completion_task\\n\\nWhile processing an open request, nfsd will first attempt to find or\\nallocate an nfs4_openowner. If it finds an nfs4_openowner that is not\\nmarked as NFS4_OO_CONFIRMED, this nfs4_openowner will released. Since\\ntwo rpc_task can attempt to open the same file simultaneously from the\\nclient to server, and because two instances of nfsd can run\\nconcurrently, this situation can lead to lots of memory leak.\\nAdditionally, when we echo 0 to /proc/fs/nfsd/threads, warning will be\\ntriggered.\\n\\n                    NFS SERVER\\nnfsd1                  nfsd2       echo 0 \u003e /proc/fs/nfsd/threads\\n\\nnfsd4_open\\n nfsd4_process_open1\\n  find_or_alloc_open_stateowner\\n   // alloc oo1, stateid1\\n                       nfsd4_open\\n                        nfsd4_process_open1\\n                        find_or_alloc_open_stateowner\\n                        // find oo1, without NFS4_OO_CONFIRMED\\n                         release_openowner\\n                          unhash_openowner_locked\\n                          list_del_init(\u0026oo-\u003eoo_perclient)\\n                          // cannot find this oo\\n                          // from client, LEAK!!!\\n                         alloc_stateowner // alloc oo2\\n\\n nfsd4_process_open2\\n  init_open_stateid\\n  // associate oo1\\n  // with stateid1, stateid1 LEAK!!!\\n  nfs4_get_vfs_file\\n  // alloc nfsd_file1 and nfsd_file_mark1\\n  // all LEAK!!!\\n\\n                         nfsd4_process_open2\\n                         ...\\n\\n                                    write_threads\\n                                     ...\\n                                     nfsd_destroy_serv\\n                                      nfsd_shutdown_net\\n                                       nfs4_state_shutdown_net\\n                                        nfs4_state_destroy_net\\n                                         destroy_client\\n                                          __destroy_client\\n                                          // won\u0027t find oo1!!!\\n                                     nfsd_shutdown_generic\\n                                      nfsd_file_cache_shutdown\\n                                       kmem_cache_destroy\\n                                       for nfsd_file_slab\\n                                       and nfsd_file_mark_slab\\n                                       // bark since nfsd_file1\\n                                       // and nfsd_file_mark1\\n                                       // still alive\\n\\n=======================================================================\\nBUG nfsd_file (Not tainted): Objects remaining in nfsd_file on\\n__kmem_cache_shutdown()\\n-----------------------------------------------------------------------\\n\\nSlab 0xffd4000004438a80 objects=34 used=1 fp=0xff11000110e2ad28\\nflags=0x17ffffc0000240(workingset|head|node=0|zone=2|lastcpupid=0x1fffff)\\nCPU: 4 UID: 0 PID: 757 Comm: sh Not tainted 6.12.0-rc6+ #19\\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS\\n1.16.1-2.fc37 04/01/2014\\nCall Trace:\\n \u003cTASK\u003e\\n dum\\n---truncated---\"}, {\"lang\": \"es\", \"value\": \"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: nfsd: se corrige la p\\u00e9rdida de nfs4_openowner cuando se producen nfsd4_open concurrentes. La acci\\u00f3n force umount(umount -f) intentar\\u00e1 eliminar todas las rpc_task, aunque la operaci\\u00f3n umount puede fallar si algunos archivos permanecen abiertos. En consecuencia, si una acci\\u00f3n intenta abrir un archivo, puede enviar dos rpc_task al servidor nfs. CLIENTE NFS thread1 thread2 open(\\\"archivo\\\") ... nfs4_do_open _nfs4_do_open _nfs4_open_and_get_state _nfs4_proc_open nfs4_run_open_task /* rpc_task1 */ rpc_run_task rpc_wait_for_completion_task umount -f nfs_umount_begin rpc_killall_tasks rpc_signal_task rpc_task1 se ha activado y ha devuelto -512 _nfs4_do_open // bucle while ... nfs4_run_open_task /* rpc_task2 */ rpc_run_task rpc_wait_for_completion_task Mientras se procesa una solicitud de apertura, nfsd primero intentar\\u00e1 encontrar o asignar un nfs4_openowner. Si encuentra un nfs4_openowner que no est\\u00e9 marcado como NFS4_OO_CONFIRMED, este nfs4_openowner se liberar\\u00e1. Dado que dos rpc_task pueden intentar abrir el mismo archivo simult\\u00e1neamente desde el cliente al servidor, y debido a que dos instancias de nfsd pueden ejecutarse simult\\u00e1neamente, esta situaci\\u00f3n puede provocar una gran p\\u00e9rdida de memoria. Adem\\u00e1s, cuando hacemos eco de 0 en /proc/fs/nfsd/threads, se activar\\u00e1 una advertencia. SERVIDOR NFS nfsd1 nfsd2 echo 0 \u0026gt; /proc/fs/nfsd/threads nfsd4_open nfsd4_process_open1 find_or_alloc_open_stateowner // asignar oo1, stateid1 nfsd4_open nfsd4_process_open1 find_or_alloc_open_stateowner // encontrar oo1, sin NFS4_OO_CONFIRMED release_openowner unhash_openowner_locked list_del_init(\u0026amp;oo-\u0026gt;oo_perclient) // no se puede encontrar este oo // del cliente, \\u00a1FUGA! alloc_stateowner // asignar oo2 nfsd4_process_open2 init_open_stateid // asociar oo1 // con stateid1, stateid1 \\u00a1FUGA! nfs4_get_vfs_file // asignar nfsd_file1 y nfsd_file_mark1 // \\u00a1\\u00a1\\u00a1TODOS FUGAN!!! nfsd4_process_open2 ... subprocesos de escritura ... nfsd_destroy_serv nfsd_shutdown_net nfs4_state_shutdown_net nfs4_state_destroy_net destroy_client __destroy_client // \\u00a1\\u00a1\\u00a1No encontrar\\u00e1 oo1!!! nfsd_shutdown_generic nfsd_file_cache_shutdown kmem_cache_destroy para nfsd_file_slab y nfsd_file_mark_slab // sin cambios desde nfsd_file1 // y nfsd_file_mark1 // siguen activos ============================================================================ ERROR nfsd_file (no contaminado): objetos que permanecen en nfsd_file en __kmem_cache_shutdown() ----------------------------------------------------------------------- Slab 0xffd4000004438a80 objetos=34 usados=1 fp=0xff11000110e2ad28 flags=0x17ffffc0000240(workingset|head|node=0|zone=2|lastcpupid=0x1fffff) CPU: 4 UID: 0 PID: 757 Comm: sh No contaminado 6.12.0-rc6+ #19 Nombre del hardware: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.1-2.fc37 01/04/2014 Seguimiento de llamadas:  dum ---truncado---\"}]",
      "id": "CVE-2024-56779",
      "lastModified": "2025-01-09T21:48:56.667",
      "metrics": "{\"cvssMetricV31\": [{\"source\": \"nvd@nist.gov\", \"type\": \"Primary\", \"cvssData\": {\"version\": \"3.1\", \"vectorString\": \"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\", \"baseScore\": 5.5, \"baseSeverity\": \"MEDIUM\", \"attackVector\": \"LOCAL\", \"attackComplexity\": \"LOW\", \"privilegesRequired\": \"LOW\", \"userInteraction\": \"NONE\", \"scope\": \"UNCHANGED\", \"confidentialityImpact\": \"NONE\", \"integrityImpact\": \"NONE\", \"availabilityImpact\": \"HIGH\"}, \"exploitabilityScore\": 1.8, \"impactScore\": 3.6}]}",
      "published": "2025-01-08T18:15:18.793",
      "references": "[{\"url\": \"https://git.kernel.org/stable/c/0ab0a3ad24e970e894abcac58f85c332d1726749\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"tags\": [\"Patch\"]}, {\"url\": \"https://git.kernel.org/stable/c/2d505a801e57428057563762f67a5a62009b2600\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"tags\": [\"Patch\"]}, {\"url\": \"https://git.kernel.org/stable/c/37dfc81266d3a32294524bfadd3396614f8633ee\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"tags\": [\"Patch\"]}, {\"url\": \"https://git.kernel.org/stable/c/45abb68c941ebc9a35c6d3a7b08196712093c636\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"tags\": [\"Patch\"]}, {\"url\": \"https://git.kernel.org/stable/c/6f73f920b7ad0084373e46121d7ac34117aed652\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"tags\": [\"Patch\"]}, {\"url\": \"https://git.kernel.org/stable/c/98100e88dd8865999dc6379a3356cd799795fe7b\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"tags\": [\"Patch\"]}, {\"url\": \"https://git.kernel.org/stable/c/a85364f0d30dee01c5d5b4afa55a9629a8f36d8e\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"tags\": [\"Patch\"]}]",
      "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "vulnStatus": "Analyzed",
      "weaknesses": "[{\"source\": \"nvd@nist.gov\", \"type\": \"Primary\", \"description\": [{\"lang\": \"en\", \"value\": \"CWE-401\"}]}]"
    },
    "microsoft_vex": {
      "current_release_date": "2025-03-08T00:00:00.000Z",
      "cve": "CVE-2024-56779",
      "id": "msrc_CVE-2024-56779",
      "initial_release_date": "2025-01-02T00:00:00.000Z",
      "product_status:fixed": "4",
      "product_status:known_affected": "4",
      "source": "Microsoft CSAF VEX",
      "status": "final",
      "title": "nfsd: fix nfs4_openowner leak when concurrent nfsd4_open occur",
      "url": "https://msrc.microsoft.com/csaf/vex/2025/msrc_cve-2024-56779.json",
      "version": "2"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2024-56779\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2025-01-08T18:15:18.793\",\"lastModified\":\"2026-08-04T11:22:26.920\",\"vulnStatus\":\"Modified\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nnfsd: fix nfs4_openowner leak when concurrent nfsd4_open occur\\n\\nThe action force umount(umount -f) will attempt to kill all rpc_task even\\numount operation may ultimately fail if some files remain open.\\nConsequently, if an action attempts to open a file, it can potentially\\nsend two rpc_task to nfs server.\\n\\n                   NFS CLIENT\\nthread1                             thread2\\nopen(\\\"file\\\")\\n...\\nnfs4_do_open\\n _nfs4_do_open\\n  _nfs4_open_and_get_state\\n   _nfs4_proc_open\\n    nfs4_run_open_task\\n     /* rpc_task1 */\\n     rpc_run_task\\n     rpc_wait_for_completion_task\\n\\n                                    umount -f\\n                                    nfs_umount_begin\\n                                     rpc_killall_tasks\\n                                      rpc_signal_task\\n     rpc_task1 been wakeup\\n     and return -512\\n _nfs4_do_open // while loop\\n    ...\\n    nfs4_run_open_task\\n     /* rpc_task2 */\\n     rpc_run_task\\n     rpc_wait_for_completion_task\\n\\nWhile processing an open request, nfsd will first attempt to find or\\nallocate an nfs4_openowner. If it finds an nfs4_openowner that is not\\nmarked as NFS4_OO_CONFIRMED, this nfs4_openowner will released. Since\\ntwo rpc_task can attempt to open the same file simultaneously from the\\nclient to server, and because two instances of nfsd can run\\nconcurrently, this situation can lead to lots of memory leak.\\nAdditionally, when we echo 0 to /proc/fs/nfsd/threads, warning will be\\ntriggered.\\n\\n                    NFS SERVER\\nnfsd1                  nfsd2       echo 0 \u003e /proc/fs/nfsd/threads\\n\\nnfsd4_open\\n nfsd4_process_open1\\n  find_or_alloc_open_stateowner\\n   // alloc oo1, stateid1\\n                       nfsd4_open\\n                        nfsd4_process_open1\\n                        find_or_alloc_open_stateowner\\n                        // find oo1, without NFS4_OO_CONFIRMED\\n                         release_openowner\\n                          unhash_openowner_locked\\n                          list_del_init(\u0026oo-\u003eoo_perclient)\\n                          // cannot find this oo\\n                          // from client, LEAK!!!\\n                         alloc_stateowner // alloc oo2\\n\\n nfsd4_process_open2\\n  init_open_stateid\\n  // associate oo1\\n  // with stateid1, stateid1 LEAK!!!\\n  nfs4_get_vfs_file\\n  // alloc nfsd_file1 and nfsd_file_mark1\\n  // all LEAK!!!\\n\\n                         nfsd4_process_open2\\n                         ...\\n\\n                                    write_threads\\n                                     ...\\n                                     nfsd_destroy_serv\\n                                      nfsd_shutdown_net\\n                                       nfs4_state_shutdown_net\\n                                        nfs4_state_destroy_net\\n                                         destroy_client\\n                                          __destroy_client\\n                                          // won\u0027t find oo1!!!\\n                                     nfsd_shutdown_generic\\n                                      nfsd_file_cache_shutdown\\n                                       kmem_cache_destroy\\n                                       for nfsd_file_slab\\n                                       and nfsd_file_mark_slab\\n                                       // bark since nfsd_file1\\n                                       // and nfsd_file_mark1\\n                                       // still alive\\n\\n=======================================================================\\nBUG nfsd_file (Not tainted): Objects remaining in nfsd_file on\\n__kmem_cache_shutdown()\\n-----------------------------------------------------------------------\\n\\nSlab 0xffd4000004438a80 objects=34 used=1 fp=0xff11000110e2ad28\\nflags=0x17ffffc0000240(workingset|head|node=0|zone=2|lastcpupid=0x1fffff)\\nCPU: 4 UID: 0 PID: 757 Comm: sh Not tainted 6.12.0-rc6+ #19\\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS\\n1.16.1-2.fc37 04/01/2014\\nCall Trace:\\n \u003cTASK\u003e\\n dum\\n---truncated---\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: nfsd: se corrige la p\u00e9rdida de nfs4_openowner cuando se producen nfsd4_open concurrentes. La acci\u00f3n force umount(umount -f) intentar\u00e1 eliminar todas las rpc_task, aunque la operaci\u00f3n umount puede fallar si algunos archivos permanecen abiertos. En consecuencia, si una acci\u00f3n intenta abrir un archivo, puede enviar dos rpc_task al servidor nfs. CLIENTE NFS thread1 thread2 open(\\\"archivo\\\") ... nfs4_do_open _nfs4_do_open _nfs4_open_and_get_state _nfs4_proc_open nfs4_run_open_task /* rpc_task1 */ rpc_run_task rpc_wait_for_completion_task umount -f nfs_umount_begin rpc_killall_tasks rpc_signal_task rpc_task1 se ha activado y ha devuelto -512 _nfs4_do_open // bucle while ... nfs4_run_open_task /* rpc_task2 */ rpc_run_task rpc_wait_for_completion_task Mientras se procesa una solicitud de apertura, nfsd primero intentar\u00e1 encontrar o asignar un nfs4_openowner. Si encuentra un nfs4_openowner que no est\u00e9 marcado como NFS4_OO_CONFIRMED, este nfs4_openowner se liberar\u00e1. Dado que dos rpc_task pueden intentar abrir el mismo archivo simult\u00e1neamente desde el cliente al servidor, y debido a que dos instancias de nfsd pueden ejecutarse simult\u00e1neamente, esta situaci\u00f3n puede provocar una gran p\u00e9rdida de memoria. Adem\u00e1s, cuando hacemos eco de 0 en /proc/fs/nfsd/threads, se activar\u00e1 una advertencia. SERVIDOR NFS nfsd1 nfsd2 echo 0 \u0026gt; /proc/fs/nfsd/threads nfsd4_open nfsd4_process_open1 find_or_alloc_open_stateowner // asignar oo1, stateid1 nfsd4_open nfsd4_process_open1 find_or_alloc_open_stateowner // encontrar oo1, sin NFS4_OO_CONFIRMED release_openowner unhash_openowner_locked list_del_init(\u0026amp;oo-\u0026gt;oo_perclient) // no se puede encontrar este oo // del cliente, \u00a1FUGA! alloc_stateowner // asignar oo2 nfsd4_process_open2 init_open_stateid // asociar oo1 // con stateid1, stateid1 \u00a1FUGA! nfs4_get_vfs_file // asignar nfsd_file1 y nfsd_file_mark1 // \u00a1\u00a1\u00a1TODOS FUGAN!!! nfsd4_process_open2 ... subprocesos de escritura ... nfsd_destroy_serv nfsd_shutdown_net nfs4_state_shutdown_net nfs4_state_destroy_net destroy_client __destroy_client // \u00a1\u00a1\u00a1No encontrar\u00e1 oo1!!! nfsd_shutdown_generic nfsd_file_cache_shutdown kmem_cache_destroy para nfsd_file_slab y nfsd_file_mark_slab // sin cambios desde nfsd_file1 // y nfsd_file_mark1 // siguen activos ============================================================================ ERROR nfsd_file (no contaminado): objetos que permanecen en nfsd_file en __kmem_cache_shutdown() ----------------------------------------------------------------------- Slab 0xffd4000004438a80 objetos=34 usados=1 fp=0xff11000110e2ad28 flags=0x17ffffc0000240(workingset|head|node=0|zone=2|lastcpupid=0x1fffff) CPU: 4 UID: 0 PID: 757 Comm: sh No contaminado 6.12.0-rc6+ #19 Nombre del hardware: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.1-2.fc37 01/04/2014 Seguimiento de llamadas:  dum ---truncado---\"}],\"affected\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"affectedData\":[{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"unaffected\",\"programFiles\":[\"fs/nfsd/nfs4state.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"3234975f477f746c22d076ea178a79ea104b2ca7\",\"lessThan\":\"a85364f0d30dee01c5d5b4afa55a9629a8f36d8e\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"3234975f477f746c22d076ea178a79ea104b2ca7\",\"lessThan\":\"2d505a801e57428057563762f67a5a62009b2600\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"3234975f477f746c22d076ea178a79ea104b2ca7\",\"lessThan\":\"0ab0a3ad24e970e894abcac58f85c332d1726749\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"3234975f477f746c22d076ea178a79ea104b2ca7\",\"lessThan\":\"45abb68c941ebc9a35c6d3a7b08196712093c636\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"3234975f477f746c22d076ea178a79ea104b2ca7\",\"lessThan\":\"37dfc81266d3a32294524bfadd3396614f8633ee\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"3234975f477f746c22d076ea178a79ea104b2ca7\",\"lessThan\":\"6f73f920b7ad0084373e46121d7ac34117aed652\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"3234975f477f746c22d076ea178a79ea104b2ca7\",\"lessThan\":\"98100e88dd8865999dc6379a3356cd799795fe7b\",\"versionType\":\"git\",\"status\":\"affected\"}]},{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"affected\",\"programFiles\":[\"fs/nfsd/nfs4state.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"3.17\",\"status\":\"affected\"},{\"version\":\"0\",\"lessThan\":\"3.17\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"5.4.287\",\"lessThanOrEqual\":\"5.4.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"5.10.231\",\"lessThanOrEqual\":\"5.10.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"5.15.174\",\"lessThanOrEqual\":\"5.15.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.1.120\",\"lessThanOrEqual\":\"6.1.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.6.64\",\"lessThanOrEqual\":\"6.6.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.12.4\",\"lessThanOrEqual\":\"6.12.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.13\",\"lessThanOrEqual\":\"*\",\"versionType\":\"original_commit_for_fix\",\"status\":\"unaffected\"}]}]}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H\",\"baseScore\":9.8,\"baseSeverity\":\"CRITICAL\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"NONE\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"HIGH\",\"integrityImpact\":\"HIGH\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":3.9,\"impactScore\":5.9},{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\",\"baseScore\":5.5,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":1.8,\"impactScore\":3.6},{\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\",\"baseScore\":5.5,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":1.8,\"impactScore\":3.6}],\"ssvcV203\":[{\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\",\"ssvcData\":{\"timestamp\":\"2025-10-01T19:56:28.713212Z\",\"id\":\"CVE-2024-56779\",\"options\":[{\"exploitation\":\"none\"},{\"automatable\":\"no\"},{\"technicalImpact\":\"partial\"}],\"role\":\"CISA Coordinator\",\"version\":\"2.0.3\"}}]},\"weaknesses\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-401\"}]},{\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\",\"type\":\"Secondary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-401\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionEndExcluding\":\"5.4.287\",\"matchCriteriaId\":\"DC7D5C80-B677-4131-A399-3366D7F3961C\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"5.5\",\"versionEndExcluding\":\"5.10.231\",\"matchCriteriaId\":\"B5C644CC-2BD7-4E32-BC54-8DCC7ABE9935\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"5.11\",\"versionEndExcluding\":\"5.15.174\",\"matchCriteriaId\":\"419FD073-1517-4FD5-8158-F94BC68A1E89\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"5.16\",\"versionEndExcluding\":\"6.1.120\",\"matchCriteriaId\":\"09AC6122-E2A4-40FE-9D33-268A1B2EC265\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.2\",\"versionEndExcluding\":\"6.6.64\",\"matchCriteriaId\":\"CA16DEE3-ABEC-4449-9F4A-7A3DC4FC36C7\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.7\",\"versionEndExcluding\":\"6.12.4\",\"matchCriteriaId\":\"04756810-D093-4B43-B1D9-CF5035968061\"}]}]}],\"references\":[{\"url\":\"https://git.kernel.org/stable/c/0ab0a3ad24e970e894abcac58f85c332d1726749\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/2d505a801e57428057563762f67a5a62009b2600\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/37dfc81266d3a32294524bfadd3396614f8633ee\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/45abb68c941ebc9a35c6d3a7b08196712093c636\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/6f73f920b7ad0084373e46121d7ac34117aed652\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/98100e88dd8865999dc6379a3356cd799795fe7b\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/a85364f0d30dee01c5d5b4afa55a9629a8f36d8e\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\"},{\"url\":\"https://lists.debian.org/debian-lts-announce/2025/03/msg00002.html\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\"}]}}",
    "redhat_vex": {
      "aggregate_severity": "Moderate",
      "current_release_date": "2026-06-28T08:17:52+00:00",
      "cve": "CVE-2024-56779",
      "id": "CVE-2024-56779",
      "initial_release_date": "2024-01-01T00:00:00+00:00",
      "product_status:fixed": "305",
      "product_status:known_affected": "112",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: nfsd: fix nfs4_openowner leak when concurrent nfsd4_open occur",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2024/cve-2024-56779.json",
      "version": "3"
    },
    "suse_vex": {
      "aggregate_severity": "moderate",
      "current_release_date": "2026-07-31T17:00:28Z",
      "cve": "CVE-2024-56779",
      "id": "CVE-2024-56779",
      "initial_release_date": "2025-01-09T00:20:31Z",
      "product_status:known_affected": "690",
      "product_status:known_not_affected": "36",
      "product_status:recommended": "443",
      "source": "SUSE CSAF VEX",
      "status": "interim",
      "title": "SUSE CVE CVE-2024-56779",
      "url": "https://ftp.suse.com/pub/projects/security/csaf-vex/cve-2024-56779.json",
      "version": "70"
    },
    "vulnrichment": {
      "containers": "{\"adp\": [{\"title\": \"CVE Program Container\", \"references\": [{\"url\": \"https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html\"}, {\"url\": \"https://lists.debian.org/debian-lts-announce/2025/03/msg00002.html\"}], \"providerMetadata\": {\"orgId\": \"af854a3a-2127-422b-91ae-364da2661108\", \"shortName\": \"CVE\", \"dateUpdated\": \"2025-11-03T20:54:16.750Z\"}}, {\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"cvssV3_1\": {\"scope\": \"UNCHANGED\", \"version\": \"3.1\", \"baseScore\": 5.5, \"attackVector\": \"LOCAL\", \"baseSeverity\": \"MEDIUM\", \"vectorString\": \"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\", \"integrityImpact\": \"NONE\", \"userInteraction\": \"NONE\", \"attackComplexity\": \"LOW\", \"availabilityImpact\": \"HIGH\", \"privilegesRequired\": \"LOW\", \"confidentialityImpact\": \"NONE\"}}, {\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2024-56779\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2025-10-01T19:56:28.713212Z\"}}}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-401\", \"description\": \"CWE-401 Missing Release of Memory after Effective Lifetime\"}]}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2025-10-01T15:51:12.801Z\"}}], \"cna\": {\"title\": \"nfsd: fix nfs4_openowner leak when concurrent nfsd4_open occur\", \"metrics\": [{\"cvssV3_1\": {\"version\": \"3.1\", \"baseScore\": 9.8, \"baseSeverity\": \"CRITICAL\", \"vectorString\": \"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H\"}, \"scenarios\": [{\"lang\": \"en\", \"value\": \"AV:N - The vulnerable code is nfsd\u0027s NFSv4 OPEN handler, reached from `svc_process()` \\u2192 `nfsd_dispatch()` \\u2192 `nfsd4_proc_compound()` \\u2192 `nfsd4_open()` on data received from a remote NFS client over routable TCP port 2049. No local access or network adjacency is required.\\nAC:L - The attacker owns both sides of the race \\u2014 it simply opens two TCP connections under one clientid and issues two concurrent NFSv4.0 COMPOUND OPENs carrying the same fresh (unconfirmed) open_owner, and the default 8 nfsd threads guarantee parallel service. The window spans all of `nfsd4_process_open2()` including the VFS open and disk I/O, and a failed attempt costs nothing and can be retried indefinitely.\\nPR:N - NFS with the default AUTH_SYS flavour performs no authentication whatsoever \\u2014 the client self-asserts its uid \\u2014 so any host permitted by the export list (routinely a whole subnet or `*`) can issue SETCLIENTID, PUTROOTFH/LOOKUP and OPEN with no credentials verified. Nothing on the path to `find_or_alloc_open_stateowner()` checks any capability or privilege.\\nUI:N - The attacker\u0027s own client issues both concurrent OPEN requests and the later conflicting OPEN entirely on its own initiative; no action by a local user or administrator is needed to trigger the leak or reach the stale stateid.\\nS:U - The leaked objects, the dangling `nfs4_client` pointer and any resulting panic all remain inside the kernel\u0027s own security authority on the NFS server host. No VM, IOMMU or sandbox boundary is crossed.\\nC:H - The leak breaks the invariant that all stateids are destroyed before `free_client()`, leaving `stp-\u003est_stid.sc_client` dangling after routine lease expiry while `stp` keeps `fp` hashed in the global `nfs4_file_rhltable`; a later OPEN with a conflicting share mode reads that freed `nfs4_client` in `nfs4_resolve_deny_conflicts_locked()`. Unauthenticated SETCLIENTID lets the attacker spray `client_slab` to control and observe the reclaimed object, and per kernel guidance a use-after-free is scored High.\\nI:H - `try_to_expire_client()` performs a `cmpxchg()` on `clp-\u003ecl_state` of the freed, attacker-groomable `nfs4_client`, giving a write primitive into reclaimed heap memory. Additionally the leaked `nfsd_file_mark` survives `nfsd_file_cache_shutdown()` as a live fsnotify mark whose group ops point into nfsd module text, corrupting control flow if the module is later unloaded.\\nA:H - Each won race permanently leaks an openowner, stateid, `nfs4_file`, `nfsd_file`, `nfsd_file_mark` and an open `struct file` that pins the inode, dentry and mount, so a remote client looping the race exhausts kernel memory and file references and makes the exported filesystem unmountable. On top of that, `kmem_cache_destroy()` fires `WARN(err, \\\"Slab cache still has objects\\u2026\\\")` at nfsd shutdown \\u2014 an immediate panic under `panic_on_warn=1` \\u2014 and the use-after-free itself crashes the server.\"}]}], \"affected\": [{\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"3234975f477f746c22d076ea178a79ea104b2ca7\", \"lessThan\": \"a85364f0d30dee01c5d5b4afa55a9629a8f36d8e\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"3234975f477f746c22d076ea178a79ea104b2ca7\", \"lessThan\": \"2d505a801e57428057563762f67a5a62009b2600\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"3234975f477f746c22d076ea178a79ea104b2ca7\", \"lessThan\": \"0ab0a3ad24e970e894abcac58f85c332d1726749\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"3234975f477f746c22d076ea178a79ea104b2ca7\", \"lessThan\": \"45abb68c941ebc9a35c6d3a7b08196712093c636\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"3234975f477f746c22d076ea178a79ea104b2ca7\", \"lessThan\": \"37dfc81266d3a32294524bfadd3396614f8633ee\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"3234975f477f746c22d076ea178a79ea104b2ca7\", \"lessThan\": \"6f73f920b7ad0084373e46121d7ac34117aed652\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"3234975f477f746c22d076ea178a79ea104b2ca7\", \"lessThan\": \"98100e88dd8865999dc6379a3356cd799795fe7b\", \"versionType\": \"git\"}], \"programFiles\": [\"fs/nfsd/nfs4state.c\"], \"defaultStatus\": \"unaffected\"}, {\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"3.17\"}, {\"status\": \"unaffected\", \"version\": \"0\", \"lessThan\": \"3.17\", \"versionType\": \"semver\"}, {\"status\": \"unaffected\", \"version\": \"5.4.287\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"5.4.*\"}, {\"status\": \"unaffected\", \"version\": \"5.10.231\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"5.10.*\"}, {\"status\": \"unaffected\", \"version\": \"5.15.174\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"5.15.*\"}, {\"status\": \"unaffected\", \"version\": \"6.1.120\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.1.*\"}, {\"status\": \"unaffected\", \"version\": \"6.6.64\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.6.*\"}, {\"status\": \"unaffected\", \"version\": \"6.12.4\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.12.*\"}, {\"status\": \"unaffected\", \"version\": \"6.13\", \"versionType\": \"original_commit_for_fix\", \"lessThanOrEqual\": \"*\"}], \"programFiles\": [\"fs/nfsd/nfs4state.c\"], \"defaultStatus\": \"affected\"}], \"references\": [{\"url\": \"https://git.kernel.org/stable/c/a85364f0d30dee01c5d5b4afa55a9629a8f36d8e\"}, {\"url\": \"https://git.kernel.org/stable/c/2d505a801e57428057563762f67a5a62009b2600\"}, {\"url\": \"https://git.kernel.org/stable/c/0ab0a3ad24e970e894abcac58f85c332d1726749\"}, {\"url\": \"https://git.kernel.org/stable/c/45abb68c941ebc9a35c6d3a7b08196712093c636\"}, {\"url\": \"https://git.kernel.org/stable/c/37dfc81266d3a32294524bfadd3396614f8633ee\"}, {\"url\": \"https://git.kernel.org/stable/c/6f73f920b7ad0084373e46121d7ac34117aed652\"}, {\"url\": \"https://git.kernel.org/stable/c/98100e88dd8865999dc6379a3356cd799795fe7b\"}], \"x_generator\": {\"engine\": \"bippy-1.2.0\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\nnfsd: fix nfs4_openowner leak when concurrent nfsd4_open occur\\n\\nThe action force umount(umount -f) will attempt to kill all rpc_task even\\numount operation may ultimately fail if some files remain open.\\nConsequently, if an action attempts to open a file, it can potentially\\nsend two rpc_task to nfs server.\\n\\n                   NFS CLIENT\\nthread1                             thread2\\nopen(\\\"file\\\")\\n...\\nnfs4_do_open\\n _nfs4_do_open\\n  _nfs4_open_and_get_state\\n   _nfs4_proc_open\\n    nfs4_run_open_task\\n     /* rpc_task1 */\\n     rpc_run_task\\n     rpc_wait_for_completion_task\\n\\n                                    umount -f\\n                                    nfs_umount_begin\\n                                     rpc_killall_tasks\\n                                      rpc_signal_task\\n     rpc_task1 been wakeup\\n     and return -512\\n _nfs4_do_open // while loop\\n    ...\\n    nfs4_run_open_task\\n     /* rpc_task2 */\\n     rpc_run_task\\n     rpc_wait_for_completion_task\\n\\nWhile processing an open request, nfsd will first attempt to find or\\nallocate an nfs4_openowner. If it finds an nfs4_openowner that is not\\nmarked as NFS4_OO_CONFIRMED, this nfs4_openowner will released. Since\\ntwo rpc_task can attempt to open the same file simultaneously from the\\nclient to server, and because two instances of nfsd can run\\nconcurrently, this situation can lead to lots of memory leak.\\nAdditionally, when we echo 0 to /proc/fs/nfsd/threads, warning will be\\ntriggered.\\n\\n                    NFS SERVER\\nnfsd1                  nfsd2       echo 0 \u003e /proc/fs/nfsd/threads\\n\\nnfsd4_open\\n nfsd4_process_open1\\n  find_or_alloc_open_stateowner\\n   // alloc oo1, stateid1\\n                       nfsd4_open\\n                        nfsd4_process_open1\\n                        find_or_alloc_open_stateowner\\n                        // find oo1, without NFS4_OO_CONFIRMED\\n                         release_openowner\\n                          unhash_openowner_locked\\n                          list_del_init(\u0026oo-\u003eoo_perclient)\\n                          // cannot find this oo\\n                          // from client, LEAK!!!\\n                         alloc_stateowner // alloc oo2\\n\\n nfsd4_process_open2\\n  init_open_stateid\\n  // associate oo1\\n  // with stateid1, stateid1 LEAK!!!\\n  nfs4_get_vfs_file\\n  // alloc nfsd_file1 and nfsd_file_mark1\\n  // all LEAK!!!\\n\\n                         nfsd4_process_open2\\n                         ...\\n\\n                                    write_threads\\n                                     ...\\n                                     nfsd_destroy_serv\\n                                      nfsd_shutdown_net\\n                                       nfs4_state_shutdown_net\\n                                        nfs4_state_destroy_net\\n                                         destroy_client\\n                                          __destroy_client\\n                                          // won\u0027t find oo1!!!\\n                                     nfsd_shutdown_generic\\n                                      nfsd_file_cache_shutdown\\n                                       kmem_cache_destroy\\n                                       for nfsd_file_slab\\n                                       and nfsd_file_mark_slab\\n                                       // bark since nfsd_file1\\n                                       // and nfsd_file_mark1\\n                                       // still alive\\n\\n=======================================================================\\nBUG nfsd_file (Not tainted): Objects remaining in nfsd_file on\\n__kmem_cache_shutdown()\\n-----------------------------------------------------------------------\\n\\nSlab 0xffd4000004438a80 objects=34 used=1 fp=0xff11000110e2ad28\\nflags=0x17ffffc0000240(workingset|head|node=0|zone=2|lastcpupid=0x1fffff)\\nCPU: 4 UID: 0 PID: 757 Comm: sh Not tainted 6.12.0-rc6+ #19\\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS\\n1.16.1-2.fc37 04/01/2014\\nCall Trace:\\n \u003cTASK\u003e\\n dum\\n---truncated---\"}], \"cpeApplicability\": [{\"nodes\": [{\"negate\": false, \"cpeMatch\": [{\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"5.4.287\", \"versionStartIncluding\": \"3.17\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"5.10.231\", \"versionStartIncluding\": \"3.17\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"5.15.174\", \"versionStartIncluding\": \"3.17\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.1.120\", \"versionStartIncluding\": \"3.17\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.6.64\", \"versionStartIncluding\": \"3.17\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.12.4\", \"versionStartIncluding\": \"3.17\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.13\", \"versionStartIncluding\": \"3.17\"}], \"operator\": \"OR\"}]}], \"providerMetadata\": {\"orgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"shortName\": \"Linux\", \"dateUpdated\": \"2026-08-05T11:46:27.780Z\"}}}",
      "cveMetadata": "{\"cveId\": \"CVE-2024-56779\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2026-08-05T11:46:27.780Z\", \"dateReserved\": \"2024-12-29T11:26:39.767Z\", \"assignerOrgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"datePublished\": \"2025-01-08T17:49:17.070Z\", \"assignerShortName\": \"Linux\"}",
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





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.


Detection rules are retrieved from Rulezet.