[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025041624-CVE-2025-22112-845f@gregkh>
Date: Wed, 16 Apr 2025 16:13:23 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2025-22112: eth: bnxt: fix out-of-range access of vnic_info array
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
eth: bnxt: fix out-of-range access of vnic_info array
The bnxt_queue_{start | stop}() access vnic_info as much as allocated,
which indicates bp->nr_vnics.
So, it should not reach bp->vnic_info[bp->nr_vnics].
The Linux kernel CVE team has assigned CVE-2025-22112 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.14 with commit 661958552eda5bf64bfafb4821cbdded935f1f68 and fixed in 6.14.2 with commit b1e081d331ab3a0dea25425f2b6ddeb365fc9d22
Issue introduced in 6.14 with commit 661958552eda5bf64bfafb4821cbdded935f1f68 and fixed in 6.15-rc1 with commit 919f9f497dbcee75d487400e8f9815b74a6a37df
Issue introduced in 6.12.20 with commit a6604717850e4c0fe39bd6084cfbc1bfc445d2b5
Issue introduced in 6.13.8 with commit b730dcab64d5f113af347cf8de696dab6ce88542
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2025-22112
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/net/ethernet/broadcom/bnxt/bnxt.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/b1e081d331ab3a0dea25425f2b6ddeb365fc9d22
https://git.kernel.org/stable/c/919f9f497dbcee75d487400e8f9815b74a6a37df
Powered by blists - more mailing lists