Linux
RDMA/bnxt_re: zero shared page before exposing to userspace
In the Linux kernel, the following vulnerability has been resolved: RDMA/bnxt_re: zero shared page before exposing to userspace bnxt_re_alloc_ucontext() allocates uctx->shpg via __get_free_page(GFP_KERNEL). The buddy allocator does not zero pages without __GFP_ZERO, so the page contains stale kernel data from whatever object most recently freed it. The page is then mapped into userspace via vm_insert_page() under BNXT_RE_MMAP_SH_PAGE in bnxt_re_mmap(). The driver only ever writes 4 bytes (a u32 AVID) at offset BNXT_RE_AVID_OFFT (0x10) inside bnxt_re_create_ah(); the remaining 4092 bytes of the page are exposed to userspace unsanitised, leaking kernel memory contents. Any user with access to /dev/infiniband/uverbsX on a host with a bnxt_re device (typically rdma group membership) can read this data via a single mmap() at pgoff 0 after IB_USER_VERBS_CMD_GET_CONTEXT. Other shared pages in the same file already use get_zeroed_page() correctly: drivers/infiniband/hw/bnxt_re/ib_verbs.c srq->uctx_srq_page = (void *)get_zeroed_page(GFP_KERNEL); cq->uctx_cq_page = (void *)get_zeroed_page(GFP_KERNEL); uctx->shpg is the only outlier. Bring it in line with the existing convention by switching to get_zeroed_page().
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 1ac5a404797523cedaf424a3aaa3cf8f9548dff8, < 53c97e9882f4e747b4ac31b211317c2eba541af9
- >= 1ac5a404797523cedaf424a3aaa3cf8f9548dff8, < 9896bdfd21d918e9f26a52bc6109cc77970ee0b1
- >= 1ac5a404797523cedaf424a3aaa3cf8f9548dff8, < 9128c2411b83a64c0a69d2ff059c741bde25a9cc
- >= 1ac5a404797523cedaf424a3aaa3cf8f9548dff8, < c19b360fa10c521c0b681875cdaa51545d45a491
- >= 1ac5a404797523cedaf424a3aaa3cf8f9548dff8, < a3ed2daab02b2a706e882ad31b5c3c4f33cb5bb1
- >= 1ac5a404797523cedaf424a3aaa3cf8f9548dff8, < e2b143df29003d2704b51f62e9297006953dbacb
- >= 1ac5a404797523cedaf424a3aaa3cf8f9548dff8, < c75f8ce4baa29ae57fe615c6a2c5101f59b8b89a
- >= 1ac5a404797523cedaf424a3aaa3cf8f9548dff8, < f6b079629becfa977f9c51fe53ad2e6dcc55ef44
Fixed in 53c97e9882f4e747b4ac31b211317c2eba541af9, 9896bdfd21d918e9f26a52bc6109cc77970ee0b1, 9128c2411b83a64c0a69d2ff059c741bde25a9cc, c19b360fa10c521c0b681875cdaa51545d45a491, a3ed2daab02b2a706e882ad31b5c3c4f33cb5bb1, e2b143df29003d2704b51f62e9297006953dbacb, c75f8ce4baa29ae57fe615c6a2c5101f59b8b89a, f6b079629becfa977f9c51fe53ad2e6dcc55ef44
- 4.11
Fixed in 0, 5.10.260, 5.15.211, 6.1.177, 6.6.144, 6.12.95, 6.18.37, 7.0.14, 7.1
Mitigation
Upgrade Linux to 53c97e9882f4e747b4ac31b211317c2eba541af9 or 9896bdfd21d918e9f26a52bc6109cc77970ee0b1 or 9128c2411b83a64c0a69d2ff059c741bde25a9cc or c19b360fa10c521c0b681875cdaa51545d45a491 or a3ed2daab02b2a706e882ad31b5c3c4f33cb5bb1 or e2b143df29003d2704b51f62e9297006953dbacb or c75f8ce4baa29ae57fe615c6a2c5101f59b8b89a or f6b079629becfa977f9c51fe53ad2e6dcc55ef44 or later.
Upgrade Linux to 0 or 5.10.260 or 5.15.211 or 6.1.177 or 6.6.144 or 6.12.95 or 6.18.37 or 7.0.14 or 7.1 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.