CVE-2026-52908
What it is
In the Linux kernel, the following vulnerability has been resolved: RDMA: During rereg_mr ensure that REREG_ACCESS is compatible If IB_MR_REREG_ACCESS changes from RO to RW then the umem has to be re-evaluated to ensure it is properly pinned as RW. Since the umem is hidden inside each driver's mr struct add a ib_umem_check_rereg() function that each driver has to call before processing IB_MR_REREG_ACCESS. mlx4 has to retain its duplicate ib_access_writable check because it implements IB_MR_REREG_ACCESS | IB_MR_REREG_TRANS by changing both items in place sequentially while the MR is live, so it will continue to not support this combination.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.1% in the next 30 days (EPSS).
- Severity: 7.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Weakness
- CWE-285
- Record status
- Modified
Affected
- Linux Kernel < 6.6.143
- Linux Kernel < 6.12.94
- Linux Kernel < 6.18.36
- Linux Kernel < 7.0.13
- Linux Kernel 7.1
Attack profile CVSS 3.1 · 7.8
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-52908.md and follow it. Check whether this project is affected by CVE-2026-52908. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/09dc18894148381d3bfc550083b1236043870dce
- https://git.kernel.org/stable/c/2904e985a2917b5dac65df82733065e78a65fc9d
- https://git.kernel.org/stable/c/50334a05a950840b39a1ce3d2a173b4183db9b3e
- https://git.kernel.org/stable/c/badad6fad60def1b9805559dd81dbab3d97b82aa
- https://git.kernel.org/stable/c/eba5df21eda0fe7418efbea2f799f8ea1b8ca94c
References
- https://git.kernel.org/stable/c/09dc18894148381d3bfc550083b1236043870dce
- https://git.kernel.org/stable/c/2904e985a2917b5dac65df82733065e78a65fc9d
- https://git.kernel.org/stable/c/50334a05a950840b39a1ce3d2a173b4183db9b3e
- https://git.kernel.org/stable/c/badad6fad60def1b9805559dd81dbab3d97b82aa
- https://git.kernel.org/stable/c/eba5df21eda0fe7418efbea2f799f8ea1b8ca94c