high 7.8

CVE-2022-48980 json

net: dsa: sja1105: avoid out of bounds access in sja1105_init_l2_policing()

published 2024-10-21 2 y ago modified 2026-06-17 4 mo ago also EUVD-2022-53859

cvss: 7.8; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.2%; EPSS 0.2% chance of exploitation in 30 days, percentile 15%
public exploits: 0; none known

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

The SJA1105 family has 45 L2 policing table entries (SJA1105_MAX_L2_POLICING_COUNT) and SJA1110 has 110 (SJA1110_MAX_L2_POLICING_COUNT). Keeping the table structure but accounting for the difference in port count (5 in SJA1105 vs 10 in SJA1110) does not fully explain the difference. Rather, the SJA1110 also has L2 ingress policers for multicast traffic. If a packet is classified as multicast, it will be processed by the policer index 99 + SRCPORT.

The sja1105_init_l2_policing() function initializes all L2 policers such that they don't interfere with normal packet reception by default. To have a common code between SJA1105 and SJA1110, the index of the multicast policer for the port is calculated because it's an index that is out of bounds for SJA1105 but in bounds for SJA1110, and a bounds check is performed.

The code fails to do the proper thing when determining what to do with the multicast policer of port 0 on SJA1105 (ds->num_ports = 5). The "mcast" index will be equal to 45, which is also equal to table->ops->max_entry_count (SJA1105_MAX_L2_POLICING_COUNT). So it passes through the check. But at the same time, SJA1105 doesn't have multicast policers. So the code programs the SHARINDX field of an out-of-bounds element in the L2 Policing table of the static config.

The comparison between index 45 and 45 entries should have determined the code to not access this policer index on SJA1105, since its memory wasn't even allocated.

With enough bad luck, the out-of-bounds write could even overwrite other valid kernel data, but in this case, the issue was detected using KASAN.

Kernel log:

sja1105 spi5.0: Probed switch chip: SJA1105Q ================================================================== BUG: KASAN: slab-out-of-bounds in sja1105_setup+0x1cbc/0x2340 Write of size 8 at addr ffffff880bd57708 by task kworker/u8:0/8 ... Workqueue: events_unbound deferred_probe_work_func Call trace: ... sja1105_setup+0x1cbc/0x2340 dsa_register_switch+0x1284/0x18d0 sja1105_probe+0x748/0x840 ... Allocated by task 8: ... sja1105_setup+0x1bcc/0x2340 dsa_register_switch+0x1284/0x18d0 sja1105_probe+0x748/0x840 ...

Patch / fix

fixed in 1 distros 3 links 3

Linux Linux 5.15.83, 6.0.13, 6.1

debian ubuntu suse

linux Debian 14, Debian 13, Debian 12 6.1.4-1

debian advisories DEBIAN-CVE-2022-48980

linux Ubuntu 22.04 LTS 5.15.0-67.74
linux-aws Ubuntu 22.04 LTS 5.15.0-1031.35
linux-gcp Ubuntu 22.04 LTS 5.15.0-1030.37
linux-gke Ubuntu 22.04 LTS 5.15.0-1028.33
linux-ibm Ubuntu 22.04 LTS 5.15.0-1026.29
linux-kvm Ubuntu 22.04 LTS 5.15.0-1029.34
linux-azure Ubuntu 22.04 LTS 5.15.0-1034.41
linux-gkeop Ubuntu 22.04 LTS 5.15.0-1016.21

ubuntu advisories UBUNTU-CVE-2022-48980

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

kernel-64kb SLE Module for Basesystem 15 SP5 5.14.21-150500.55.88.1
kernel-syms SLE Module for Development Tools 15 SP5 5.14.21-150500.55.88.1
kernel-source SLE Module for Development Tools 15 SP5, SLE Module for Basesystem 15 SP5 5.14.21-150500.55.88.1
kernel-default SLE Module for Legacy 15 SP5, SLE Module for Basesystem 15 SP5, SLE Micro 5.5 +2 more 5.14.21-150500.55.88.1
kernel-zfcpdump SLE Module for Basesystem 15 SP5 5.14.21-150500.55.88.1
kernel-obs-build SLE Module for Development Tools 15 SP5 5.14.21-150500.55.88.1
kernel-default-base SLE Module for Basesystem 15 SP5, SLE Micro 5.5 5.14.21-150500.55.88.1.150500.6.39.4
kernel-rt SLE Micro 5.5, Real Time Module 15 SP5, openSUSE Leap Micro 5.5 +1 more 5.14.21-150500.13.76.1

suse advisories SUSE-SU-2024:4364-1 SUSE-SU-2024:3985-1 SUSE-SU-2024:3983-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-48980 updated 2026-11-05 cvss 7.8

kernel: net: dsa: sja1105: avoid out of bounds access in sja1105_init_l2_policing()

Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more
not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 2 y ago (2024-10-22)

Exploit prediction

0.24% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
NVD	3.1	7.8	CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

Linux Linux

Classification

Weakness

CWE-787 Out-of-bounds Write

Technology feeds

Linux kernel rss critical rss

References

Sources

CVE List CVE-2022-48980
NVD CVE-2022-48980

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary