linux-cve-announce - CVE-2026-22982: net: mscc: ocelot: Fix crash when adding interface under a lag

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2026012348-CVE-2026-22982-b250@gregkh>
Date: Fri, 23 Jan 2026 16:24:53 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2026-22982: net: mscc: ocelot: Fix crash when adding interface under a lag

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

net: mscc: ocelot: Fix crash when adding interface under a lag

Commit 15faa1f67ab4 ("lan966x: Fix crash when adding interface under a lag")
fixed a similar issue in the lan966x driver caused by a NULL pointer dereference.
The ocelot_set_aggr_pgids() function in the ocelot driver has similar logic
and is susceptible to the same crash.

This issue specifically affects the ocelot_vsc7514.c frontend, which leaves
unused ports as NULL pointers. The felix_vsc9959.c frontend is unaffected as
it uses the DSA framework which registers all ports.

Fix this by checking if the port pointer is valid before accessing it.

The Linux kernel CVE team has assigned CVE-2026-22982 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 5.12 with commit 528d3f190c98c8f7d9581f68db4af021696727b2 and fixed in 5.15.198 with commit 8767f238b0e6c3d0b295ac6dce9fbe6a99bd1b9d
	Issue introduced in 5.12 with commit 528d3f190c98c8f7d9581f68db4af021696727b2 and fixed in 6.1.161 with commit b17818307446c5a8d925a39a792261dbfa930041
	Issue introduced in 5.12 with commit 528d3f190c98c8f7d9581f68db4af021696727b2 and fixed in 6.6.121 with commit 2985712dc76dfa670eb7fd607c09d4d48e5f5c6e
	Issue introduced in 5.12 with commit 528d3f190c98c8f7d9581f68db4af021696727b2 and fixed in 6.12.66 with commit 03fb1708b7d1e76aecebf767ad059c319845039f
	Issue introduced in 5.12 with commit 528d3f190c98c8f7d9581f68db4af021696727b2 and fixed in 6.18.6 with commit f490af47bbee02441e356a1e0b86e3b3dd5120ff
	Issue introduced in 5.12 with commit 528d3f190c98c8f7d9581f68db4af021696727b2 and fixed in 6.19-rc5 with commit 34f3ff52cb9fa7dbf04f5c734fcc4cb6ed5d1a95

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-2026-22982
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/mscc/ocelot.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/8767f238b0e6c3d0b295ac6dce9fbe6a99bd1b9d
	https://git.kernel.org/stable/c/b17818307446c5a8d925a39a792261dbfa930041
	https://git.kernel.org/stable/c/2985712dc76dfa670eb7fd607c09d4d48e5f5c6e
	https://git.kernel.org/stable/c/03fb1708b7d1e76aecebf767ad059c319845039f
	https://git.kernel.org/stable/c/f490af47bbee02441e356a1e0b86e3b3dd5120ff
	https://git.kernel.org/stable/c/34f3ff52cb9fa7dbf04f5c734fcc4cb6ed5d1a95