{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98361 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98361 is a high-severity vulnerability in Linux, published on 6 Oct 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-98361 and fix it if it is affected.\n\nWhat it is: CVE-2026-98361 is a high-severity vulnerability in Linux, published on 6 Oct 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-98361 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-98361/ (Markdown: https://insights.sbomify.com/CVE-2026-98361/index.md)","id":"CVE-2026-98361","markdown":"https://insights.sbomify.com/CVE-2026-98361/index.md","name":"CVE-2026-98361","record":{"aliases":["BELL-CVE-2026-98361","DEBIAN-CVE-2026-98361","GHSA-g3wm-757g-9p35","UBUNTU-CVE-2026-98361"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["privilege_escalation","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel RDMA","requires_auth":"low_privilege","summary":"An unprivileged user can overwrite read-only file pages via RDMA ODP, enabling privilege escalation by modifying sensitive files like setuid binaries.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","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\nRDMA/rxe: Restore HMM_PFN_WRITE check in ODP write paths\n\nCommit 0b261d7c1cd3 (\"RDMA/rxe: Break endless pagefault loop for RO\npages\") dropped the access permission test from rxe_check_pagefault()\nand left only HMM_PFN_VALID. A page faulted in read-only, for example\na page-cache folio behind a PROT_READ file mapping, then satisfies the\ncheck and ODP write operations (RDMA WRITE, RDMA READ response, SEND\npayload, atomics) modify it through kmap without ever breaking CoW.\n\nAn unprivileged user can register an ODP MR over such a mapping and\nhave incoming RDMA traffic overwrite the page cache of a file it only\nholds O_RDONLY, including /etc/passwd or setuid binaries. This is the\nsame primitive class as Dirty COW and CVE-2022-2590.\n\nmlx5 has the missing invariant: its ODP path sets the device write bit\nonly for pfns that carry HMM_PFN_WRITE. Restore it in rxe by requiring\nHMM_PFN_WRITE in rxe_check_pagefault() for every operation except\nRXE_PAGEFAULT_RDONLY. A write to a non-writable VMA now fails the one\nfault attempt with -EPERM from hmm_vma_fault() instead of re-faulting\nforever. For a writable VMA the fault breaks CoW and the write lands\nin the private page.\n\nKeep pmem flushes on the read-only check. arch_wb_cache_pmem() never\nmodifies memory, and the FLUSH access bits do not make the umem\nwritable, so classifying flushes as writes would make every flush\nagainst a flush-only MR fail.","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":"RDMA/rxe: Restore HMM_PFN_WRITE check in ODP write paths","id":"CVE-2026-98361","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"clk: scpi: bound-check DVFS index in scpi_dvfs_recalc_rate","id":"CVE-2026-98362"},"packages":[],"prev":{"headline":"RDMA/rxe: insert mcg into mcg_tree only after rxe_mcast_add() succeeds","id":"CVE-2026-98360"},"products":["Linux"],"published":"2026-10-06","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"An unprivileged user can overwrite read-only file pages via RDMA ODP, enabling privilege escalation by modifying sensitive files like setuid binaries.","url":"https://insights.sbomify.com/CVE-2026-98361/"}