{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-38091 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-38091 is a high-severity vulnerability in Linux kernel, published on 2 Jul 2025. 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-2025-38091 and fix it if it is affected.\n\nWhat it is: CVE-2025-38091 is a high-severity vulnerability in Linux kernel, published on 2 Jul 2025. 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-2025-38091 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-2025-38091/ (Markdown: https://insights.sbomify.com/CVE-2025-38091/index.md)","id":"CVE-2025-38091","markdown":"https://insights.sbomify.com/CVE-2025-38091/index.md","name":"CVE-2025-38091","record":{"aliases":["BELL-CVE-2025-38091","DEBIAN-CVE-2025-38091","GHSA-2hx2-mhgc-wx7q","ROOT-OS-DEBIAN-12-CVE-2025-38091","ROOT-OS-UBUNTU-2204-CVE-2025-38091","ROOT-OS-UBUNTU-2404-CVE-2025-38091","UBUNTU-CVE-2025-38091"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"low_privilege","summary":"A missing check in the AMD display driver causes a kernel warning and potential crash during GPU reset, requiring a patch.","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":"nvd","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/amd/display: check stream id dml21 wrapper to get plane_id\n\n[Why \u0026 How]\nFix a false positive warning which occurs due to lack of correct checks\nwhen querying plane_id in DML21. This fixes the warning when performing a\nmode1 reset (cat /sys/kernel/debug/dri/1/amdgpu_gpu_recover):\n\n[   35.751250] WARNING: CPU: 11 PID: 326 at /tmp/amd.PHpyAl7v/amd/amdgpu/../display/dc/dml2/dml2_dc_resource_mgmt.c:91 dml2_map_dc_pipes+0x243d/0x3f40 [amdgpu]\n[   35.751434] Modules linked in: amdgpu(OE) amddrm_ttm_helper(OE) amdttm(OE) amddrm_buddy(OE) amdxcp(OE) amddrm_exec(OE) amd_sched(OE) amdkcl(OE) drm_suballoc_helper drm_ttm_helper ttm drm_display_helper cec rc_core i2c_algo_bit rfcomm qrtr cmac algif_hash algif_skcipher af_alg bnep amd_atl intel_rapl_msr intel_rapl_common snd_hda_codec_hdmi snd_hda_intel edac_mce_amd snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec kvm_amd snd_hda_core snd_hwdep snd_pcm kvm snd_seq_midi snd_seq_midi_event snd_rawmidi crct10dif_pclmul polyval_clmulni polyval_generic btusb ghash_clmulni_intel sha256_ssse3 btrtl sha1_ssse3 snd_seq btintel aesni_intel btbcm btmtk snd_seq_device crypto_simd sunrpc cryptd bluetooth snd_timer ccp binfmt_misc rapl snd i2c_piix4 wmi_bmof gigabyte_wmi k10temp i2c_smbus soundcore gpio_amdpt mac_hid sch_fq_codel msr parport_pc ppdev lp parport efi_pstore nfnetlink dmi_sysfs ip_tables x_tables autofs4 hid_generic usbhid hid crc32_pclmul igc ahci xhci_pci libahci xhci_pci_renesas video wmi\n[   35.751501] CPU: 11 UID: 0 PID: 326 Comm: kworker/u64:9 Tainted: G           OE      6.11.0-21-generic #21~24.04.1-Ubuntu\n[   35.751504] Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE\n[   35.751505] Hardware name: Gigabyte Technology Co., Ltd. X670E AORUS PRO X/X670E AORUS PRO X, BIOS F30 05/22/2024\n[   35.751506] Workqueue: amdgpu-reset-dev amdgpu_debugfs_reset_work [amdgpu]\n[   35.751638] RIP: 0010:dml2_map_dc_pipes+0x243d/0x3f40 [amdgpu]\n[   35.751794] Code: 6d 0c 00 00 8b 84 24 88 00 00 00 41 3b 44 9c 20 0f 84 fc 07 00 00 48 83 c3 01 48 83 fb 06 75 b3 4c 8b 64 24 68 4c 8b 6c 24 40 \u003c0f\u003e 0b b8 06 00 00 00 49 8b 94 24 a0 49 00 00 89 c3 83 f8 07 0f 87\n[   35.751796] RSP: 0018:ffffbfa3805d7680 EFLAGS: 00010246\n[   35.751798] RAX: 0000000000010000 RBX: 0000000000000006 RCX: 0000000000000000\n[   35.751799] RDX: 0000000000000000 RSI: 0000000000000005 RDI: 0000000000000000\n[   35.751800] RBP: ffffbfa3805d78f0 R08: 0000000000000000 R09: 0000000000000000\n[   35.751801] R10: 0000000000000000 R11: 0000000000000000 R12: ffffbfa383249000\n[   35.751802] R13: ffffa0e68f280000 R14: ffffbfa383249658 R15: 0000000000000000\n[   35.751803] FS:  0000000000000000(0000) GS:ffffa0edbe580000(0000) knlGS:0000000000000000\n[   35.751804] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[   35.751805] CR2: 00005d847ef96c58 CR3: 000000041de3e000 CR4: 0000000000f50ef0\n[   35.751806] PKRU: 55555554\n[   35.751807] Call Trace:\n[   35.751810]  \u003cTASK\u003e\n[   35.751816]  ? show_regs+0x6c/0x80\n[   35.751820]  ? __warn+0x88/0x140\n[   35.751822]  ? dml2_map_dc_pipes+0x243d/0x3f40 [amdgpu]\n[   35.751964]  ? report_bug+0x182/0x1b0\n[   35.751969]  ? handle_bug+0x6e/0xb0\n[   35.751972]  ? exc_invalid_op+0x18/0x80\n[   35.751974]  ? asm_exc_invalid_op+0x1b/0x20\n[   35.751978]  ? dml2_map_dc_pipes+0x243d/0x3f40 [amdgpu]\n[   35.752117]  ? math_pow+0x48/0xa0 [amdgpu]\n[   35.752256]  ? srso_alias_return_thunk+0x5/0xfbef5\n[   35.752260]  ? math_pow+0x48/0xa0 [amdgpu]\n[   35.752400]  ? srso_alias_return_thunk+0x5/0xfbef5\n[   35.752403]  ? math_pow+0x11/0xa0 [amdgpu]\n[   35.752524]  ? srso_alias_return_thunk+0x5/0xfbef5\n[   35.752526]  ? core_dcn4_mode_programming+0xe4d/0x20d0 [amdgpu]\n[   35.752663]  ? srso_alias_return_thunk+0x5/0xfbef5\n[   35.752669]  dml21_validate+0x3d4/0x980 [amdgpu]\n\n(cherry picked from commit f8ad62c0a93e5dd94243e10f1b742232e4d6411e)","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/amd/display: check stream id dml21 wrapper to get plane_id","id":"CVE-2025-38091","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"null_dereference","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"ksmbd: use list_first_entry_or_null for opinfo_get_list()","id":"CVE-2025-38092"},"packages":[],"prev":{"headline":"drivers/rapidio/rio_cm.c: prevent possible heap overwrite","id":"CVE-2025-38090"},"products":["Linux"],"published":"2025-07-02","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"A missing check in the AMD display driver causes a kernel warning and potential crash during GPU reset, requiring a patch.","url":"https://insights.sbomify.com/CVE-2025-38091/"}