CVE-2026-74584

CVE CVE-2026-74584EUVD EUVD-2026-64332Published 2026-08-22T14:28:07.000ZLast changed 2026-08-25T05:40:11.000ZCVSS 7.1

What the advisory describes

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().

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux 1ac5a404797523cedaf424a3aaa3cf8f9548dff8 <9128c2411b83a64c0a69d2ff059c741bde25a9cc; 1ac5a404797523cedaf424a3aaa3cf8f9548dff8 <f6b079629becfa977f9c51fe53ad2e6dcc55ef44; 1ac5a404797523cedaf424a3aaa3cf8f9548dff8 <c75f8ce4baa29ae57fe615c6a2c5101f59b8b89a; patch: 7.1; 1ac5a404797523cedaf424a3aaa3cf8f9548dff8 <a3ed2daab02b2a706e882ad31b5c3c4f33cb5bb1; 1ac5a404797523cedaf424a3aaa3cf8f9548dff8 <c19b360fa10c521c0b681875cdaa51545d45a491; patch: 0; patch: 6.1.177; patch: 6.12.95; patch: 5.10.260; patch: 6.18.37; patch: 7.0.14; patch: 5.15.211; 4.11; 1ac5a404797523cedaf424a3aaa3cf8f9548dff8 <e2b143df29003d2704b51f62e9297006953dbacb; patch: 6.6.144; 1ac5a404797523cedaf424a3aaa3cf8f9548dff8 <9896bdfd21d918e9f26a52bc6109cc77970ee0b1; 1ac5a404797523cedaf424a3aaa3cf8f9548dff8 <53c97e9882f4e747b4ac31b211317c2eba541af9

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.