CVE-2024-36963 (GCVE-0-2024-36963)
Vulnerability from cvelistv5
Published
2024-06-03 07:50
Modified
2026-08-05 11:32
Summary
In the Linux kernel, the following vulnerability has been resolved: tracefs: Reset permissions on remount if permissions are options There's an inconsistency with the way permissions are handled in tracefs. Because the permissions are generated when accessed, they default to the root inode's permission if they were never set by the user. If the user sets the permissions, then a flag is set and the permissions are saved via the inode (for tracefs files) or an internal attribute field (for eventfs). But if a remount happens that specify the permissions, all the files that were not changed by the user gets updated, but the ones that were are not. If the user were to remount the file system with a given permission, then all files and directories within that file system should be updated. This can cause security issues if a file's permission was updated but the admin forgot about it. They could incorrectly think that remounting with permissions set would update all files, but miss some. For example: # cd /sys/kernel/tracing # chgrp 1002 current_tracer # ls -l [..] -rw-r----- 1 root root 0 May 1 21:25 buffer_size_kb -rw-r----- 1 root root 0 May 1 21:25 buffer_subbuf_size_kb -r--r----- 1 root root 0 May 1 21:25 buffer_total_size_kb -rw-r----- 1 root lkp 0 May 1 21:25 current_tracer -rw-r----- 1 root root 0 May 1 21:25 dynamic_events -r--r----- 1 root root 0 May 1 21:25 dyn_ftrace_total_info -r--r----- 1 root root 0 May 1 21:25 enabled_functions Where current_tracer now has group "lkp". # mount -o remount,gid=1001 . # ls -l -rw-r----- 1 root tracing 0 May 1 21:25 buffer_size_kb -rw-r----- 1 root tracing 0 May 1 21:25 buffer_subbuf_size_kb -r--r----- 1 root tracing 0 May 1 21:25 buffer_total_size_kb -rw-r----- 1 root lkp 0 May 1 21:25 current_tracer -rw-r----- 1 root tracing 0 May 1 21:25 dynamic_events -r--r----- 1 root tracing 0 May 1 21:25 dyn_ftrace_total_info -r--r----- 1 root tracing 0 May 1 21:25 enabled_functions Everything changed but the "current_tracer". Add a new link list that keeps track of all the tracefs_inodes which has the permission flags that tell if the file/dir should use the root inode's permission or not. Then on remount, clear all the flags so that the default behavior of using the root inode's permission is done for all files and directories.
Impacted products
Vendor Product Version
Linux Linux Version: 628adb842bd5e1c2c598534a7a022b8235289de6
Version: 8186fff7ab649085e2c60d032d9a20a85af1d87c
Version: 8186fff7ab649085e2c60d032d9a20a85af1d87c
Version: 9c2ac5e0ea7899411fd900d4681890722a020735
Version: 6.6.18   
Version: 6.7.4   
Create a notification for this product.
Show details on NVD website


