{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-46268 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-46268 is a medium-severity vulnerability in Linux kernel, published on 3 Jun 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-46268 and fix it if it is affected.\n\nWhat it is: CVE-2026-46268 is a medium-severity vulnerability in Linux kernel, published on 3 Jun 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-46268 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-46268/ (Markdown: https://insights.sbomify.com/CVE-2026-46268/index.md)","id":"CVE-2026-46268","markdown":"https://insights.sbomify.com/CVE-2026-46268/index.md","name":"CVE-2026-46268","record":{"aliases":["BELL-CVE-2026-46268","DEBIAN-CVE-2026-46268","GHSA-9f46-h8mj-93v5","UBUNTU-CVE-2026-46268"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A logic error in the Linux kernel PCI/P2PDMA driver triggers a warning when debug VM options are enabled, potentially causing system instability.","user_interaction":"not_required","vuln_class":"other"},"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\nPCI/P2PDMA: Fix p2pmem_alloc_mmap() warning condition\n\nCommit b7e282378773 has already changed the initial page refcount of\np2pdma page from one to zero, however, in p2pmem_alloc_mmap() it uses\n\"VM_WARN_ON_ONCE_PAGE(!page_ref_count(page))\" to assert the initial page\nrefcount should not be zero and the following will be reported when\nCONFIG_DEBUG_VM is enabled:\n\n  page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x380400000\n  flags: 0x20000000002000(reserved|node=0|zone=4)\n  raw: 0020000000002000 ff1100015e3ab440 0000000000000000 0000000000000000\n  raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000\n  page dumped because: VM_WARN_ON_ONCE_PAGE(!page_ref_count(page))\n  ------------[ cut here ]------------\n  WARNING: CPU: 5 PID: 449 at drivers/pci/p2pdma.c:240 p2pmem_alloc_mmap+0x83a/0xa60\n\nFix by using \"page_ref_count(page)\" as the assertion condition.","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":"PCI/P2PDMA: Fix p2pmem_alloc_mmap() warning condition","id":"CVE-2026-46268","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"other","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"pinctrl: canaan: k230: Fix NULL pointer dereference when parsing devicetree","id":"CVE-2026-46269"},"packages":[],"prev":{"headline":"nfc: hci: shdlc: Stop timers and work before freeing context","id":"CVE-2026-46267"},"products":["Linux"],"published":"2026-06-03","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-06-03","vendors":["Linux"]},"summary":"A logic error in the Linux kernel PCI/P2PDMA driver triggers a warning when debug VM options are enabled, potentially causing system instability.","url":"https://insights.sbomify.com/CVE-2026-46268/"}