CVE-2022-48980

Source
https://nvd.nist.gov/vuln/detail/CVE-2022-48980
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-48980.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2022-48980
Related
Published
2024-10-21T20:15:10Z
Modified
2024-10-25T18:36:00Z
Severity
  • 7.8 (High) CVSS_V3 - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H CVSS Calculator
Summary
[none]
Details

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

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

The SJA1105 family has 45 L2 policing table entries (SJA1105MAXL2POLICINGCOUNT) and SJA1110 has 110 (SJA1110MAXL2POLICINGCOUNT). 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 sja1105initl2_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->numports = 5). The "mcast" index will be equal to 45, which is also equal to table->ops->maxentrycount (SJA1105MAXL2POLICING_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 sja1105setup+0x1cbc/0x2340 Write of size 8 at addr ffffff880bd57708 by task kworker/u8:0/8 ... Workqueue: eventsunbound deferredprobeworkfunc Call trace: ... sja1105setup+0x1cbc/0x2340 dsaregisterswitch+0x1284/0x18d0 sja1105probe+0x748/0x840 ... Allocated by task 8: ... sja1105setup+0x1bcc/0x2340 dsaregisterswitch+0x1284/0x18d0 sja1105_probe+0x748/0x840 ...

References

Affected packages

Debian:12 / linux

Package

Name
linux
Purl
pkg:deb/debian/linux?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
6.1.4-1

Ecosystem specific

{
    "urgency": "not yet assigned"
}

Debian:13 / linux

Package

Name
linux
Purl
pkg:deb/debian/linux?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
6.1.4-1

Ecosystem specific

{
    "urgency": "not yet assigned"
}