{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-53187 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-53187 is a high-severity memory corruption vulnerability in Linux kernel, published on 25 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-53187 and fix it if it is affected.\n\nWhat it is: CVE-2026-53187 is a high-severity memory corruption vulnerability in Linux kernel, published on 25 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-53187 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-53187/ (Markdown: https://insights.sbomify.com/CVE-2026-53187/index.md)","id":"CVE-2026-53187","markdown":"https://insights.sbomify.com/CVE-2026-53187/index.md","name":"CVE-2026-53187","record":{"aliases":["BELL-CVE-2026-53187","DEBIAN-CVE-2026-53187","GHSA-rc47-m48r-2657","UBUNTU-CVE-2026-53187"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel RDMA","requires_auth":"low_privilege","summary":"A local attacker can trigger an out-of-bounds read or kernel panic in the Linux kernel RDMA subsystem by providing an invalid CPU ID during DMA handle allocation.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/core: Validate cpu_id against nr_cpu_ids in DMAH alloc\n\nThe cpu_id attribute supplied by user space through\nUVERBS_ATTR_ALLOC_DMAH_CPU_ID is passed directly to cpumask_test_cpu()\nwithout first verifying that the value is within the valid CPU range.\n\nPassing such untrusted data to cpumask_test_cpu() may lead to an\nout-of-bounds read of the underlying cpumask bitmap: the helper expands\nto a test_bit() that indexes the bitmap by cpu_id / BITS_PER_LONG with\nno bound check.\n\nIn addition, on kernels built with CONFIG_DEBUG_PER_CPU_MAPS it trips\nthe WARN_ON_ONCE() in cpumask_check(); combined with panic_on_warn this\nturns a bad user input into a machine reboot.\n\nReject any cpu_id that is not smaller than nr_cpu_ids with -EINVAL\nbefore it is used.\n\nReported by Smatch.","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/core: Validate cpu_id against nr_cpu_ids in DMAH alloc","id":"CVE-2026-53187","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"RDMA/core: Validate the passed in fops for ib_get_ucaps()","id":"CVE-2026-53188"},"packages":[],"prev":{"headline":"RDMA/srp: bound SRP_RSP sense copy by the received length","id":"CVE-2026-53186"},"products":["Linux"],"published":"2026-06-25","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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A local attacker can trigger an out-of-bounds read or kernel panic in the Linux kernel RDMA subsystem by providing an invalid CPU ID during DMA handle allocation.","url":"https://insights.sbomify.com/CVE-2026-53187/"}