CVE-2023-52843 json
llc: verify mac len before reading mac header
published 2024-05-21 2 y ago modified 2026-06-17 4 mo ago also EUVD-2023-59556
- cvss
- 5.5
- 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
Summary
In the Linux kernel, the following vulnerability has been resolved:
llc: verify mac len before reading mac header
LLC reads the mac header with eth_hdr without verifying that the skb has an Ethernet header.
Syzbot was able to enter llc_rcv on a tun device. Tun can insert packets without mac len and with user configurable skb->protocol (passing a tun_pi header when not configuring IFF_NO_PI).
BUG: KMSAN: uninit-value in llc_station_ac_send_test_r net/llc/llc_station.c:81 [inline] BUG: KMSAN: uninit-value in llc_station_rcv+0x6fb/0x1290 net/llc/llc_station.c:111 llc_station_ac_send_test_r net/llc/llc_station.c:81 [inline] llc_station_rcv+0x6fb/0x1290 net/llc/llc_station.c:111 llc_rcv+0xc5d/0x14a0 net/llc/llc_input.c:218 __netif_receive_skb_one_core net/core/dev.c:5523 [inline] __netif_receive_skb+0x1a6/0x5a0 net/core/dev.c:5637 netif_receive_skb_internal net/core/dev.c:5723 [inline] netif_receive_skb+0x58/0x660 net/core/dev.c:5782 tun_rx_batched+0x3ee/0x980 drivers/net/tun.c:1555 tun_get_user+0x54c5/0x69c0 drivers/net/tun.c:2002
Add a mac_len test before all three eth_hdr(skb) calls under net/llc.
There are further uses in include/net/llc_pdu.h. All these are protected by a test skb->protocol == ETH_P_802_2. Which does not protect against this tun scenario.
But the mac_len test added in this patch in llc_fixup_skb will indirectly protect those too. That is called from llc_rcv before any other LLC code.
It is tempting to just add a blanket mac_len check in llc_rcv, but not sure whether that could break valid LLC paths that do not assume an Ethernet header. 802.2 LLC may be used on top of non-802.3 protocols in principle. The below referenced commit shows that used to, on top of Token Ring.
At least one of the three eth_hdr uses goes back to before the start of git history. But the one that syzbot exercises is introduced in this commit. That commit is old enough (2008), that effectively all stable kernels should receive this.
Patch / fix
- Linux Linux 4.14.330, 4.19.299, 5.4.261, 5.10.201, 5.15.139, 6.1.63, 6.5.12, 6.6.2, 6.7
- linux Debian 12 6.1.64-1
- linux Debian 14, Debian 13 6.6.8-1
debian advisories DEBIAN-CVE-2023-52843
- linux Ubuntu 20.04 LTS 5.4.0-173.191
- linux Ubuntu 22.04 LTS 5.15.0-100.110
- linux-aws Ubuntu 20.04 LTS 5.4.0-1120.130
- linux-aws Ubuntu 22.04 LTS 5.15.0-1056.61
- linux-gcp Ubuntu 20.04 LTS 5.4.0-1124.133
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1053.61
- linux-gke Ubuntu 22.04 LTS 5.15.0-1052.57
- linux-ibm Ubuntu 20.04 LTS 5.4.0-1067.72
ubuntu advisories UBUNTU-CVE-2023-52843
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-rt Linux Micro 6.0 6.4.0-9.1
- kernel-source-rt Linux Micro 6.0 6.4.0-9.1
- kernel-source Linux Micro 6.0 6.4.0-18.1
- kernel-default Linux Micro 6.0 6.4.0-18.1
- kernel-kvmsmall Linux Micro 6.0 6.4.0-18.1
- kernel-default-base Linux Micro 6.0 6.4.0-17.1.1.51
- kernel-rt Real Time Module 15 SP6, openSUSE Leap 15.6 6.4.0-150600.10.5.1
- kernel-syms-rt Real Time Module 15 SP6, openSUSE Leap 15.6 6.4.0-150600.10.5.1
suse advisories SUSE-SU-2025:20028-1SUSE-SU-2025:20008-1SUSE-SU-2024:2973-1SUSE-SU-2024:2939-1SUSE-SU-2024:2896-1SUSE-SU-2024:2571-1
- git.kernel.org/stable/c/900a4418e3f66a32db6baaf23f92b99c20ae6535 commit
- git.kernel.org/stable/c/9a3f9054a5227d7567cba1fb821df48ccecad10c commit
- git.kernel.org/stable/c/cbdcdf42d15dac74c7287679fb2a9d955f8feb1f commit
- git.kernel.org/stable/c/3a2653828ffc6101aef80bf58d5b77484239f779 commit
- git.kernel.org/stable/c/352887b3edd007cf9b0abc30fe9d98622acd859b commit
- git.kernel.org/stable/c/f980e9a57dfb9530f1f4ee41a2420f2a256d7b29 commit
- git.kernel.org/stable/c/0a720d0259ad3521ec6c9e4199f9f6fc75bac77a commit
- git.kernel.org/stable/c/ff5cb6a4f0c6d7fbdc84858323fb4b7af32cfd79 commit
- git.kernel.org/stable/c/7b3ba18703a63f6fd487183b9262b08e5632da1b commit
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-2023-52843 updated cvss 5.5
kernel: llc: verify mac len before reading mac header
-
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 morenot 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 ICSA-25-226-15 updated
Siemens SINEC OS
-
Siemens RUGGEDCOM RST2428P (6GK6242-6PA00) Siemens SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family Siemens SCALANCE XCM-/XRM-/XCH-/XRH-300 familynot affected
Facts from CISA's republication of the vendor's own advisory (CSAF); the linked advisory is the authoritative source. CISA notification · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
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 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-908 Use of Uninitialized Resource
- Technology feeds
References
-
git.kernel.org
/stable/c/900a4418e3f66a32db6baaf23f92b99c20ae6535
patch
-
git.kernel.org
/stable/c/9a3f9054a5227d7567cba1fb821df48ccecad10c
patch
-
git.kernel.org
/stable/c/cbdcdf42d15dac74c7287679fb2a9d955f8feb1f
patch
-
git.kernel.org
/stable/c/3a2653828ffc6101aef80bf58d5b77484239f779
patch
-
git.kernel.org
/stable/c/352887b3edd007cf9b0abc30fe9d98622acd859b
patch
-
git.kernel.org
/stable/c/f980e9a57dfb9530f1f4ee41a2420f2a256d7b29
patch
-
git.kernel.org
/stable/c/0a720d0259ad3521ec6c9e4199f9f6fc75bac77a
patch
-
git.kernel.org
/stable/c/ff5cb6a4f0c6d7fbdc84858323fb4b7af32cfd79
patch
-
git.kernel.org
/stable/c/7b3ba18703a63f6fd487183b9262b08e5632da1b
patch
Sources
- CVE List CVE-2023-52843
- NVD CVE-2023-52843
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.