{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-64131 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-64131 is a medium-severity denial of service 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-64131 and fix it if it is affected.\n\nWhat it is: CVE-2026-64131 is a medium-severity denial of service 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-64131 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-64131/ (Markdown: https://insights.sbomify.com/CVE-2026-64131/index.md)","id":"CVE-2026-64131","markdown":"https://insights.sbomify.com/CVE-2026-64131/index.md","name":"CVE-2026-64131","record":{"aliases":["BELL-CVE-2026-64131","DEBIAN-CVE-2026-64131","GHSA-2qhr-9xff-qp48","UBUNTU-CVE-2026-64131"],"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":"low_privilege","summary":"A logic error in the Linux kernel memory management subsystem causes spurious warnings during process teardown, potentially leading to system instability or denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"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":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nmm/memory: fix spurious warning when unmapping device-private/exclusive pages\n\nDevice private and exclusive entries are only supported for anonymous\nfolios.  This condition is tested in __migrate_device_pages() and\nmake_device_exclusive() using folio_test_anon().  However the unmap path\ntests this assumption using vma_is_anonymous().\n\nThis is wrong because whilst anonymous VMAs can only contain folios where\nfolio_test_anon() is true the opposite relation does not hold.  A folio\nfor which folio_test_anon() is true does not imply vma_is_anonymous() is\ntrue.  Such a condition can occur if for example a folio is part of a\nprivate filebacked mapping.\n\nIn this case vma_is_anonymous() is false as the mapping is filebacked, but\nfolio_test_anon() may be true, thus permitting devices to migrate the\nfolio to device private memory.  This can lead to the following spurious\nwarnings during process teardown:\n\n[  772.737706] ------------[ cut here ]------------\n[  772.739201] WARNING: mm/memory.c:1754 at unmap_page_range.cold+0x26/0x18a, CPU#17: hmm-tests/2041\n[  772.742050] Modules linked in: test_hmm nvidia_uvm(O) nvidia(O)\n[  772.743959] CPU: 17 UID: 0 PID: 2041 Comm: hmm-tests Tainted: G        W  O        7.0.0+ #387 PREEMPT(full)\n[  772.747104] Tainted: [W]=WARN, [O]=OOT_MODULE\n[  772.748509] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.17.0-0-gb52ca86e094d-prebuilt.qemu.org 04/01/2014\n[  772.752117] RIP: 0010:unmap_page_range.cold+0x26/0x18a\n[  772.753780] Code: 7e fe ff ff 48 89 4c 24 78 4c 89 44 24 38 e8 f2 ff b1 00 48 8b 4c 24 78 4c 8b 44 24 38 48 8b 44 24 18 48 83 78 48 00 74 04 90 \u003c0f\u003e 0b 90 48 89 ca b8 ff ff 37 00 48 c1 ea 03 48 c1 e0 2a 80 3c 02\n[  772.759602] RSP: 0018:ffff888112607550 EFLAGS: 00010286\n[  772.761310] RAX: ffff88811bbf4dc0 RBX: dffffc0000000000 RCX: ffffea03e9bfffd8\n[  772.763583] RDX: 1ffff1102377e9c1 RSI: 0000000000000008 RDI: ffff88811bbf4e08\n[  772.765914] RBP: 0000000000000006 R08: ffff8881059f7448 R09: ffffed10224c0e68\n[  772.768184] R10: ffff888112607347 R11: 0000000000000001 R12: 0000000000000001\n[  772.770461] R13: ffffea03e9bfffc0 R14: ffff888112607908 R15: ffffea03e9bfffc0\n[  772.772782] FS:  00007f327caa2780(0000) GS:ffff888427b7d000(0000) knlGS:0000000000000000\n[  772.775328] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[  772.777187] CR2: 00007f327ca89000 CR3: 00000001994d5000 CR4: 00000000000006f0\n[  772.779135] Call Trace:\n[  772.779792]  \u003cTASK\u003e\n[  772.780317]  ? dmirror_interval_invalidate+0x1a3/0x290 [test_hmm]\n[  772.781873]  ? vm_normal_page_pud+0x2b0/0x2b0\n[  772.782992]  ? __rwlock_init+0x150/0x150\n[  772.784006]  ? lock_release+0x216/0x2b0\n[  772.785008]  ? __mmu_notifier_invalidate_range_start+0x505/0x6e0\n[  772.786522]  ? lock_release+0x216/0x2b0\n[  772.787498]  ? unmap_single_vma+0xb6/0x210\n[  772.788573]  unmap_vmas+0x27d/0x520\n[  772.789506]  ? unmap_single_vma+0x210/0x210\n[  772.790607]  ? mas_update_gap.part.0+0x620/0x620\n[  772.791834]  unmap_region+0x19e/0x350\n[  772.792769]  ? remove_vma+0x130/0x130\n[  772.793684]  ? mas_alloc_nodes+0x1f2/0x300\n[  772.794730]  vms_complete_munmap_vmas+0x8c1/0xe20\n[  772.795926]  ? unmap_region+0x350/0x350\n[  772.796917]  do_vmi_align_munmap+0x36a/0x4e0\n[  772.798018]  ? lock_release+0x216/0x2b0\n[  772.799024]  ? vma_shrink+0x620/0x620\n[  772.799983]  do_vmi_munmap+0x150/0x2c0\n[  772.800939]  __vm_munmap+0x161/0x2c0\n[  772.801872]  ? expand_downwards+0xd60/0xd60\n[  772.802948]  ? clockevents_program_event+0x1ef/0x540\n[  772.804217]  ? lock_release+0x216/0x2b0\n[  772.805158]  __x64_sys_munmap+0x59/0x80\n[  772.805776]  do_syscall_64+0xfc/0x670\n[  772.806336]  ? irqentry_exit+0xda/0x580\n[  772.806976]  entry_SYSCALL_64_after_hwframe+0x4b/0x53\n[  772.807772] RIP: 0033:0x7f327cbb2717\n[  772.808323] Code: 73 01 c3 48 8b 0d f9 76 0d 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 0b 00 00 00 0f 05 \u003c48\u003e 3d 01 f0 ff\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":"mm/memory: fix spurious warning when unmapping device-private/exclusive pages","id":"CVE-2026-64131","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"ipv6: ioam: refresh hdr pointer before ioam6_event()","id":"CVE-2026-64132"},"packages":[],"prev":{"headline":"mm/page_alloc: fix initialization of tags of the huge zero folio with init_on_free","id":"CVE-2026-64130"},"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-07-19","vendors":["Linux"]},"summary":"A logic error in the Linux kernel memory management subsystem causes spurious warnings during process teardown, potentially leading to system instability or denial of service.","url":"https://insights.sbomify.com/CVE-2026-64131/"}