CVE-2024-50031 (GCVE-0-2024-50031)

Vulnerability from cvelistv5 – Published: 2024-10-21 19:39 – Updated: 2026-08-05 11:41
VLAI
Title
drm/v3d: Stop the active perfmon before being destroyed
Summary
In the Linux kernel, the following vulnerability has been resolved: drm/v3d: Stop the active perfmon before being destroyed When running `kmscube` with one or more performance monitors enabled via `GALLIUM_HUD`, the following kernel panic can occur: [ 55.008324] Unable to handle kernel paging request at virtual address 00000000052004a4 [ 55.008368] Mem abort info: [ 55.008377] ESR = 0x0000000096000005 [ 55.008387] EC = 0x25: DABT (current EL), IL = 32 bits [ 55.008402] SET = 0, FnV = 0 [ 55.008412] EA = 0, S1PTW = 0 [ 55.008421] FSC = 0x05: level 1 translation fault [ 55.008434] Data abort info: [ 55.008442] ISV = 0, ISS = 0x00000005, ISS2 = 0x00000000 [ 55.008455] CM = 0, WnR = 0, TnD = 0, TagAccess = 0 [ 55.008467] GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 [ 55.008481] user pgtable: 4k pages, 39-bit VAs, pgdp=00000001046c6000 [ 55.008497] [00000000052004a4] pgd=0000000000000000, p4d=0000000000000000, pud=0000000000000000 [ 55.008525] Internal error: Oops: 0000000096000005 [#1] PREEMPT SMP [ 55.008542] Modules linked in: rfcomm [...] vc4 v3d snd_soc_hdmi_codec drm_display_helper gpu_sched drm_shmem_helper cec drm_dma_helper drm_kms_helper i2c_brcmstb drm drm_panel_orientation_quirks snd_soc_core snd_compress snd_pcm_dmaengine snd_pcm snd_timer snd backlight [ 55.008799] CPU: 2 PID: 166 Comm: v3d_bin Tainted: G C 6.6.47+rpt-rpi-v8 #1 Debian 1:6.6.47-1+rpt1 [ 55.008824] Hardware name: Raspberry Pi 4 Model B Rev 1.5 (DT) [ 55.008838] pstate: 20000005 (nzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 55.008855] pc : __mutex_lock.constprop.0+0x90/0x608 [ 55.008879] lr : __mutex_lock.constprop.0+0x58/0x608 [ 55.008895] sp : ffffffc080673cf0 [ 55.008904] x29: ffffffc080673cf0 x28: 0000000000000000 x27: ffffff8106188a28 [ 55.008926] x26: ffffff8101e78040 x25: ffffff8101baa6c0 x24: ffffffd9d989f148 [ 55.008947] x23: ffffffda1c2a4008 x22: 0000000000000002 x21: ffffffc080673d38 [ 55.008968] x20: ffffff8101238000 x19: ffffff8104f83188 x18: 0000000000000000 [ 55.008988] x17: 0000000000000000 x16: ffffffda1bd04d18 x15: 00000055bb08bc90 [ 55.009715] x14: 0000000000000000 x13: 0000000000000000 x12: ffffffda1bd4cbb0 [ 55.010433] x11: 00000000fa83b2da x10: 0000000000001a40 x9 : ffffffda1bd04d04 [ 55.011162] x8 : ffffff8102097b80 x7 : 0000000000000000 x6 : 00000000030a5857 [ 55.011880] x5 : 00ffffffffffffff x4 : 0300000005200470 x3 : 0300000005200470 [ 55.012598] x2 : ffffff8101238000 x1 : 0000000000000021 x0 : 0300000005200470 [ 55.013292] Call trace: [ 55.013959] __mutex_lock.constprop.0+0x90/0x608 [ 55.014646] __mutex_lock_slowpath+0x1c/0x30 [ 55.015317] mutex_lock+0x50/0x68 [ 55.015961] v3d_perfmon_stop+0x40/0xe0 [v3d] [ 55.016627] v3d_bin_job_run+0x10c/0x2d8 [v3d] [ 55.017282] drm_sched_main+0x178/0x3f8 [gpu_sched] [ 55.017921] kthread+0x11c/0x128 [ 55.018554] ret_from_fork+0x10/0x20 [ 55.019168] Code: f9400260 f1001c1f 54001ea9 927df000 (b9403401) [ 55.019776] ---[ end trace 0000000000000000 ]--- [ 55.020411] note: v3d_bin[166] exited with preempt_count 1 This issue arises because, upon closing the file descriptor (which happens when we interrupt `kmscube`), the active performance monitor is not stopped. Although all perfmons are destroyed in `v3d_perfmon_close_file()`, the active performance monitor's pointer (`v3d->active_perfmon`) is still retained. If `kmscube` is run again, the driver will attempt to stop the active performance monitor using the stale pointer in `v3d->active_perfmon`. However, this pointer is no longer valid because the previous process has already terminated, and all performance monitors associated with it have been destroyed and freed. To fix this, when the active performance monitor belongs to a given process, explicitly stop it before destroying and freeing it.
Severity
7.8 (High)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
SSVC
Exploitation: none Automatable: no Technical Impact: partial
CISA Coordinator (v2.0.3)
Assigner
References
Impacted products
Vendor Product Version
Linux Linux Affected: 26a4dc29b74a137f45665089f6d3d633fcc9b662 , < 24ab54a066d2ef671b03eb909ca2114c0c9ac1e7 (git)
Affected: 26a4dc29b74a137f45665089f6d3d633fcc9b662 , < 0c9e9a3a4873705740b19300cadc6599170646ef (git)
Affected: 26a4dc29b74a137f45665089f6d3d633fcc9b662 , < 07c51108d9e278831c16191d1223ee49986e7890 (git)
Affected: 26a4dc29b74a137f45665089f6d3d633fcc9b662 , < 333767cbce6ac20ec794c76eec82ed0ef55022db (git)
Affected: 26a4dc29b74a137f45665089f6d3d633fcc9b662 , < 7d1fd3638ee3a9f9bca4785fffb638ca19120718 (git)
Create a notification for this product.
Linux Linux Affected: 5.15
Unaffected: 0 , < 5.15 (semver)
Unaffected: 5.15.168 , ≤ 5.15.* (semver)
Unaffected: 6.1.113 , ≤ 6.1.* (semver)
Unaffected: 6.6.57 , ≤ 6.6.* (semver)
Unaffected: 6.11.4 , ≤ 6.11.* (semver)
Unaffected: 6.12 , ≤ * (original_commit_for_fix)
Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2024-50031",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2024-10-22T13:26:04.844363Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2024-10-22T13:28:45.758Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      },
      {
        "providerMetadata": {
          "dateUpdated": "2025-11-03T22:24:37.994Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "url": "https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/gpu/drm/v3d/v3d_perfmon.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "24ab54a066d2ef671b03eb909ca2114c0c9ac1e7",
              "status": "affected",
              "version": "26a4dc29b74a137f45665089f6d3d633fcc9b662",
              "versionType": "git"
            },
            {
              "lessThan": "0c9e9a3a4873705740b19300cadc6599170646ef",
              "status": "affected",
              "version": "26a4dc29b74a137f45665089f6d3d633fcc9b662",
              "versionType": "git"
            },
            {
              "lessThan": "07c51108d9e278831c16191d1223ee49986e7890",
              "status": "affected",
              "version": "26a4dc29b74a137f45665089f6d3d633fcc9b662",
              "versionType": "git"
            },
            {
              "lessThan": "333767cbce6ac20ec794c76eec82ed0ef55022db",
              "status": "affected",
              "version": "26a4dc29b74a137f45665089f6d3d633fcc9b662",
              "versionType": "git"
            },
            {
              "lessThan": "7d1fd3638ee3a9f9bca4785fffb638ca19120718",
              "status": "affected",
              "version": "26a4dc29b74a137f45665089f6d3d633fcc9b662",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/gpu/drm/v3d/v3d_perfmon.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "5.15"
            },
            {
              "lessThan": "5.15",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "5.15.*",
              "status": "unaffected",
              "version": "5.15.168",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.1.*",
              "status": "unaffected",
              "version": "6.1.113",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.57",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.11.*",
              "status": "unaffected",
              "version": "6.11.4",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.12",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.15.168",
                  "versionStartIncluding": "5.15",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.1.113",
                  "versionStartIncluding": "5.15",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.6.57",
                  "versionStartIncluding": "5.15",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.11.4",
                  "versionStartIncluding": "5.15",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12",
                  "versionStartIncluding": "5.15",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/v3d: Stop the active perfmon before being destroyed\n\nWhen running `kmscube` with one or more performance monitors enabled\nvia `GALLIUM_HUD`, the following kernel panic can occur:\n\n[   55.008324] Unable to handle kernel paging request at virtual address 00000000052004a4\n[   55.008368] Mem abort info:\n[   55.008377]   ESR = 0x0000000096000005\n[   55.008387]   EC = 0x25: DABT (current EL), IL = 32 bits\n[   55.008402]   SET = 0, FnV = 0\n[   55.008412]   EA = 0, S1PTW = 0\n[   55.008421]   FSC = 0x05: level 1 translation fault\n[   55.008434] Data abort info:\n[   55.008442]   ISV = 0, ISS = 0x00000005, ISS2 = 0x00000000\n[   55.008455]   CM = 0, WnR = 0, TnD = 0, TagAccess = 0\n[   55.008467]   GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0\n[   55.008481] user pgtable: 4k pages, 39-bit VAs, pgdp=00000001046c6000\n[   55.008497] [00000000052004a4] pgd=0000000000000000, p4d=0000000000000000, pud=0000000000000000\n[   55.008525] Internal error: Oops: 0000000096000005 [#1] PREEMPT SMP\n[   55.008542] Modules linked in: rfcomm [...] vc4 v3d snd_soc_hdmi_codec drm_display_helper\ngpu_sched drm_shmem_helper cec drm_dma_helper drm_kms_helper i2c_brcmstb\ndrm drm_panel_orientation_quirks snd_soc_core snd_compress snd_pcm_dmaengine snd_pcm snd_timer snd backlight\n[   55.008799] CPU: 2 PID: 166 Comm: v3d_bin Tainted: G         C         6.6.47+rpt-rpi-v8 #1  Debian 1:6.6.47-1+rpt1\n[   55.008824] Hardware name: Raspberry Pi 4 Model B Rev 1.5 (DT)\n[   55.008838] pstate: 20000005 (nzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n[   55.008855] pc : __mutex_lock.constprop.0+0x90/0x608\n[   55.008879] lr : __mutex_lock.constprop.0+0x58/0x608\n[   55.008895] sp : ffffffc080673cf0\n[   55.008904] x29: ffffffc080673cf0 x28: 0000000000000000 x27: ffffff8106188a28\n[   55.008926] x26: ffffff8101e78040 x25: ffffff8101baa6c0 x24: ffffffd9d989f148\n[   55.008947] x23: ffffffda1c2a4008 x22: 0000000000000002 x21: ffffffc080673d38\n[   55.008968] x20: ffffff8101238000 x19: ffffff8104f83188 x18: 0000000000000000\n[   55.008988] x17: 0000000000000000 x16: ffffffda1bd04d18 x15: 00000055bb08bc90\n[   55.009715] x14: 0000000000000000 x13: 0000000000000000 x12: ffffffda1bd4cbb0\n[   55.010433] x11: 00000000fa83b2da x10: 0000000000001a40 x9 : ffffffda1bd04d04\n[   55.011162] x8 : ffffff8102097b80 x7 : 0000000000000000 x6 : 00000000030a5857\n[   55.011880] x5 : 00ffffffffffffff x4 : 0300000005200470 x3 : 0300000005200470\n[   55.012598] x2 : ffffff8101238000 x1 : 0000000000000021 x0 : 0300000005200470\n[   55.013292] Call trace:\n[   55.013959]  __mutex_lock.constprop.0+0x90/0x608\n[   55.014646]  __mutex_lock_slowpath+0x1c/0x30\n[   55.015317]  mutex_lock+0x50/0x68\n[   55.015961]  v3d_perfmon_stop+0x40/0xe0 [v3d]\n[   55.016627]  v3d_bin_job_run+0x10c/0x2d8 [v3d]\n[   55.017282]  drm_sched_main+0x178/0x3f8 [gpu_sched]\n[   55.017921]  kthread+0x11c/0x128\n[   55.018554]  ret_from_fork+0x10/0x20\n[   55.019168] Code: f9400260 f1001c1f 54001ea9 927df000 (b9403401)\n[   55.019776] ---[ end trace 0000000000000000 ]---\n[   55.020411] note: v3d_bin[166] exited with preempt_count 1\n\nThis issue arises because, upon closing the file descriptor (which happens\nwhen we interrupt `kmscube`), the active performance monitor is not\nstopped. Although all perfmons are destroyed in `v3d_perfmon_close_file()`,\nthe active performance monitor\u0027s pointer (`v3d-\u003eactive_perfmon`) is still\nretained.\n\nIf `kmscube` is run again, the driver will attempt to stop the active\nperformance monitor using the stale pointer in `v3d-\u003eactive_perfmon`.\nHowever, this pointer is no longer valid because the previous process has\nalready terminated, and all performance monitors associated with it have\nbeen destroyed and freed.\n\nTo fix this, when the active performance monitor belongs to a given\nprocess, explicitly stop it before destroying and freeing it."
        }
      ],
      "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 vulnerability is reached exclusively through ioctls on the local DRM render node /dev/dri/renderD128 (V3D_PERFMON_CREATE plus V3D_SUBMIT_CL/CSD), requiring a local file descriptor on the device. There is no network or remote-peer input path, and the GPU is an integrated SoC block rather than a pluggable device.\nAC:L - This is a deterministic stale-pointer bug, not a race \u2014 the attacker controls both the free (close the fd) and the use (submit the next job), with an unbounded window in between to heap-spray the reclaimed chunk. Upstream reproduces it simply by running kmscube twice, and the attacker can even select the target kmalloc cache by choosing ncounters.\nPR:L - All required ioctls are DRM_RENDER_ALLOW and DRM_AUTH is automatically satisfied for render clients (drm_ioctl.c:550), so no capability, DRM master, or authentication is needed \u2014 only an open fd on the render node, which ordinary logged-in users and GPU-enabled containers routinely have. No root or init-namespace privilege is involved.\nUI:N - The attacker performs every step itself: create perfmon, submit a job, close the fd, spray the heap, then submit another job to trigger the use-after-free. No victim action is required, though the global stale pointer will also fire on any other user\u0027s GPU submission.\nS:U - The corruption is confined to kernel heap memory within the same security authority; no VM, IOMMU, or hypervisor boundary is crossed. It does cross a process boundary (one user\u0027s stale pointer corrupts memory during another user\u0027s job), but that remains a standard kernel privilege-escalation scope.\nC:H - The use-after-free reads freed memory (ncounters, mutex state) that the attacker can populate via heap spray, and the resulting heap corruption is readily leveraged into arbitrary kernel memory disclosure by tampering with length/pointer fields of adjacent reclaimed objects such as msg_msg or pipe_buffer.\nI:H - v3d_perfmon_stop() performs a read-modify-write loop (perfmon-\u003evalues[i] += ...) into the freed/reclaimed object with the iteration count taken from that same attacker-controlled memory, writing u64s up to roughly 2 KB past the allocation into neighbouring slab objects. Combined with mutex_lock() on attacker-controlled memory, this yields a heap-corruption primitive suitable for control-flow hijacking.\nA:H - The upstream bug report is a fatal kernel oops (level-1 translation fault in __mutex_lock) in the v3d_bin scheduler kthread, which exits with preempt_count 1 leaving the mutex held and the GPU scheduler wedged. Any unprivileged user can trigger this crash repeatedly and reliably."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T11:41:07.577Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/24ab54a066d2ef671b03eb909ca2114c0c9ac1e7"
        },
        {
          "url": "https://git.kernel.org/stable/c/0c9e9a3a4873705740b19300cadc6599170646ef"
        },
        {
          "url": "https://git.kernel.org/stable/c/07c51108d9e278831c16191d1223ee49986e7890"
        },
        {
          "url": "https://git.kernel.org/stable/c/333767cbce6ac20ec794c76eec82ed0ef55022db"
        },
        {
          "url": "https://git.kernel.org/stable/c/7d1fd3638ee3a9f9bca4785fffb638ca19120718"
        }
      ],
      "title": "drm/v3d: Stop the active perfmon before being destroyed",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2024-50031",
    "datePublished": "2024-10-21T19:39:33.795Z",
    "dateReserved": "2024-10-21T12:17:06.069Z",
    "dateUpdated": "2026-08-05T11:41:07.577Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2024-50031",
      "date": "2026-08-10",
      "epss": "0.00245",
      "percentile": "0.15763"
    },
    "fkie_nvd": {
      "configurations": "[{\"nodes\": [{\"operator\": \"OR\", \"negate\": false, \"cpeMatch\": [{\"vulnerable\": true, \"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"versionStartIncluding\": \"5.15\", \"versionEndExcluding\": \"5.15.168\", \"matchCriteriaId\": \"151D0F58-4482-4AA5-87D2-803A6F5164C1\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"versionStartIncluding\": \"5.16\", \"versionEndExcluding\": \"6.1.113\", \"matchCriteriaId\": \"D01BD22E-ACD1-4618-9D01-6116570BE1EE\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"versionStartIncluding\": \"6.2\", \"versionEndExcluding\": \"6.6.57\", \"matchCriteriaId\": \"05D83DB8-7465-4F88-AFB2-980011992AC1\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"versionStartIncluding\": \"6.7\", \"versionEndExcluding\": \"6.11.4\", \"matchCriteriaId\": \"AA84D336-CE9A-4535-B901-1AD77EC17C34\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:o:linux:linux_kernel:6.12:rc1:*:*:*:*:*:*\", \"matchCriteriaId\": \"7F361E1D-580F-4A2D-A509-7615F73167A1\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:o:linux:linux_kernel:6.12:rc2:*:*:*:*:*:*\", \"matchCriteriaId\": \"925478D0-3E3D-4E6F-ACD5-09F28D5DF82C\"}]}]}]",
      "descriptions": "[{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\ndrm/v3d: Stop the active perfmon before being destroyed\\n\\nWhen running `kmscube` with one or more performance monitors enabled\\nvia `GALLIUM_HUD`, the following kernel panic can occur:\\n\\n[   55.008324] Unable to handle kernel paging request at virtual address 00000000052004a4\\n[   55.008368] Mem abort info:\\n[   55.008377]   ESR = 0x0000000096000005\\n[   55.008387]   EC = 0x25: DABT (current EL), IL = 32 bits\\n[   55.008402]   SET = 0, FnV = 0\\n[   55.008412]   EA = 0, S1PTW = 0\\n[   55.008421]   FSC = 0x05: level 1 translation fault\\n[   55.008434] Data abort info:\\n[   55.008442]   ISV = 0, ISS = 0x00000005, ISS2 = 0x00000000\\n[   55.008455]   CM = 0, WnR = 0, TnD = 0, TagAccess = 0\\n[   55.008467]   GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0\\n[   55.008481] user pgtable: 4k pages, 39-bit VAs, pgdp=00000001046c6000\\n[   55.008497] [00000000052004a4] pgd=0000000000000000, p4d=0000000000000000, pud=0000000000000000\\n[   55.008525] Internal error: Oops: 0000000096000005 [#1] PREEMPT SMP\\n[   55.008542] Modules linked in: rfcomm [...] vc4 v3d snd_soc_hdmi_codec drm_display_helper\\ngpu_sched drm_shmem_helper cec drm_dma_helper drm_kms_helper i2c_brcmstb\\ndrm drm_panel_orientation_quirks snd_soc_core snd_compress snd_pcm_dmaengine snd_pcm snd_timer snd backlight\\n[   55.008799] CPU: 2 PID: 166 Comm: v3d_bin Tainted: G         C         6.6.47+rpt-rpi-v8 #1  Debian 1:6.6.47-1+rpt1\\n[   55.008824] Hardware name: Raspberry Pi 4 Model B Rev 1.5 (DT)\\n[   55.008838] pstate: 20000005 (nzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\\n[   55.008855] pc : __mutex_lock.constprop.0+0x90/0x608\\n[   55.008879] lr : __mutex_lock.constprop.0+0x58/0x608\\n[   55.008895] sp : ffffffc080673cf0\\n[   55.008904] x29: ffffffc080673cf0 x28: 0000000000000000 x27: ffffff8106188a28\\n[   55.008926] x26: ffffff8101e78040 x25: ffffff8101baa6c0 x24: ffffffd9d989f148\\n[   55.008947] x23: ffffffda1c2a4008 x22: 0000000000000002 x21: ffffffc080673d38\\n[   55.008968] x20: ffffff8101238000 x19: ffffff8104f83188 x18: 0000000000000000\\n[   55.008988] x17: 0000000000000000 x16: ffffffda1bd04d18 x15: 00000055bb08bc90\\n[   55.009715] x14: 0000000000000000 x13: 0000000000000000 x12: ffffffda1bd4cbb0\\n[   55.010433] x11: 00000000fa83b2da x10: 0000000000001a40 x9 : ffffffda1bd04d04\\n[   55.011162] x8 : ffffff8102097b80 x7 : 0000000000000000 x6 : 00000000030a5857\\n[   55.011880] x5 : 00ffffffffffffff x4 : 0300000005200470 x3 : 0300000005200470\\n[   55.012598] x2 : ffffff8101238000 x1 : 0000000000000021 x0 : 0300000005200470\\n[   55.013292] Call trace:\\n[   55.013959]  __mutex_lock.constprop.0+0x90/0x608\\n[   55.014646]  __mutex_lock_slowpath+0x1c/0x30\\n[   55.015317]  mutex_lock+0x50/0x68\\n[   55.015961]  v3d_perfmon_stop+0x40/0xe0 [v3d]\\n[   55.016627]  v3d_bin_job_run+0x10c/0x2d8 [v3d]\\n[   55.017282]  drm_sched_main+0x178/0x3f8 [gpu_sched]\\n[   55.017921]  kthread+0x11c/0x128\\n[   55.018554]  ret_from_fork+0x10/0x20\\n[   55.019168] Code: f9400260 f1001c1f 54001ea9 927df000 (b9403401)\\n[   55.019776] ---[ end trace 0000000000000000 ]---\\n[   55.020411] note: v3d_bin[166] exited with preempt_count 1\\n\\nThis issue arises because, upon closing the file descriptor (which happens\\nwhen we interrupt `kmscube`), the active performance monitor is not\\nstopped. Although all perfmons are destroyed in `v3d_perfmon_close_file()`,\\nthe active performance monitor\u0027s pointer (`v3d-\u003eactive_perfmon`) is still\\nretained.\\n\\nIf `kmscube` is run again, the driver will attempt to stop the active\\nperformance monitor using the stale pointer in `v3d-\u003eactive_perfmon`.\\nHowever, this pointer is no longer valid because the previous process has\\nalready terminated, and all performance monitors associated with it have\\nbeen destroyed and freed.\\n\\nTo fix this, when the active performance monitor belongs to a given\\nprocess, explicitly stop it before destroying and freeing it.\"}, {\"lang\": \"es\", \"value\": \"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: drm/v3d: Detener el perfmon activo antes de ser destruido Al ejecutar `kmscube` con uno o m\\u00e1s monitores de rendimiento habilitados a trav\\u00e9s de `GALLIUM_HUD`, puede ocurrir el siguiente p\\u00e1nico del kernel: [ 55.008324] No se puede manejar la solicitud de paginaci\\u00f3n del kernel en la direcci\\u00f3n virtual 00000000052004a4 [ 55.008368] Informaci\\u00f3n de aborto de memoria: [ 55.008377] ESR = 0x0000000096000005 [ 55.008387] EC = 0x25: DABT (EL actual), IL = 32 bits [ 55.008402] SET = 0, FnV = 0 [ 55.008412] EA = 0, S1PTW = 0 [ 55.008421] FSC = 0x05: error de traducci\\u00f3n de nivel 1 [ 55.008434] Informaci\\u00f3n de interrupci\\u00f3n de datos: [ 55.008442] ISV = 0, ISS = 0x00000005, ISS2 = 0x00000000 [ 55.008455] CM = 0, WnR = 0, TnD = 0, TagAccess = 0 [ 55.008467] GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 [ 55.008481] pgtable de usuario: p\\u00e1ginas de 4k, VA de 39 bits, pgdp=00000001046c6000 [ 55.008497] [000000000052004a4] pgd=0000000000000000, p4d=00000000000000000, pud=0000000000000000 [ 55.008525] Error interno: Oops: 0000000096000005 [#1] PREEMPT SMP [ 55.008542] M\\u00f3dulos vinculados en: rfcomm [...] vc4 v3d snd_soc_hdmi_codec drm_display_helper gpu_sched drm_shmem_helper cec drm_dma_helper drm_kms_helper i2c_brcmstb drm drm_panel_orientation_quirks snd_soc_core snd_compress snd_pcm_dmaengine snd_pcm snd_timer snd backlight [ 55.008799] CPU: 2 PID: 166 Comm: v3d_bin Contaminado: GC 6.6.47+rpt-rpi-v8 #1 Debian 1:6.6.47-1+rpt1 [ 55.008824] Nombre del hardware: Raspberry Pi 4 Modelo B Rev 1.5 (DT) [ 55.008838] pstate: 20000005 (nzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 55.008855] pc : __mutex_lock.constprop.0+0x90/0x608 [ 55.008879] lr : __mutex_lock.constprop.0+0x58/0x608 [ 55.008895] sp : ffffffc080673cf0 [ 55.008904] x29: ffffffc080673cf0 x28: 0000000000000000 x27: ffffff8106188a28 [ 55.008926] x26: ffffff8101e78040 x25: ffffff8101baa6c0 x24: ffffffd9d989f148 [ 55.008947] x23: ffffffda1c2a4008 x22: 0000000000000002 x21: ffffffc080673d38 [ 55.008968] x20: ffffff8101238000 x19: ffffff8104f83188 x18: 0000000000000000 [ 55.008988] x17: 0000000000000000 x16: ffffffda1bd04d18 x15: 00000055bb08bc90 [ 55.009715] x14: 000000000000000 x13: 0000000000000000 x12: ffffffda1bd4cbb0 [ 55.010433] x11: 00000000fa83b2da x10: 0000000000001a40 x9: ffffffda1bd04d04 [55.011162] x8: ffffff8102097b80 x7: 0000000000000000 x6: 00000000030a5857 [55.011880] x5: 00ffffffffffffff x4: 0300000005200470 x3: 0300000005200470 [55.012598] x2: ffffff8101238000 x1: 0000000000000021 x0 : 0300000005200470 [ 55.013292] Rastreo de llamadas: [ 55.013959] __mutex_lock.constprop.0+0x90/0x608 [ 55.014646] __mutex_lock_slowpath+0x1c/0x30 [ 55.015317] mutex_lock+0x50/0x68 [ 55.015961] v3d_perfmon_stop+0x40/0xe0 [v3d] [ 55.016627] v3d_bin_job_run+0x10c/0x2d8 [v3d] [ 55.017282] drm_sched_main+0x178/0x3f8 [gpu_sched] [ 55.017921] kthread+0x11c/0x128 [ 55.018554] ret_from_fork+0x10/0x20 [ 55.019168] C\\u00f3digo: f9400260 f1001c1f 54001ea9 927df000 (b9403401) [ 55.019776] ---[ fin del seguimiento 000000000000000 ]--- [ 55.020411] nota: v3d_bin[166] sali\\u00f3 con preempt_count 1 Este problema surge porque, al cerrar el descriptor de archivo (lo que sucede cuando interrumpimos `kmscube`), el monitor de rendimiento activo no se detiene. Aunque todos los monitores de rendimiento se destruyen en `v3d_perfmon_close_file()`, el puntero del monitor de rendimiento activo (`v3d-\u0026gt;active_perfmon`) a\\u00fan se conserva. Si se ejecuta de nuevo `kmscube`, el controlador intentar\\u00e1 detener el monitor de rendimiento activo utilizando el puntero obsoleto en `v3d-\u0026gt;active_perfmon`. Sin embargo, este puntero ya no es v\\u00e1lido porque el proceso anterior ya ha finalizado y todos los monitores de rendimiento asociados con \\u00e9l se han destruido y liberado. Para solucionar esto, cuando el monitor de rendimiento activo pertenece a un proceso determinado, det\\u00e9ngalo expl\\u00edcitamente antes de destruirlo y liberarlo.\"}]",
      "id": "CVE-2024-50031",
      "lastModified": "2024-10-25T15:30:15.727",
      "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": "2024-10-21T20:15:16.350",
      "references": "[{\"url\": \"https://git.kernel.org/stable/c/07c51108d9e278831c16191d1223ee49986e7890\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"tags\": [\"Patch\"]}, {\"url\": \"https://git.kernel.org/stable/c/0c9e9a3a4873705740b19300cadc6599170646ef\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"tags\": [\"Patch\"]}, {\"url\": \"https://git.kernel.org/stable/c/24ab54a066d2ef671b03eb909ca2114c0c9ac1e7\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"tags\": [\"Patch\"]}, {\"url\": \"https://git.kernel.org/stable/c/333767cbce6ac20ec794c76eec82ed0ef55022db\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"tags\": [\"Patch\"]}, {\"url\": \"https://git.kernel.org/stable/c/7d1fd3638ee3a9f9bca4785fffb638ca19120718\", \"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\": \"NVD-CWE-noinfo\"}]}]"
    },
    "microsoft_vex": {
      "current_release_date": "2026-02-18T01:52:03.000Z",
      "cve": "CVE-2024-50031",
      "id": "msrc_CVE-2024-50031",
      "initial_release_date": "2024-10-01T07:00:00.000Z",
      "product_status:fixed": "5",
      "product_status:known_affected": "5",
      "source": "Microsoft CSAF VEX",
      "status": "final",
      "title": "drm/v3d: Stop the active perfmon before being destroyed",
      "url": "https://msrc.microsoft.com/csaf/vex/2024/msrc_cve-2024-50031.json",
      "version": "3"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2024-50031\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2024-10-21T20:15:16.350\",\"lastModified\":\"2026-08-04T11:21:09.797\",\"vulnStatus\":\"Modified\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\ndrm/v3d: Stop the active perfmon before being destroyed\\n\\nWhen running `kmscube` with one or more performance monitors enabled\\nvia `GALLIUM_HUD`, the following kernel panic can occur:\\n\\n[   55.008324] Unable to handle kernel paging request at virtual address 00000000052004a4\\n[   55.008368] Mem abort info:\\n[   55.008377]   ESR = 0x0000000096000005\\n[   55.008387]   EC = 0x25: DABT (current EL), IL = 32 bits\\n[   55.008402]   SET = 0, FnV = 0\\n[   55.008412]   EA = 0, S1PTW = 0\\n[   55.008421]   FSC = 0x05: level 1 translation fault\\n[   55.008434] Data abort info:\\n[   55.008442]   ISV = 0, ISS = 0x00000005, ISS2 = 0x00000000\\n[   55.008455]   CM = 0, WnR = 0, TnD = 0, TagAccess = 0\\n[   55.008467]   GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0\\n[   55.008481] user pgtable: 4k pages, 39-bit VAs, pgdp=00000001046c6000\\n[   55.008497] [00000000052004a4] pgd=0000000000000000, p4d=0000000000000000, pud=0000000000000000\\n[   55.008525] Internal error: Oops: 0000000096000005 [#1] PREEMPT SMP\\n[   55.008542] Modules linked in: rfcomm [...] vc4 v3d snd_soc_hdmi_codec drm_display_helper\\ngpu_sched drm_shmem_helper cec drm_dma_helper drm_kms_helper i2c_brcmstb\\ndrm drm_panel_orientation_quirks snd_soc_core snd_compress snd_pcm_dmaengine snd_pcm snd_timer snd backlight\\n[   55.008799] CPU: 2 PID: 166 Comm: v3d_bin Tainted: G         C         6.6.47+rpt-rpi-v8 #1  Debian 1:6.6.47-1+rpt1\\n[   55.008824] Hardware name: Raspberry Pi 4 Model B Rev 1.5 (DT)\\n[   55.008838] pstate: 20000005 (nzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\\n[   55.008855] pc : __mutex_lock.constprop.0+0x90/0x608\\n[   55.008879] lr : __mutex_lock.constprop.0+0x58/0x608\\n[   55.008895] sp : ffffffc080673cf0\\n[   55.008904] x29: ffffffc080673cf0 x28: 0000000000000000 x27: ffffff8106188a28\\n[   55.008926] x26: ffffff8101e78040 x25: ffffff8101baa6c0 x24: ffffffd9d989f148\\n[   55.008947] x23: ffffffda1c2a4008 x22: 0000000000000002 x21: ffffffc080673d38\\n[   55.008968] x20: ffffff8101238000 x19: ffffff8104f83188 x18: 0000000000000000\\n[   55.008988] x17: 0000000000000000 x16: ffffffda1bd04d18 x15: 00000055bb08bc90\\n[   55.009715] x14: 0000000000000000 x13: 0000000000000000 x12: ffffffda1bd4cbb0\\n[   55.010433] x11: 00000000fa83b2da x10: 0000000000001a40 x9 : ffffffda1bd04d04\\n[   55.011162] x8 : ffffff8102097b80 x7 : 0000000000000000 x6 : 00000000030a5857\\n[   55.011880] x5 : 00ffffffffffffff x4 : 0300000005200470 x3 : 0300000005200470\\n[   55.012598] x2 : ffffff8101238000 x1 : 0000000000000021 x0 : 0300000005200470\\n[   55.013292] Call trace:\\n[   55.013959]  __mutex_lock.constprop.0+0x90/0x608\\n[   55.014646]  __mutex_lock_slowpath+0x1c/0x30\\n[   55.015317]  mutex_lock+0x50/0x68\\n[   55.015961]  v3d_perfmon_stop+0x40/0xe0 [v3d]\\n[   55.016627]  v3d_bin_job_run+0x10c/0x2d8 [v3d]\\n[   55.017282]  drm_sched_main+0x178/0x3f8 [gpu_sched]\\n[   55.017921]  kthread+0x11c/0x128\\n[   55.018554]  ret_from_fork+0x10/0x20\\n[   55.019168] Code: f9400260 f1001c1f 54001ea9 927df000 (b9403401)\\n[   55.019776] ---[ end trace 0000000000000000 ]---\\n[   55.020411] note: v3d_bin[166] exited with preempt_count 1\\n\\nThis issue arises because, upon closing the file descriptor (which happens\\nwhen we interrupt `kmscube`), the active performance monitor is not\\nstopped. Although all perfmons are destroyed in `v3d_perfmon_close_file()`,\\nthe active performance monitor\u0027s pointer (`v3d-\u003eactive_perfmon`) is still\\nretained.\\n\\nIf `kmscube` is run again, the driver will attempt to stop the active\\nperformance monitor using the stale pointer in `v3d-\u003eactive_perfmon`.\\nHowever, this pointer is no longer valid because the previous process has\\nalready terminated, and all performance monitors associated with it have\\nbeen destroyed and freed.\\n\\nTo fix this, when the active performance monitor belongs to a given\\nprocess, explicitly stop it before destroying and freeing it.\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: drm/v3d: Detener el perfmon activo antes de ser destruido Al ejecutar `kmscube` con uno o m\u00e1s monitores de rendimiento habilitados a trav\u00e9s de `GALLIUM_HUD`, puede ocurrir el siguiente p\u00e1nico del kernel: [ 55.008324] No se puede manejar la solicitud de paginaci\u00f3n del kernel en la direcci\u00f3n virtual 00000000052004a4 [ 55.008368] Informaci\u00f3n de aborto de memoria: [ 55.008377] ESR = 0x0000000096000005 [ 55.008387] EC = 0x25: DABT (EL actual), IL = 32 bits [ 55.008402] SET = 0, FnV = 0 [ 55.008412] EA = 0, S1PTW = 0 [ 55.008421] FSC = 0x05: error de traducci\u00f3n de nivel 1 [ 55.008434] Informaci\u00f3n de interrupci\u00f3n de datos: [ 55.008442] ISV = 0, ISS = 0x00000005, ISS2 = 0x00000000 [ 55.008455] CM = 0, WnR = 0, TnD = 0, TagAccess = 0 [ 55.008467] GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 [ 55.008481] pgtable de usuario: p\u00e1ginas de 4k, VA de 39 bits, pgdp=00000001046c6000 [ 55.008497] [000000000052004a4] pgd=0000000000000000, p4d=00000000000000000, pud=0000000000000000 [ 55.008525] Error interno: Oops: 0000000096000005 [#1] PREEMPT SMP [ 55.008542] M\u00f3dulos vinculados en: rfcomm [...] vc4 v3d snd_soc_hdmi_codec drm_display_helper gpu_sched drm_shmem_helper cec drm_dma_helper drm_kms_helper i2c_brcmstb drm drm_panel_orientation_quirks snd_soc_core snd_compress snd_pcm_dmaengine snd_pcm snd_timer snd backlight [ 55.008799] CPU: 2 PID: 166 Comm: v3d_bin Contaminado: GC 6.6.47+rpt-rpi-v8 #1 Debian 1:6.6.47-1+rpt1 [ 55.008824] Nombre del hardware: Raspberry Pi 4 Modelo B Rev 1.5 (DT) [ 55.008838] pstate: 20000005 (nzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 55.008855] pc : __mutex_lock.constprop.0+0x90/0x608 [ 55.008879] lr : __mutex_lock.constprop.0+0x58/0x608 [ 55.008895] sp : ffffffc080673cf0 [ 55.008904] x29: ffffffc080673cf0 x28: 0000000000000000 x27: ffffff8106188a28 [ 55.008926] x26: ffffff8101e78040 x25: ffffff8101baa6c0 x24: ffffffd9d989f148 [ 55.008947] x23: ffffffda1c2a4008 x22: 0000000000000002 x21: ffffffc080673d38 [ 55.008968] x20: ffffff8101238000 x19: ffffff8104f83188 x18: 0000000000000000 [ 55.008988] x17: 0000000000000000 x16: ffffffda1bd04d18 x15: 00000055bb08bc90 [ 55.009715] x14: 000000000000000 x13: 0000000000000000 x12: ffffffda1bd4cbb0 [ 55.010433] x11: 00000000fa83b2da x10: 0000000000001a40 x9: ffffffda1bd04d04 [55.011162] x8: ffffff8102097b80 x7: 0000000000000000 x6: 00000000030a5857 [55.011880] x5: 00ffffffffffffff x4: 0300000005200470 x3: 0300000005200470 [55.012598] x2: ffffff8101238000 x1: 0000000000000021 x0 : 0300000005200470 [ 55.013292] Rastreo de llamadas: [ 55.013959] __mutex_lock.constprop.0+0x90/0x608 [ 55.014646] __mutex_lock_slowpath+0x1c/0x30 [ 55.015317] mutex_lock+0x50/0x68 [ 55.015961] v3d_perfmon_stop+0x40/0xe0 [v3d] [ 55.016627] v3d_bin_job_run+0x10c/0x2d8 [v3d] [ 55.017282] drm_sched_main+0x178/0x3f8 [gpu_sched] [ 55.017921] kthread+0x11c/0x128 [ 55.018554] ret_from_fork+0x10/0x20 [ 55.019168] C\u00f3digo: f9400260 f1001c1f 54001ea9 927df000 (b9403401) [ 55.019776] ---[ fin del seguimiento 000000000000000 ]--- [ 55.020411] nota: v3d_bin[166] sali\u00f3 con preempt_count 1 Este problema surge porque, al cerrar el descriptor de archivo (lo que sucede cuando interrumpimos `kmscube`), el monitor de rendimiento activo no se detiene. Aunque todos los monitores de rendimiento se destruyen en `v3d_perfmon_close_file()`, el puntero del monitor de rendimiento activo (`v3d-\u0026gt;active_perfmon`) a\u00fan se conserva. Si se ejecuta de nuevo `kmscube`, el controlador intentar\u00e1 detener el monitor de rendimiento activo utilizando el puntero obsoleto en `v3d-\u0026gt;active_perfmon`. Sin embargo, este puntero ya no es v\u00e1lido porque el proceso anterior ya ha finalizado y todos los monitores de rendimiento asociados con \u00e9l se han destruido y liberado. Para solucionar esto, cuando el monitor de rendimiento activo pertenece a un proceso determinado, det\u00e9ngalo expl\u00edcitamente antes de destruirlo y liberarlo.\"}],\"affected\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"affectedData\":[{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"unaffected\",\"programFiles\":[\"drivers/gpu/drm/v3d/v3d_perfmon.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"26a4dc29b74a137f45665089f6d3d633fcc9b662\",\"lessThan\":\"24ab54a066d2ef671b03eb909ca2114c0c9ac1e7\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"26a4dc29b74a137f45665089f6d3d633fcc9b662\",\"lessThan\":\"0c9e9a3a4873705740b19300cadc6599170646ef\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"26a4dc29b74a137f45665089f6d3d633fcc9b662\",\"lessThan\":\"07c51108d9e278831c16191d1223ee49986e7890\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"26a4dc29b74a137f45665089f6d3d633fcc9b662\",\"lessThan\":\"333767cbce6ac20ec794c76eec82ed0ef55022db\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"26a4dc29b74a137f45665089f6d3d633fcc9b662\",\"lessThan\":\"7d1fd3638ee3a9f9bca4785fffb638ca19120718\",\"versionType\":\"git\",\"status\":\"affected\"}]},{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"affected\",\"programFiles\":[\"drivers/gpu/drm/v3d/v3d_perfmon.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"5.15\",\"status\":\"affected\"},{\"version\":\"0\",\"lessThan\":\"5.15\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"5.15.168\",\"lessThanOrEqual\":\"5.15.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.1.113\",\"lessThanOrEqual\":\"6.1.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.6.57\",\"lessThanOrEqual\":\"6.6.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.11.4\",\"lessThanOrEqual\":\"6.11.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.12\",\"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:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\",\"baseScore\":7.8,\"baseSeverity\":\"HIGH\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"HIGH\",\"integrityImpact\":\"HIGH\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":1.8,\"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}],\"ssvcV203\":[{\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\",\"ssvcData\":{\"timestamp\":\"2024-10-22T13:26:04.844363Z\",\"id\":\"CVE-2024-50031\",\"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\":\"NVD-CWE-noinfo\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"5.15\",\"versionEndExcluding\":\"5.15.168\",\"matchCriteriaId\":\"151D0F58-4482-4AA5-87D2-803A6F5164C1\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"5.16\",\"versionEndExcluding\":\"6.1.113\",\"matchCriteriaId\":\"D01BD22E-ACD1-4618-9D01-6116570BE1EE\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.2\",\"versionEndExcluding\":\"6.6.57\",\"matchCriteriaId\":\"05D83DB8-7465-4F88-AFB2-980011992AC1\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.7\",\"versionEndExcluding\":\"6.11.4\",\"matchCriteriaId\":\"AA84D336-CE9A-4535-B901-1AD77EC17C34\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.12:rc1:*:*:*:*:*:*\",\"matchCriteriaId\":\"7F361E1D-580F-4A2D-A509-7615F73167A1\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.12:rc2:*:*:*:*:*:*\",\"matchCriteriaId\":\"925478D0-3E3D-4E6F-ACD5-09F28D5DF82C\"}]}]}],\"references\":[{\"url\":\"https://git.kernel.org/stable/c/07c51108d9e278831c16191d1223ee49986e7890\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/0c9e9a3a4873705740b19300cadc6599170646ef\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/24ab54a066d2ef671b03eb909ca2114c0c9ac1e7\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/333767cbce6ac20ec794c76eec82ed0ef55022db\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/7d1fd3638ee3a9f9bca4785fffb638ca19120718\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\"}]}}",
    "redhat_vex": {
      "aggregate_severity": "Moderate",
      "current_release_date": "2026-08-04T14:18:14+00:00",
      "cve": "CVE-2024-50031",
      "id": "CVE-2024-50031",
      "initial_release_date": "2024-10-21T00:00:00+00:00",
      "product_status:known_not_affected": "198",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: drm/v3d: Stop the active perfmon before being destroyed",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2024/cve-2024-50031.json",
      "version": "3"
    },
    "suse_vex": {
      "aggregate_severity": "moderate",
      "current_release_date": "2026-07-25T01:29:30Z",
      "cve": "CVE-2024-50031",
      "id": "CVE-2024-50031",
      "initial_release_date": "2024-10-22T02:50:11Z",
      "product_status:known_affected": "354",
      "product_status:known_not_affected": "263",
      "product_status:recommended": "641",
      "source": "SUSE CSAF VEX",
      "status": "interim",
      "title": "SUSE CVE CVE-2024-50031",
      "url": "https://ftp.suse.com/pub/projects/security/csaf-vex/cve-2024-50031.json",
      "version": "63"
    },
    "vulnrichment": {
      "containers": "{\"adp\": [{\"title\": \"CVE Program Container\", \"references\": [{\"url\": \"https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html\"}], \"providerMetadata\": {\"orgId\": \"af854a3a-2127-422b-91ae-364da2661108\", \"shortName\": \"CVE\", \"dateUpdated\": \"2025-11-03T22:24:37.994Z\"}}, {\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2024-50031\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2024-10-22T13:26:04.844363Z\"}}}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2024-10-22T13:26:07.912Z\"}}], \"cna\": {\"title\": \"drm/v3d: Stop the active perfmon before being destroyed\", \"metrics\": [{\"cvssV3_1\": {\"version\": \"3.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\"}, \"scenarios\": [{\"lang\": \"en\", \"value\": \"AV:L - The vulnerability is reached exclusively through ioctls on the local DRM render node /dev/dri/renderD128 (V3D_PERFMON_CREATE plus V3D_SUBMIT_CL/CSD), requiring a local file descriptor on the device. There is no network or remote-peer input path, and the GPU is an integrated SoC block rather than a pluggable device.\\nAC:L - This is a deterministic stale-pointer bug, not a race \\u2014 the attacker controls both the free (close the fd) and the use (submit the next job), with an unbounded window in between to heap-spray the reclaimed chunk. Upstream reproduces it simply by running kmscube twice, and the attacker can even select the target kmalloc cache by choosing ncounters.\\nPR:L - All required ioctls are DRM_RENDER_ALLOW and DRM_AUTH is automatically satisfied for render clients (drm_ioctl.c:550), so no capability, DRM master, or authentication is needed \\u2014 only an open fd on the render node, which ordinary logged-in users and GPU-enabled containers routinely have. No root or init-namespace privilege is involved.\\nUI:N - The attacker performs every step itself: create perfmon, submit a job, close the fd, spray the heap, then submit another job to trigger the use-after-free. No victim action is required, though the global stale pointer will also fire on any other user\u0027s GPU submission.\\nS:U - The corruption is confined to kernel heap memory within the same security authority; no VM, IOMMU, or hypervisor boundary is crossed. It does cross a process boundary (one user\u0027s stale pointer corrupts memory during another user\u0027s job), but that remains a standard kernel privilege-escalation scope.\\nC:H - The use-after-free reads freed memory (ncounters, mutex state) that the attacker can populate via heap spray, and the resulting heap corruption is readily leveraged into arbitrary kernel memory disclosure by tampering with length/pointer fields of adjacent reclaimed objects such as msg_msg or pipe_buffer.\\nI:H - v3d_perfmon_stop() performs a read-modify-write loop (perfmon-\u003evalues[i] += ...) into the freed/reclaimed object with the iteration count taken from that same attacker-controlled memory, writing u64s up to roughly 2 KB past the allocation into neighbouring slab objects. Combined with mutex_lock() on attacker-controlled memory, this yields a heap-corruption primitive suitable for control-flow hijacking.\\nA:H - The upstream bug report is a fatal kernel oops (level-1 translation fault in __mutex_lock) in the v3d_bin scheduler kthread, which exits with preempt_count 1 leaving the mutex held and the GPU scheduler wedged. Any unprivileged user can trigger this crash repeatedly and reliably.\"}]}], \"affected\": [{\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"26a4dc29b74a137f45665089f6d3d633fcc9b662\", \"lessThan\": \"24ab54a066d2ef671b03eb909ca2114c0c9ac1e7\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"26a4dc29b74a137f45665089f6d3d633fcc9b662\", \"lessThan\": \"0c9e9a3a4873705740b19300cadc6599170646ef\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"26a4dc29b74a137f45665089f6d3d633fcc9b662\", \"lessThan\": \"07c51108d9e278831c16191d1223ee49986e7890\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"26a4dc29b74a137f45665089f6d3d633fcc9b662\", \"lessThan\": \"333767cbce6ac20ec794c76eec82ed0ef55022db\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"26a4dc29b74a137f45665089f6d3d633fcc9b662\", \"lessThan\": \"7d1fd3638ee3a9f9bca4785fffb638ca19120718\", \"versionType\": \"git\"}], \"programFiles\": [\"drivers/gpu/drm/v3d/v3d_perfmon.c\"], \"defaultStatus\": \"unaffected\"}, {\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"5.15\"}, {\"status\": \"unaffected\", \"version\": \"0\", \"lessThan\": \"5.15\", \"versionType\": \"semver\"}, {\"status\": \"unaffected\", \"version\": \"5.15.168\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"5.15.*\"}, {\"status\": \"unaffected\", \"version\": \"6.1.113\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.1.*\"}, {\"status\": \"unaffected\", \"version\": \"6.6.57\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.6.*\"}, {\"status\": \"unaffected\", \"version\": \"6.11.4\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.11.*\"}, {\"status\": \"unaffected\", \"version\": \"6.12\", \"versionType\": \"original_commit_for_fix\", \"lessThanOrEqual\": \"*\"}], \"programFiles\": [\"drivers/gpu/drm/v3d/v3d_perfmon.c\"], \"defaultStatus\": \"affected\"}], \"references\": [{\"url\": \"https://git.kernel.org/stable/c/24ab54a066d2ef671b03eb909ca2114c0c9ac1e7\"}, {\"url\": \"https://git.kernel.org/stable/c/0c9e9a3a4873705740b19300cadc6599170646ef\"}, {\"url\": \"https://git.kernel.org/stable/c/07c51108d9e278831c16191d1223ee49986e7890\"}, {\"url\": \"https://git.kernel.org/stable/c/333767cbce6ac20ec794c76eec82ed0ef55022db\"}, {\"url\": \"https://git.kernel.org/stable/c/7d1fd3638ee3a9f9bca4785fffb638ca19120718\"}], \"x_generator\": {\"engine\": \"bippy-1.2.0\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\ndrm/v3d: Stop the active perfmon before being destroyed\\n\\nWhen running `kmscube` with one or more performance monitors enabled\\nvia `GALLIUM_HUD`, the following kernel panic can occur:\\n\\n[   55.008324] Unable to handle kernel paging request at virtual address 00000000052004a4\\n[   55.008368] Mem abort info:\\n[   55.008377]   ESR = 0x0000000096000005\\n[   55.008387]   EC = 0x25: DABT (current EL), IL = 32 bits\\n[   55.008402]   SET = 0, FnV = 0\\n[   55.008412]   EA = 0, S1PTW = 0\\n[   55.008421]   FSC = 0x05: level 1 translation fault\\n[   55.008434] Data abort info:\\n[   55.008442]   ISV = 0, ISS = 0x00000005, ISS2 = 0x00000000\\n[   55.008455]   CM = 0, WnR = 0, TnD = 0, TagAccess = 0\\n[   55.008467]   GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0\\n[   55.008481] user pgtable: 4k pages, 39-bit VAs, pgdp=00000001046c6000\\n[   55.008497] [00000000052004a4] pgd=0000000000000000, p4d=0000000000000000, pud=0000000000000000\\n[   55.008525] Internal error: Oops: 0000000096000005 [#1] PREEMPT SMP\\n[   55.008542] Modules linked in: rfcomm [...] vc4 v3d snd_soc_hdmi_codec drm_display_helper\\ngpu_sched drm_shmem_helper cec drm_dma_helper drm_kms_helper i2c_brcmstb\\ndrm drm_panel_orientation_quirks snd_soc_core snd_compress snd_pcm_dmaengine snd_pcm snd_timer snd backlight\\n[   55.008799] CPU: 2 PID: 166 Comm: v3d_bin Tainted: G         C         6.6.47+rpt-rpi-v8 #1  Debian 1:6.6.47-1+rpt1\\n[   55.008824] Hardware name: Raspberry Pi 4 Model B Rev 1.5 (DT)\\n[   55.008838] pstate: 20000005 (nzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\\n[   55.008855] pc : __mutex_lock.constprop.0+0x90/0x608\\n[   55.008879] lr : __mutex_lock.constprop.0+0x58/0x608\\n[   55.008895] sp : ffffffc080673cf0\\n[   55.008904] x29: ffffffc080673cf0 x28: 0000000000000000 x27: ffffff8106188a28\\n[   55.008926] x26: ffffff8101e78040 x25: ffffff8101baa6c0 x24: ffffffd9d989f148\\n[   55.008947] x23: ffffffda1c2a4008 x22: 0000000000000002 x21: ffffffc080673d38\\n[   55.008968] x20: ffffff8101238000 x19: ffffff8104f83188 x18: 0000000000000000\\n[   55.008988] x17: 0000000000000000 x16: ffffffda1bd04d18 x15: 00000055bb08bc90\\n[   55.009715] x14: 0000000000000000 x13: 0000000000000000 x12: ffffffda1bd4cbb0\\n[   55.010433] x11: 00000000fa83b2da x10: 0000000000001a40 x9 : ffffffda1bd04d04\\n[   55.011162] x8 : ffffff8102097b80 x7 : 0000000000000000 x6 : 00000000030a5857\\n[   55.011880] x5 : 00ffffffffffffff x4 : 0300000005200470 x3 : 0300000005200470\\n[   55.012598] x2 : ffffff8101238000 x1 : 0000000000000021 x0 : 0300000005200470\\n[   55.013292] Call trace:\\n[   55.013959]  __mutex_lock.constprop.0+0x90/0x608\\n[   55.014646]  __mutex_lock_slowpath+0x1c/0x30\\n[   55.015317]  mutex_lock+0x50/0x68\\n[   55.015961]  v3d_perfmon_stop+0x40/0xe0 [v3d]\\n[   55.016627]  v3d_bin_job_run+0x10c/0x2d8 [v3d]\\n[   55.017282]  drm_sched_main+0x178/0x3f8 [gpu_sched]\\n[   55.017921]  kthread+0x11c/0x128\\n[   55.018554]  ret_from_fork+0x10/0x20\\n[   55.019168] Code: f9400260 f1001c1f 54001ea9 927df000 (b9403401)\\n[   55.019776] ---[ end trace 0000000000000000 ]---\\n[   55.020411] note: v3d_bin[166] exited with preempt_count 1\\n\\nThis issue arises because, upon closing the file descriptor (which happens\\nwhen we interrupt `kmscube`), the active performance monitor is not\\nstopped. Although all perfmons are destroyed in `v3d_perfmon_close_file()`,\\nthe active performance monitor\u0027s pointer (`v3d-\u003eactive_perfmon`) is still\\nretained.\\n\\nIf `kmscube` is run again, the driver will attempt to stop the active\\nperformance monitor using the stale pointer in `v3d-\u003eactive_perfmon`.\\nHowever, this pointer is no longer valid because the previous process has\\nalready terminated, and all performance monitors associated with it have\\nbeen destroyed and freed.\\n\\nTo fix this, when the active performance monitor belongs to a given\\nprocess, explicitly stop it before destroying and freeing it.\"}], \"cpeApplicability\": [{\"nodes\": [{\"negate\": false, \"cpeMatch\": [{\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"5.15.168\", \"versionStartIncluding\": \"5.15\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.1.113\", \"versionStartIncluding\": \"5.15\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.6.57\", \"versionStartIncluding\": \"5.15\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.11.4\", \"versionStartIncluding\": \"5.15\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.12\", \"versionStartIncluding\": \"5.15\"}], \"operator\": \"OR\"}]}], \"providerMetadata\": {\"orgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"shortName\": \"Linux\", \"dateUpdated\": \"2026-08-05T11:41:07.577Z\"}}}",
      "cveMetadata": "{\"cveId\": \"CVE-2024-50031\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2026-08-05T11:41:07.577Z\", \"dateReserved\": \"2024-10-21T12:17:06.069Z\", \"assignerOrgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"datePublished\": \"2024-10-21T19:39:33.795Z\", \"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.