{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-68239 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-68239 is a vulnerability in Linux, published on 10 Aug 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-68239 and fix it if it is affected.\n\nWhat it is: CVE-2026-68239 is a vulnerability in Linux, published on 10 Aug 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-68239 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-68239/ (Markdown: https://insights.sbomify.com/CVE-2026-68239/index.md)","id":"CVE-2026-68239","markdown":"https://insights.sbomify.com/CVE-2026-68239/index.md","name":"CVE-2026-68239","record":{"aliases":["BELL-CVE-2026-68239","DEBIAN-CVE-2026-68239","GHSA-9454-9rqj-9cxx","UBUNTU-CVE-2026-68239"],"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 null pointer dereference in the Linux kernel's TTM memory management allows local attackers to cause a system crash via general protection fault.","user_interaction":"not_required","vuln_class":"null_dereference"},"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/ttm: Account for NULL and handle pages in ttm_pool_backup\n\nPages in ttm_pool_backup can be NULL or backup handles\n(ttm_backup_page_ptr_is_handle()), neither of which can be passed to\nset_pages_array_wb() or freed. Add a dedicated WB pass before the\ndma/purge loop that walks allocations using the same i += num_pages\nstride, skipping NULL and handle entries, and calls set_pages_array_wb()\nonce per contiguous run of real pages. Apply the same NULL/handle guard\nto the dma/purge loop.\n\nFixes the following oops:\n\nOops: general protection fault, kernel NULL pointer dereference 0x0: 0000 [#1] SMP NOPTI\nRIP: 0010:__cpa_process_fault+0xf8/0x770\nRSP: 0018:ffffc90000a87718 EFLAGS: 00010287\nRAX: 0000000000000000 RBX: ffffc90000a87868 RCX: 0000000000000000\nRDX: 0000000000001000 RSI: 0005088000000000 RDI: ffffffff827c5f34\nRBP: 0005088000000000 R08: ffffc90000a877cb R09: ffffc90000a877d0\nR10: 0000000000000000 R11: 000000000000001b R12: 000ffffffffff000\nR13: ffffc90000a87868 R14: ffffc90000a87868 R15: ffff88815b882ae0\nFS:  0000000000000000(0000) GS:ffff8884ec840000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f930b844000 CR3: 000000000262e003 CR4: 0000000008f70ef0\nPKRU: 55555554\nCall Trace:\n \u003cTASK\u003e\n __change_page_attr_set_clr+0x989/0xe90\n ? __purge_vmap_area_lazy+0x6c/0x3a0\n ? _vm_unmap_aliases+0x250/0x2a0\n set_pages_array_wb+0x7f/0x120\n ttm_pool_backup+0x4c9/0x5b0 [ttm]\n ? dma_resv_wait_timeout+0x3b/0xf0\n ttm_tt_backup+0x32/0x60 [ttm]\n ttm_bo_shrink+0x66/0x110 [ttm]\n xe_bo_shrink_purge+0x12b/0x1b0 [xe]\n xe_bo_shrink+0xbb/0x270 [xe]\n __xe_shrinker_walk+0xf7/0x160 [xe]\n xe_shrinker_walk+0x9d/0xc0 [xe]\n xe_shrinker_scan+0x11f/0x210 [xe]\n do_shrink_slab+0x13b/0x270\n shrink_slab+0xf1/0x400\n shrink_node+0x352/0x8a0\n balance_pgdat+0x32c/0x700\n kswapd+0x205/0x2f0\n ? __pfx_autoremove_wake_function+0x10/0x10\n ? __pfx_kswapd+0x10/0x10\n kthread+0xd1/0x110\n ? __pfx_kthread+0x10/0x10\n ret_from_fork+0x1b1/0x200\n ? __pfx_kthread+0x10/0x10\n ret_from_fork_asm+0x1a/0x30\n \u003c/TASK\u003e","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/ttm: Account for NULL and handle pages in ttm_pool_backup","id":"CVE-2026-68239","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"drm/gpusvm: publish dpagemap early to avoid device mapping leak on error","id":"CVE-2026-68240"},"packages":[],"prev":{"headline":"drm/amdgpu: Release VFCT ACPI table reference","id":"CVE-2026-68238"},"products":["Linux"],"published":"2026-08-10","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-08-17","vendors":["Linux"]},"summary":"A null pointer dereference in the Linux kernel's TTM memory management allows local attackers to cause a system crash via general protection fault.","url":"https://insights.sbomify.com/CVE-2026-68239/"}