{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-64100 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-64100 is a medium-severity vulnerability in Linux kernel, published on 19 Jul 2026. 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-2026-64100 and fix it if it is affected.\n\nWhat it is: CVE-2026-64100 is a medium-severity vulnerability in Linux kernel, published on 19 Jul 2026. 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-2026-64100 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-2026-64100/ (Markdown: https://insights.sbomify.com/CVE-2026-64100/index.md)","id":"CVE-2026-64100","markdown":"https://insights.sbomify.com/CVE-2026-64100/index.md","name":"CVE-2026-64100","record":{"aliases":["BELL-CVE-2026-64100","DEBIAN-CVE-2026-64100","GHSA-3q3c-q46p-rwcg","UBUNTU-CVE-2026-64100"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel driver","requires_auth":"low_privilege","summary":"A deadlock in the Linux kernel MSM DRM driver can cause a system hang under memory pressure, requiring a kernel patch to resolve.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-667","name":"Improper Locking"}],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/msm: Fix shrinker deadlock\n\nWith PROVE_LOCKING on an Snapdragon X1 and VM reclaim pressure, we see:\n\n   ======================================================\n   WARNING: possible circular locking dependency detected\n   7.0.0-debug+ #43 Tainted: G        W\n   ------------------------------------------------------\n   kswapd0/82 is trying to acquire lock:\n   ffff800080ec3870 (reservation_ww_class_acquire){+.+.}-{0:0}, at: msm_gem_shrinker_scan+0x17c/0x400 [msm]\n\n   but task is already holding lock:\n   ffffc31709b263b8 (fs_reclaim){+.+.}-{0:0}, at: balance_pgdat+0x88/0x988\n\n   which lock already depends on the new lock.\n\n   the existing dependency chain (in reverse order) is:\n\n   -\u003e #2 (fs_reclaim){+.+.}-{0:0}:\n          __lock_acquire+0x4d0/0xad0\n          lock_acquire.part.0+0xc4/0x248\n          lock_acquire+0x8c/0x248\n          fs_reclaim_acquire+0xd0/0xf0\n          dma_resv_lockdep+0x224/0x348\n          do_one_initcall+0x84/0x5d0\n          do_initcalls+0x194/0x1d8\n          kernel_init_freeable+0x128/0x180\n          kernel_init+0x2c/0x160\n          ret_from_fork+0x10/0x20\n\n   -\u003e #1 (reservation_ww_class_mutex){+.+.}-{4:4}:\n          __lock_acquire+0x4d0/0xad0\n          lock_acquire.part.0+0xc4/0x248\n          lock_acquire+0x8c/0x248\n          dma_resv_lockdep+0x1a8/0x348\n          do_one_initcall+0x84/0x5d0\n          do_initcalls+0x194/0x1d8\n          kernel_init_freeable+0x128/0x180\n          kernel_init+0x2c/0x160\n          ret_from_fork+0x10/0x20\n\n   -\u003e #0 (reservation_ww_class_acquire){+.+.}-{0:0}:\n          check_prev_add+0x114/0x790\n          validate_chain+0x594/0x6f0\n          __lock_acquire+0x4d0/0xad0\n          lock_acquire.part.0+0xc4/0x248\n          lock_acquire+0x8c/0x248\n          drm_gem_lru_scan+0x1ac/0x440\n          msm_gem_shrinker_scan+0x17c/0x400 [msm]\n          do_shrink_slab+0x150/0x4a0\n          shrink_slab+0x144/0x460\n          shrink_one+0x9c/0x1b0\n          shrink_many+0x27c/0x5c0\n          shrink_node+0x344/0x550\n          balance_pgdat+0x2c0/0x988\n          kswapd+0x11c/0x318\n          kthread+0x10c/0x128\n          ret_from_fork+0x10/0x20\n\n   other info that might help us debug this:\n   Chain exists of:\n     reservation_ww_class_acquire --\u003e reservation_ww_class_mutex --\u003e fs_reclaim\n    Possible unsafe locking scenario:\n          CPU0                    CPU1\n          ----                    ----\n     lock(fs_reclaim);\n                                  lock(reservation_ww_class_mutex);\n                                  lock(fs_reclaim);\n     lock(reservation_ww_class_acquire);\n\n    *** DEADLOCK ***\n   1 lock held by kswapd0/82:\n    #0: ffffc31709b263b8 (fs_reclaim){+.+.}-{0:0}, at: balance_pgdat+0x88/0x988\n\n   stack backtrace:\n   CPU: 4 UID: 0 PID: 82 Comm: kswapd0 Tainted: G        W           7.0.0-debug+ #43 PREEMPT(full)\n   Tainted: [W]=WARN\n   Hardware name: LENOVO 21BX0016US/21BX0016US, BIOS N3HET94W (1.66 ) 09/15/2025\n   Call trace:\n    show_stack+0x20/0x40 (C)\n    dump_stack_lvl+0x9c/0xd0\n    dump_stack+0x18/0x30\n    print_circular_bug+0x114/0x120\n    check_noncircular+0x178/0x198\n    check_prev_add+0x114/0x790\n    validate_chain+0x594/0x6f0\n    __lock_acquire+0x4d0/0xad0\n    lock_acquire.part.0+0xc4/0x248\n    lock_acquire+0x8c/0x248\n    drm_gem_lru_scan+0x1ac/0x440\n    msm_gem_shrinker_scan+0x17c/0x400 [msm]\n    do_shrink_slab+0x150/0x4a0\n    shrink_slab+0x144/0x460\n    shrink_one+0x9c/0x1b0\n    shrink_many+0x27c/0x5c0\n    shrink_node+0x344/0x550\n    balance_pgdat+0x2c0/0x988\n    kswapd+0x11c/0x318\n    kthread+0x10c/0x128\n    ret_from_fork+0x10/0x20\n\nkswapd0 holding fs_reclaim calls the MSM shrinker, which calls\ndma_resv_lock. This in turn acquires fs_reclaim.\n\nFix this deadlock by using dma_resv_trylock() instead, dropping the\nsubsequently unused passed wait-wound lock 'ticket'.\n\nPatchwork: https://patchwork.freedesktop.org/patch/723564/\n[rob: fixup compile errors, replace lockdep splat with somethin\n---truncated---","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/msm: Fix shrinker deadlock","id":"CVE-2026-64100","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"fwctl: pds: Validate RPC input size before parsing","id":"CVE-2026-64101"},"packages":[],"prev":{"headline":"drm/v3d: Fix use-after-free of CPU job query arrays on error path","id":"CVE-2026-64099"},"products":["Linux"],"published":"2026-07-19","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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-07-19","vendors":["Linux"]},"summary":"A deadlock in the Linux kernel MSM DRM driver can cause a system hang under memory pressure, requiring a kernel patch to resolve.","url":"https://insights.sbomify.com/CVE-2026-64100/"}