octeontx2-af: cn10k: restrict VF LMTLINE sharing to its own PF
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 893ae97214c385be02f8ec097298cc48c7f0d905 · < 59da37fee81a8d76079313348ca13c5bc90dd6ae| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
octeontx2-af: cn10k: restrict VF LMTLINE sharing to its own PF
rvu_mbox_handler_lmtst_tbl_setup() uses req->base_pcifunc as a direct index into the LMT map table to read another function's LMTLINE physical base address and copy it into the caller's own LMT map table entry. The mailbox dispatcher authenticates req->hdr.pcifunc from the IRQ source, but req->base_pcifunc is a separate payload field and is not sanitized.
Reject the request with -EPERM when a VF caller's base_pcifunc is not a valid function under its own PF. is_pf_func_valid() bounds the FUNC field to the PF's configured VF count, keeping the computed index inside the caller's own slot block.
From the CVE record · Linux
The octeontx2-af mailbox handler does not validate a VF caller’s base_pcifunc field before using it to look up an LMTLINE physical base address. A VF caller that can send the mailbox request can cause an address from another function to be copied into its own LMT map entry; no user interaction is described.
Engineers running Linux kernels with the octeontx2-af cn10k driver should check whether their kernel includes the fix; affected versions are not specified.