CVE-2026-72045 Affecting kernel-zfcpdump-devel-matched package, versions <0:5.14.0-687.48.1.el9_8


Severity

Recommended
high

Based on Rocky Linux security rating.

Threat Intelligence

EPSS
0.17% (7th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ROCKY9-KERNELZFCPDUMPDEVELMATCHED-19880467
  • published17 Sept 2026
  • disclosed15 Aug 2026

Introduced: 15 Aug 2026

CVE-2026-72045  (opens in a new tab)

How to fix?

Upgrade Rocky-Linux:9 kernel-zfcpdump-devel-matched to version 0:5.14.0-687.48.1.el9_8 or higher.
This issue was patched in RLSA-2026:67470.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-zfcpdump-devel-matched package and not the kernel-zfcpdump-devel-matched package as distributed by Rocky-Linux. See How to fix? for Rocky-Linux:9 relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1