CVE-2023-52768

wifi: wilc1000: use vmm_table as array in wilc struct

HIGH
7.8
CVSS Score
Published: May 21, 2024 at 03:30 PM UTC
Updated: August 5, 2026 at 10:24 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: wifi: wilc1000: use vmm_table as array in wilc struct Enabling KASAN and running some iperf tests raises some memory issues with vmm_table: BUG: KASAN: slab-out-of-bounds in wilc_wlan_handle_txq+0x6ac/0xdb4 Write of size 4 at addr c3a61540 by task wlan0-tx/95 KASAN detects that we are writing data beyond range allocated to vmm_table. There is indeed a mismatch between the size passed to allocator in wilc_wlan_init, and the range of possible indexes used later: allocation size is missing a multiplication by sizeof(u32)

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 5.19.95.15.68 ≤ v < 5.15.1405.19.9 ≤ v < 5.205.19.9 ≤ v < 6.1.646.0 ≤ v < 6.1.646.0 ≤ v < 6.5.136.0 ≤ v < 6.6.36.0 ≤ v < 6.76.2 ≤ v < 6.5.136.6 ≤ v < 6.6.332dd0b22a5ba1dd296ccf2caf46ad44c3a8d5d9840b717bfcefab28a0656b8caa5e43d5449e5a6715.15.685.19.95212d958f6518003cd98c9886f8e8aedcfc257416.0
Vendor states this is fixed in 05ac1a198a63ad66bf5ae8b7321407c102d40ef3 (fixed)
Vendor states this is fixed in 3ce1c2c3999b232258f7aabab311d47dda75605c (fixed)
Vendor states this is fixed in 4b0d6ddb6466d10df878a7787f175a0e4adc3e27 (fixed)
Vendor states this is fixed in 541b3757fd443a68ed8d25968eae511a8275e7c8 (fixed)
Vendor states this is fixed in 6aaf7cd8bdfe245d3c9a8b48fe70c2011965948e (fixed)
Vendor states this is fixed in 5.15.140 (unaffected)
Affected range stops below 5.20, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.0 (unaffected)
Vendor states this is fixed in 6.1.64 (unaffected)
Vendor states this is fixed in 6.5.13 (unaffected)
Vendor states this is fixed in 6.6.3 (unaffected)
Vendor states this is fixed in 6.7 (unaffected)

References (5)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/05ac1a198a63ad66bf5ae8b7321407c102d40ef3
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/3ce1c2c3999b232258f7aabab311d47dda75605c
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/4b0d6ddb6466d10df878a7787f175a0e4adc3e27
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/541b3757fd443a68ed8d25968eae511a8275e7c8
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/6aaf7cd8bdfe245d3c9a8b48fe70c2011965948e

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-129

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card