RDMA/bnxt_re: Initialize dpi variable to zero
CVE-2026-72501 is fixed in 16 products on 1 platform, first by DEBIAN-CVE-2026-72501, released August 15, 2026. It is not reported as exploited. Patch Radar priority: Routine.
In the Linux kernel, the following vulnerability has been resolved: RDMA/bnxt_re: Initialize dpi variable to zero dpi is initialized only for BNXT_RE_ALLOC_WC_PAGE, but copied for all the cases. So initialize the dpi to 0.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| dtb-aarch64 · opensuse-leap 16.0 | 6.12.0-160000.38.1 | OPENSUSE-SU-2026:21910-1 | Sep 22, 2026 |
| kernel-64kb · opensuse-leap 16.0 | 6.12.0-160000.38.1 | OPENSUSE-SU-2026:21910-1 | Sep 22, 2026 |
| kernel-64kb · sles 15.7 | 6.4.0-150700.53.81.1 | SUSE-SU-2026:4254-1 | Oct 7, 2026 |
| kernel-64kb · sles 16.0 | 6.12.0-160000.38.1 | SUSE-SU-2026:23902-1 | Sep 22, 2026 |
| kernel-azure · opensuse-leap 16.0 | 6.12.0-160000.38.1 | OPENSUSE-SU-2026:21910-1 | Sep 22, 2026 |
| kernel-azure · sles 15.7 | 6.4.0-150700.53.81.1 | SUSE-SU-2026:4254-1 | Oct 7, 2026 |
| kernel-azure · sles 16.0 | 6.12.0-160000.38.1 | SUSE-SU-2026:23902-1 | Sep 22, 2026 |
| kernel-default · opensuse-leap 16.0 | 6.12.0-160000.38.1 | OPENSUSE-SU-2026:21910-1 | Sep 22, 2026 |
| kernel-default · sles 15.7 | 6.4.0-150700.53.81.1 | SUSE-SU-2026:4254-1 | Oct 7, 2026 |
| kernel-default · sles 16.0 | 6.12.0-160000.38.1 | SUSE-SU-2026:23902-1 | Sep 22, 2026 |
| kernel-default-base · opensuse-leap 16.0 | 6.12.0-160000.38.1.160000.2.22 | OPENSUSE-SU-2026:21910-1 | Sep 22, 2026 |
| kernel-default-base · sles 15.7 | 6.4.0-150700.53.81.1.150700.17.45.1 | SUSE-SU-2026:4254-1 | Oct 7, 2026 |
| kernel-default-base · sles 16.0 | 6.12.0-160000.38.1.160000.2.23 | SUSE-SU-2026:23902-1 | Sep 22, 2026 |
| kernel-docs · opensuse-leap 16.0 | 6.12.0-160000.38.1 | OPENSUSE-SU-2026:21910-1 | Sep 22, 2026 |
| kernel-docs · sles 15.7 | 6.4.0-150700.53.81.1 | SUSE-SU-2026:4254-1 | Oct 7, 2026 |
| kernel-docs · sles 16.0 | 6.12.0-160000.38.1 | SUSE-SU-2026:23902-1 | Sep 22, 2026 |
| kernel-kvmsmall · opensuse-leap 16.0 | 6.12.0-160000.38.1 | OPENSUSE-SU-2026:21910-1 | Sep 22, 2026 |
| kernel-kvmsmall · sles 16.0 | 6.12.0-160000.38.1 | SUSE-SU-2026:23902-1 | Sep 22, 2026 |
| kernel-livepatch-SLE15-SP7-RT_Update_20 · sles 15.7 | 1-150700.1.3.1 | SUSE-SU-2026:4120-1 | Sep 10, 2026 |
| kernel-livepatch-SLE15-SP7_Update_21 · sles 15.7 | 1-150700.15.3.1 | SUSE-SU-2026:4254-1 | Oct 7, 2026 |
| kernel-obs-build · opensuse-leap 16.0 | 6.12.0-160000.38.1 | OPENSUSE-SU-2026:21910-1 | Sep 22, 2026 |
| kernel-obs-build · sles 15.7 | 6.4.0-150700.53.81.1 | SUSE-SU-2026:4254-1 | Oct 7, 2026 |
| kernel-obs-qa · opensuse-leap 16.0 | 6.12.0-160000.38.1 | OPENSUSE-SU-2026:21910-1 | Sep 22, 2026 |
| kernel-obs-qa · sles 16.0 | 6.12.0-160000.38.1 | SUSE-SU-2026:23902-1 | Sep 22, 2026 |
| kernel-rt · opensuse-leap 16.0 | 6.12.0-160000.38.1 | OPENSUSE-SU-2026:21910-1 | Sep 22, 2026 |
| kernel-source · opensuse-leap 16.0 | 6.12.0-160000.38.1 | OPENSUSE-SU-2026:21910-1 | Sep 22, 2026 |
| kernel-source · sles 15.7 | 6.4.0-150700.53.81.1 | SUSE-SU-2026:4254-1 | Oct 7, 2026 |
| kernel-source · sles 16.0 | 6.12.0-160000.38.1 | SUSE-SU-2026:23902-1 | Sep 22, 2026 |
| kernel-syms · opensuse-leap 16.0 | 6.12.0-160000.38.1 | OPENSUSE-SU-2026:21910-1 | Sep 22, 2026 |
| kernel-syms · sles 15.7 | 6.4.0-150700.53.81.1 | SUSE-SU-2026:4254-1 | Oct 7, 2026 |
| kernel-syms · sles 16.0 | 6.12.0-160000.38.1 | SUSE-SU-2026:23902-1 | Sep 22, 2026 |
| kernel-zfcpdump · opensuse-leap 16.0 | 6.12.0-160000.38.1 | OPENSUSE-SU-2026:21910-1 | Sep 22, 2026 |
| kernel-zfcpdump · sles 15.7 | 6.4.0-150700.53.81.1 | SUSE-SU-2026:4254-1 | Oct 7, 2026 |
| kernel-zfcpdump · sles 16.0 | 6.12.0-160000.38.1 | SUSE-SU-2026:23902-1 | Sep 22, 2026 |
| linux · Debian 13.5 (trixie) | 6.12.115-2 | DEBIAN-CVE-2026-72501 | Aug 15, 2026 |
| linux · Debian 14 | 7.1.5-1 | DEBIAN-CVE-2026-72501 | Aug 15, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.