CVE-2023-52834

atl1c: Work around the DMA RX overflow issue

MEDIUM
5.5
CVSS Score
Published: May 21, 2024 at 03:31 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
MEDIUM5.5
Exploit prediction
EPSS 0.7%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: atl1c: Work around the DMA RX overflow issue This is based on alx driver commit 881d0327db37 ("net: alx: Work around the DMA RX overflow issue"). The alx and atl1c drivers had RX overflow error which was why a custom allocator was created to avoid certain addresses. The simpler workaround then created for alx driver, but not for atl1c due to lack of tester. Instead of using a custom allocator, check the allocated skb address and use skb_reserve() to move away from problematic 0x...fc0 address. Tested on AR8131 on Acer 4540.

Affected

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

v < 5.15.1402.6.29 ≤ v < 5.15.1402.6.29 ≤ v < 6.1.642.6.29 ≤ v < 6.5.132.6.29 ≤ v < 6.6.32.6.29 ≤ v < 6.75.16 ≤ v < 6.1.646.2 ≤ v < 6.5.136.6 ≤ v < 6.6.32.6.2943250ddd75a35d1f7926d989a10fefd30c37eaa7
Vendor states this is fixed in 32f08b7b430ee01ec47d730f961a3306c1c7b6fb (fixed)
Vendor states this is fixed in 54a6152da4993ec8e4b53dc3cf577f5a2c829afa (fixed)
Vendor states this is fixed in 57e44ff9c2c9747b2b1a53556810b0e5192655d6 (fixed)
Vendor states this is fixed in 86565682e9053e5deb128193ea9e88531bbae9cf (fixed)
Vendor states this is fixed in c29a89b23f67ee592f4dee61f9d7efbf86d60315 (fixed)
Vendor states this is fixed in 2.6.29 (unaffected)
Vendor states this is fixed in 5.15.140 (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/32f08b7b430ee01ec47d730f961a3306c1c7b6fb
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/54a6152da4993ec8e4b53dc3cf577f5a2c829afa
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/57e44ff9c2c9747b2b1a53556810b0e5192655d6
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/86565682e9053e5deb128193ea9e88531bbae9cf
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/c29a89b23f67ee592f4dee61f9d7efbf86d60315

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

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

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfo

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