{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-50031 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2024-50031 is a high-severity vulnerability in Linux kernel, published on 21 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-50031 and fix it if it is affected.\n\nWhat it is: CVE-2024-50031 is a high-severity vulnerability in Linux kernel, published on 21 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-50031 in the wild and no public exploit code.\n\nAffected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-50031/ (Markdown: https://insights.sbomify.com/CVE-2024-50031/index.md)","id":"CVE-2024-50031","markdown":"https://insights.sbomify.com/CVE-2024-50031/index.md","name":"CVE-2024-50031","record":{"aliases":["AZL-51351","AZL-51551","BELL-CVE-2024-50031","DEBIAN-CVE-2024-50031","GHSA-3fxp-j2vr-qqgv","UBUNTU-CVE-2024-50031"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel DRM driver","requires_auth":"low_privilege","summary":"A null pointer dereference in the Linux kernel's v3d DRM driver causes a kernel panic when performance monitors are active.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"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's 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"drm/v3d: Stop the active perfmon before being destroyed","id":"CVE-2024-50031","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"null_dereference","year":"2024"},"n_packages":0,"n_references":5,"next":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","id":"CVE-2024-50032"},"packages":[],"prev":{"headline":"drm/xe/ct: prevent UAF in send_recv()","id":"CVE-2024-50030"},"products":["Linux"],"published":"2024-10-21","related":[{"cvss_score":8.8,"headline":"Linux Kernel Out-of-Bounds Write","id":"CVE-2026-53266","kev_date_added":"2026-09-18","published":"2026-06-25"},{"cvss_score":8.8,"headline":"Linux Kernel Improper Input Validation","id":"CVE-2013-6282","kev_date_added":"2022-09-15","published":"2013-11-19"},{"cvss_score":8.4,"headline":"Linux Kernel Heap-Based Buffer Overflow","id":"CVE-2022-0185","kev_date_added":"2024-08-21","published":"2022-02-11"},{"cvss_score":8.4,"headline":"Linux Kernel Privilege Escalation","id":"CVE-2013-2094","kev_date_added":"2022-09-15","published":"2013-05-14"},{"cvss_score":7.8,"headline":"Linux Kernel Unspecified","id":"CVE-2026-53362","kev_date_added":"2026-08-27","published":"2026-07-04"},{"cvss_score":7.8,"headline":"Linux Kernel Missing Initialization of a Variable","id":"CVE-2026-46300","kev_date_added":"2026-10-28","published":"2026-05-23"},{"cvss_score":7.8,"headline":"Linux Kernel Race Condition","id":"CVE-2025-39964","kev_date_added":"2026-09-18","published":"2025-10-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-05","vendors":["Linux"]},"summary":"A null pointer dereference in the Linux kernel's v3d DRM driver causes a kernel panic when performance monitors are active.","url":"https://insights.sbomify.com/CVE-2024-50031/"}