{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "cvssV3_1": {
              "attackComplexity": "LOW",
              "attackVector": "LOCAL",
              "availabilityImpact": "HIGH",
              "baseScore": 7.8,
              "baseSeverity": "HIGH",
              "confidentialityImpact": "HIGH",
              "integrityImpact": "HIGH",
              "privilegesRequired": "LOW",
              "scope": "UNCHANGED",
              "userInteraction": "NONE",
              "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
              "version": "3.1"
            }
          },
          {
            "other": {
              "content": {
                "id": "CVE-2024-36963",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "total"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2025-05-20T14:06:38.590905Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "problemTypes": [
          {
            "descriptions": [
              {
                "cweId": "CWE-863",
                "description": "CWE-863 Incorrect Authorization",
                "lang": "en",
                "type": "CWE"
              }
            ]
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2025-05-20T14:07:59.778Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      },
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-02T03:43:50.371Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/5f91fc82794d4a6e41cdcd02d00baa377d94ca78"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/414fb08628143203d29ccd0264b5a83fb9523c03"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/baa23a8d4360d981a49913841a726edede5cdd54"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "fs/tracefs/event_inode.c",
            "fs/tracefs/inode.c",
            "fs/tracefs/internal.h"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "5f91fc82794d4a6e41cdcd02d00baa377d94ca78",
              "status": "affected",
              "version": "628adb842bd5e1c2c598534a7a022b8235289de6",
              "versionType": "git"
            },
            {
              "lessThan": "414fb08628143203d29ccd0264b5a83fb9523c03",
              "status": "affected",
              "version": "8186fff7ab649085e2c60d032d9a20a85af1d87c",
              "versionType": "git"
            },
            {
              "lessThan": "baa23a8d4360d981a49913841a726edede5cdd54",
              "status": "affected",
              "version": "8186fff7ab649085e2c60d032d9a20a85af1d87c",
              "versionType": "git"
            },
            {
              "status": "affected",
              "version": "9c2ac5e0ea7899411fd900d4681890722a020735",
              "versionType": "git"
            },
            {
              "lessThan": "6.6.31",
              "status": "affected",
              "version": "6.6.18",
              "versionType": "semver"
            },
            {
              "lessThan": "6.8",
              "status": "affected",
              "version": "6.7.4",
              "versionType": "semver"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "fs/tracefs/event_inode.c",
            "fs/tracefs/inode.c",
            "fs/tracefs/internal.h"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.8"
            },
            {
              "lessThan": "6.8",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.31",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.8.*",
              "status": "unaffected",
              "version": "6.8.10",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.9",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.6.31",
                  "versionStartIncluding": "6.6.18",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.8.10",
                  "versionStartIncluding": "6.8",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.9",
                  "versionStartIncluding": "6.8",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionStartIncluding": "6.7.4",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ntracefs: Reset permissions on remount if permissions are options\n\nThere\u0027s an inconsistency with the way permissions are handled in tracefs.\nBecause the permissions are generated when accessed, they default to the\nroot inode\u0027s permission if they were never set by the user. If the user\nsets the permissions, then a flag is set and the permissions are saved via\nthe inode (for tracefs files) or an internal attribute field (for\neventfs).\n\nBut if a remount happens that specify the permissions, all the files that\nwere not changed by the user gets updated, but the ones that were are not.\nIf the user were to remount the file system with a given permission, then\nall files and directories within that file system should be updated.\n\nThis can cause security issues if a file\u0027s permission was updated but the\nadmin forgot about it. They could incorrectly think that remounting with\npermissions set would update all files, but miss some.\n\nFor example:\n\n # cd /sys/kernel/tracing\n # chgrp 1002 current_tracer\n # ls -l\n[..]\n -rw-r-----  1 root root 0 May  1 21:25 buffer_size_kb\n -rw-r-----  1 root root 0 May  1 21:25 buffer_subbuf_size_kb\n -r--r-----  1 root root 0 May  1 21:25 buffer_total_size_kb\n -rw-r-----  1 root lkp  0 May  1 21:25 current_tracer\n -rw-r-----  1 root root 0 May  1 21:25 dynamic_events\n -r--r-----  1 root root 0 May  1 21:25 dyn_ftrace_total_info\n -r--r-----  1 root root 0 May  1 21:25 enabled_functions\n\nWhere current_tracer now has group \"lkp\".\n\n # mount -o remount,gid=1001 .\n # ls -l\n -rw-r-----  1 root tracing 0 May  1 21:25 buffer_size_kb\n -rw-r-----  1 root tracing 0 May  1 21:25 buffer_subbuf_size_kb\n -r--r-----  1 root tracing 0 May  1 21:25 buffer_total_size_kb\n -rw-r-----  1 root lkp     0 May  1 21:25 current_tracer\n -rw-r-----  1 root tracing 0 May  1 21:25 dynamic_events\n -r--r-----  1 root tracing 0 May  1 21:25 dyn_ftrace_total_info\n -r--r-----  1 root tracing 0 May  1 21:25 enabled_functions\n\nEverything changed but the \"current_tracer\".\n\nAdd a new link list that keeps track of all the tracefs_inodes which has\nthe permission flags that tell if the file/dir should use the root inode\u0027s\npermission or not. Then on remount, clear all the flags so that the\ndefault behavior of using the root inode\u0027s permission is done for all\nfiles and directories."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7.8,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:L - The flaw is reached through ordinary filesystem operations on tracefs (open/read/write/stat, chown) at /sys/kernel/tracing, which requires a local account on the system. There is no network-reachable path to tracefs permission handling.\nAC:L - The stale-permission condition is deterministic \u2014 no race, no memory-layout or timing dependency \u2014 and the attacker can set the pinning flag themselves, since fs/attr.c:chown_ok() allows an owner\u0027s no-op self-chown and chgrp_ok() allows an owner chgrp to their own group, so a granted user can pin every tracefs file at will. Remounting with uid=/gid= is the documented, routinely used way to manage tracefs ownership, so the exploited state arises in normal administration.\nPR:L - The attacker needs only an unprivileged local account that holds (or previously held) tracefs access via the uid=/gid= mount option or the tracing group; no CAP_SYS_ADMIN, CAP_CHOWN or root is required, because setting the pinning flag is permitted to the file\u0027s own owner. Root privileges are never needed on the attacker\u0027s side.\nUI:N - Once the file system is in the vulnerable state, the attacker simply exercises retained read/write access to tracefs with no action required from any other user. The administrator\u0027s remount is a routine configuration operation that establishes the state, not an attacker-induced victim interaction at exploitation time.\nS:U - The unauthorized access and its consequences stay within the kernel/OS security authority managing tracefs; no VM, IOMMU, or container-host boundary is crossed.\nC:H - Retained access to tracefs yields the ring buffer (`trace`, `trace_pipe`, `trace_pipe_raw`) containing kernel addresses and other processes\u0027 syscall data, and writable `kprobe_events`/`dynamic_events` gives probe fetch arguments that dereference and dump arbitrary kernel memory \u2014 an effective arbitrary kernel-read primitive that also defeats KASLR.\nI:H - Group/owner write access is retained on 0640 control files, letting the attacker install kprobes/uprobes, switch tracers, rewrite `set_ftrace_filter` and event filters/triggers, and clear or inject ring-buffer records \u2014 modifying kernel-wide tracing behavior and destroying trace/audit evidence that the administrator believed was locked down.\nA:H - Retained write access to `buffer_size_kb`/per-CPU `buffer_size_kb` permits allocating enormous per-CPU ring buffers leading to memory exhaustion and OOM kills, and enabling global function/function_graph tracing degrades the entire system, so a complete denial of service is achievable."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T11:32:17.919Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/5f91fc82794d4a6e41cdcd02d00baa377d94ca78"
        },
        {
          "url": "https://git.kernel.org/stable/c/414fb08628143203d29ccd0264b5a83fb9523c03"
        },
        {
          "url": "https://git.kernel.org/stable/c/baa23a8d4360d981a49913841a726edede5cdd54"
        }
      ],
      "title": "tracefs: Reset permissions on remount if permissions are options",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2024-36963",
    "datePublished": "2024-06-03T07:50:01.125Z",
    "dateReserved": "2024-05-30T15:25:07.081Z",
    "dateUpdated": "2026-08-05T11:32:17.919Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "vulnrichment": {
      "containers": "{\"adp\": [{\"title\": \"CVE Program Container\", \"references\": [{\"url\": \"https://git.kernel.org/stable/c/5f91fc82794d4a6e41cdcd02d00baa377d94ca78\", \"tags\": [\"x_transferred\"]}, {\"url\": \"https://git.kernel.org/stable/c/414fb08628143203d29ccd0264b5a83fb9523c03\", \"tags\": [\"x_transferred\"]}, {\"url\": \"https://git.kernel.org/stable/c/baa23a8d4360d981a49913841a726edede5cdd54\", \"tags\": [\"x_transferred\"]}], \"providerMetadata\": {\"orgId\": \"af854a3a-2127-422b-91ae-364da2661108\", \"shortName\": \"CVE\", \"dateUpdated\": \"2024-08-02T03:43:50.371Z\"}}, {\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"cvssV3_1\": {\"scope\": \"UNCHANGED\", \"version\": \"3.1\", \"baseScore\": 7.8, \"attackVector\": \"LOCAL\", \"baseSeverity\": \"HIGH\", \"vectorString\": \"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\", \"integrityImpact\": \"HIGH\", \"userInteraction\": \"NONE\", \"attackComplexity\": \"LOW\", \"availabilityImpact\": \"HIGH\", \"privilegesRequired\": \"LOW\", \"confidentialityImpact\": \"HIGH\"}}, {\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2024-36963\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"total\"}], \"version\": \"2.0.3\", \"timestamp\": \"2025-05-20T14:06:38.590905Z\"}}}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-863\", \"description\": \"CWE-863 Incorrect Authorization\"}]}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2024-06-04T15:38:05.479Z\"}}], \"cna\": {\"title\": \"tracefs: Reset permissions on remount if permissions are options\", \"affected\": [{\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"628adb842bd5e1c2c598534a7a022b8235289de6\", \"lessThan\": \"5f91fc82794d4a6e41cdcd02d00baa377d94ca78\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"8186fff7ab649085e2c60d032d9a20a85af1d87c\", \"lessThan\": \"414fb08628143203d29ccd0264b5a83fb9523c03\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"8186fff7ab649085e2c60d032d9a20a85af1d87c\", \"lessThan\": \"baa23a8d4360d981a49913841a726edede5cdd54\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"9c2ac5e0ea7899411fd900d4681890722a020735\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"6.6.18\", \"lessThan\": \"6.6.31\", \"versionType\": \"semver\"}, {\"status\": \"affected\", \"version\": \"6.7.4\", \"lessThan\": \"6.8\", \"versionType\": \"semver\"}], \"programFiles\": [\"fs/tracefs/event_inode.c\", \"fs/tracefs/inode.c\", \"fs/tracefs/internal.h\"], \"defaultStatus\": \"unaffected\"}, {\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"6.8\"}, {\"status\": \"unaffected\", \"version\": \"0\", \"lessThan\": \"6.8\", \"versionType\": \"semver\"}, {\"status\": \"unaffected\", \"version\": \"6.6.31\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.6.*\"}, {\"status\": \"unaffected\", \"version\": \"6.8.10\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.8.*\"}, {\"status\": \"unaffected\", \"version\": \"6.9\", \"versionType\": \"original_commit_for_fix\", \"lessThanOrEqual\": \"*\"}], \"programFiles\": [\"fs/tracefs/event_inode.c\", \"fs/tracefs/inode.c\", \"fs/tracefs/internal.h\"], \"defaultStatus\": \"affected\"}], \"references\": [{\"url\": \"https://git.kernel.org/stable/c/5f91fc82794d4a6e41cdcd02d00baa377d94ca78\"}, {\"url\": \"https://git.kernel.org/stable/c/414fb08628143203d29ccd0264b5a83fb9523c03\"}, {\"url\": \"https://git.kernel.org/stable/c/baa23a8d4360d981a49913841a726edede5cdd54\"}], \"x_generator\": {\"engine\": \"bippy-1.2.0\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\ntracefs: Reset permissions on remount if permissions are options\\n\\nThere\u0027s an inconsistency with the way permissions are handled in tracefs.\\nBecause the permissions are generated when accessed, they default to the\\nroot inode\u0027s permission if they were never set by the user. If the user\\nsets the permissions, then a flag is set and the permissions are saved via\\nthe inode (for tracefs files) or an internal attribute field (for\\neventfs).\\n\\nBut if a remount happens that specify the permissions, all the files that\\nwere not changed by the user gets updated, but the ones that were are not.\\nIf the user were to remount the file system with a given permission, then\\nall files and directories within that file system should be updated.\\n\\nThis can cause security issues if a file\u0027s permission was updated but the\\nadmin forgot about it. They could incorrectly think that remounting with\\npermissions set would update all files, but miss some.\\n\\nFor example:\\n\\n # cd /sys/kernel/tracing\\n # chgrp 1002 current_tracer\\n # ls -l\\n[..]\\n -rw-r-----  1 root root 0 May  1 21:25 buffer_size_kb\\n -rw-r-----  1 root root 0 May  1 21:25 buffer_subbuf_size_kb\\n -r--r-----  1 root root 0 May  1 21:25 buffer_total_size_kb\\n -rw-r-----  1 root lkp  0 May  1 21:25 current_tracer\\n -rw-r-----  1 root root 0 May  1 21:25 dynamic_events\\n -r--r-----  1 root root 0 May  1 21:25 dyn_ftrace_total_info\\n -r--r-----  1 root root 0 May  1 21:25 enabled_functions\\n\\nWhere current_tracer now has group \\\"lkp\\\".\\n\\n # mount -o remount,gid=1001 .\\n # ls -l\\n -rw-r-----  1 root tracing 0 May  1 21:25 buffer_size_kb\\n -rw-r-----  1 root tracing 0 May  1 21:25 buffer_subbuf_size_kb\\n -r--r-----  1 root tracing 0 May  1 21:25 buffer_total_size_kb\\n -rw-r-----  1 root lkp     0 May  1 21:25 current_tracer\\n -rw-r-----  1 root tracing 0 May  1 21:25 dynamic_events\\n -r--r-----  1 root tracing 0 May  1 21:25 dyn_ftrace_total_info\\n -r--r-----  1 root tracing 0 May  1 21:25 enabled_functions\\n\\nEverything changed but the \\\"current_tracer\\\".\\n\\nAdd a new link list that keeps track of all the tracefs_inodes which has\\nthe permission flags that tell if the file/dir should use the root inode\u0027s\\npermission or not. Then on remount, clear all the flags so that the\\ndefault behavior of using the root inode\u0027s permission is done for all\\nfiles and directories.\"}], \"cpeApplicability\": [{\"nodes\": [{\"negate\": false, \"cpeMatch\": [{\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.6.31\", \"versionStartIncluding\": \"6.6.18\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.8.10\", \"versionStartIncluding\": \"6.8\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.9\", \"versionStartIncluding\": \"6.8\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionStartIncluding\": \"6.7.4\"}], \"operator\": \"OR\"}]}], \"providerMetadata\": {\"orgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"shortName\": \"Linux\", \"dateUpdated\": \"2026-05-23T15:48:01.182Z\"}}}",
      "cveMetadata": "{\"cveId\": \"CVE-2024-36963\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2026-05-23T15:48:01.182Z\", \"dateReserved\": \"2024-05-30T15:25:07.081Z\", \"assignerOrgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"datePublished\": \"2024-06-03T07:50:01.125Z\", \"assignerShortName\": \"Linux\"}",
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.


Loading…

Loading…