{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98106 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98106 is a vulnerability in Linux, published on 25 Sep 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-98106 and fix it if it is affected.\n\nWhat it is: CVE-2026-98106 is a vulnerability in Linux, published on 25 Sep 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-98106 in the wild and no public exploit code.\n\nAffected product: Linux. 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-98106/ (Markdown: https://insights.sbomify.com/CVE-2026-98106/index.md)","id":"CVE-2026-98106","markdown":"https://insights.sbomify.com/CVE-2026-98106/index.md","name":"CVE-2026-98106","record":{"aliases":["BELL-CVE-2026-98106","DEBIAN-CVE-2026-98106","GHSA-94vc-8r96-mrjf","UBUNTU-CVE-2026-98106"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A race condition in the Linux kernel DRM pagemap allows local attackers to trigger a soft lockup and RCU stall via double migration of device pages.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/pagemap: Prevent double migration of device pages\n\nA device-private folio migrated to system memory by a CPU fault can\nremain reachable through the raw-PFN eviction path until migration\nfinalization drops the source reference.\n\nIf eviction selects the same device-private folio during this window,\nit can attempt to migrate the folio again. The second migration can leave\nan uncharged folio on an LRU list, causing folio_lruvec_lock_irqsave() to\nretry indefinitely and resulting in a soft lockup and RCU stall.\n\nMark successfully migrated device-private folios using a low bit of\ntheir zone_device_data before migration finalization. Make both CPU-fault\nand raw-PFN migration paths skip device-private folios carrying this\nflag.\n\nMask the flag when retrieving the drm_pagemap_zdd pointer and preserve\nit when a device-private folio is split. Keeping the state on the physical\nfolio also avoids depending on a virtual address that may change before a\nfault occurs.\n\nv2:\n- Replace the retired-PFN XArray with an embedded bitmap. (Matthew Brost)\n- Mark every base page covered by a migrated folio so retirement remains\n  valid if the folio is later split.\n\nv3:\n- Store the migrated state in a low bit of zone_device_data instead of\n  adding virtual-range and bitmap tracking to the ZDD. (Matthew Brost)\n- Mask the flag when retrieving the ZDD and preserve it when splitting\n  a folio.\n- Drop the pre-existing fixes already covered by Matthew Brost's series:\n  https://patchwork.freedesktop.org/series/171651/\n\nv4:\n- Advance by the folio size only for migration entries marked with\n  MIGRATE_PFN_COMPOUND. (Sashiko)\n\nv5:\n- Simplify ZDD flag updates and folio iteration. (Matthew Brost)\n- Skip retired device-private folios in the CPU-fault path. (Matthew Brost)\n- Preserve flag bits while taking a new ZDD reference for split folios.\n\nv6:\n- Restore MIGRATE_PFN_COMPOUND-aware stepping so non-compound migration\n  entries are processed one at a time. (Sashiko)\n- Drop the pre-existing fixes already covered by Matthew Brost's series:\n  https://patchwork.freedesktop.org/series/171651/\n\nThe lockup was observed as:\n[10109.860465] watchdog: BUG: soft lockup - CPU#9 stuck for 26s! [kworker/u65:5:6557]\n[10109.860524] Tainted: [S]=CPU_OUT_OF_SPEC, [O]=OOT_MODULE\n[10109.860524] Hardware name: ASUS System Product Name/PRIME Z790-P WIFI, BIOS 0812 02/24/2023\n[10109.860525] Workqueue: xe_page_fault_work_queue xe_pagefault_queue_work [xe]\n[10109.860644] RIP: 0010:_raw_spin_unlock_irqrestore+0x57/0x80\n[10109.860655] Call Trace:\n[10109.860655]  \u003cTASK\u003e\n[10109.860657]  folio_lruvec_lock_irqsave+0x216/0x220\n[10109.860661]  ? __pfx_lru_add+0x10/0x10\n[10109.860665]  folio_batch_move_lru+0xc8/0x450\n[10109.860670]  ? lock_acquire+0xc4/0x2d0\n[10109.860674]  ? __folio_batch_add_and_move+0x60/0x2e0\n[10109.860677]  ? folio_migrate_mapping+0xa6/0x110\n[10109.860679]  ? folio_migrate_flags+0x13b/0x1b0\n[10109.860681]  ? __pfx_lru_add+0x10/0x10\n[10109.860683]  __folio_batch_add_and_move+0xe7/0x2e0\n[10109.860685]  ? dma_iova_try_alloc+0xb0/0x140\n[10109.860689]  folio_add_lru+0x64/0x80\n[10109.860691]  __migrate_device_finalize+0x12c/0x270\n[10109.860695]  migrate_device_finalize+0x10/0x20\n[10109.860698]  drm_pagemap_evict_to_ram+0x185/0x370 [drm_gpusvm_helper]\n[10109.860704]  ? drm_pagemap_evict_to_ram+0x96/0x370 [drm_gpusvm_helper]\n[10109.860709]  xe_svm_bo_evict+0x15/0x20 [xe]\n[10109.860819]  ? xe_svm_bo_evict+0x15/0x20 [xe]\n[10109.860921]  xe_bo_move+0x107e/0x1570 [xe]\n[10109.860992]  ? xe_ttm_tt_create+0x168/0x340 [xe]\n[10109.861059]  ? __up_read+0x98/0x2b0\n[10109.861061]  ? lock_is_held_type+0xa3/0x130\n[10109.861067]  ttm_bo_handle_move_mem+0xe8/0x1e0 [ttm]\n[10109.861075]  ttm_bo_evict+0x141/0x1c0 [ttm]\n[10109.861081]  ttm_bo_evict_cb+0x9f/0x100 [ttm]\n[10109.861086]  ttm_lru_walk_for_evict+0x84/0x190 [ttm]\n[10109.861091]  ? xe_ttm_vram_mgr_new+0x258/0x3a0 [xe]\n[10109.861198]  ttm_bo_alloc_resource+0x219/0\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/pagemap: Prevent double migration of device pages","id":"CVE-2026-98106","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Bluetooth: L2CAP: fix out-of-bounds write in l2cap_ecred_connect","id":"CVE-2026-98107"},"packages":[],"prev":{"headline":"net: ethernet: oa_tc6: Improve the error recovery","id":"CVE-2026-98105"},"products":["Linux"],"published":"2026-09-25","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A race condition in the Linux kernel DRM pagemap allows local attackers to trigger a soft lockup and RCU stall via double migration of device pages.","url":"https://insights.sbomify.com/CVE-2026-98106/"}