RDMA/bnxt_re: zero shared page before exposing to userspace
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.260, 5.15.211, 6.1.177, 6.6.144, 6.12.95, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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().
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From 1ac5a404797523cedaf424a3aaa3cf8f9548dff8 · fixed in 53c97e9882f4e747b4ac31b211317c2eba541af9; From 1ac5a404797523cedaf424a3aaa3cf8f9548dff8 · fixed in 9896bdfd21d918e9f26a52bc6109cc77970ee0b1; From 1ac5a404797523cedaf424a3aaa3cf8f9548dff8 · fixed in 9128c2411b83a64c0a69d2ff059c741bde25a9cc; From 1ac5a404797523cedaf424a3aaa3cf8f9548dff8 · fixed in c19b360fa10c521c0b681875cdaa51545d45a491; From 1ac5a404797523cedaf424a3aaa3cf8f9548dff8 · fixed in a3ed2daab02b2a706e882ad31b5c3c4f33cb5bb1; From 1ac5a404797523cedaf424a3aaa3cf8f9548dff8 · fixed in e2b143df29003d2704b51f62e9297006953dbacb; From 1ac5a404797523cedaf424a3aaa3cf8f9548dff8 · fixed in c75f8ce4baa29ae57fe615c6a2c5101f59b8b89a; From 1ac5a404797523cedaf424a3aaa3cf8f9548dff8 · fixed in f6b079629becfa977f9c51fe53ad2e6dcc55ef44
- Linux Linux
4.11
- KernelLinux
From 4.11.0 · fixed in 5.10.260; From 5.11.0 · fixed in 5.15.211; From 5.16.0 · fixed in 6.1.177; From 6.2.0 · fixed in 6.6.144; From 6.7.0 · fixed in 6.12.95; From 6.13.0 · fixed in 6.18.37; From 6.19.0 · fixed in 7.0.14
References 8
git.kernel.org
- stable/c/53c97e9882f4e747b4ac31b211317c2eba541af9
- stable/c/9896bdfd21d918e9f26a52bc6109cc77970ee0b1
- stable/c/9128c2411b83a64c0a69d2ff059c741bde25a9cc
- stable/c/c19b360fa10c521c0b681875cdaa51545d45a491
- stable/c/a3ed2daab02b2a706e882ad31b5c3c4f33cb5bb1
- stable/c/e2b143df29003d2704b51f62e9297006953dbacb
- stable/c/c75f8ce4baa29ae57fe615c6a2c5101f59b8b89a
- stable/c/f6b079629becfa977f9c51fe53ad2e6dcc55ef44