LiveActive security incident?Get immediate response
CVE Record

CVE-2023-52834: atl1c: Work around the DMA RX overflow issue

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This CVE covers a Linux kernel network driver defect in atl1c, used by some Atheros/Attansic Ethernet adapters. The issue involves receive-side DMA overflow behavior. The public record provides no CVSS score, no confirmed exploitation, and no detailed business impact beyond the kernel driver fix.

Executive priority

Handle through normal kernel patch management, with higher priority for physical or embedded Linux assets using affected Ethernet adapters. There is not enough sourced evidence to justify emergency treatment, but kernel driver defects should not be left indefinitely unpatched.

Technical view

The fix changes atl1c receive buffer handling by checking allocated skb addresses and reserving offset space to avoid problematic 0x...fc0 addresses. It mirrors an earlier alx driver workaround and was tested on AR8131 hardware. Affected exposure depends on kernel version, downstream backports, and whether atl1c-supported hardware is present.

Likely exposure

Most exposure is likely on Linux systems using atl1c-supported Ethernet hardware, such as AR8131-class adapters. Cloud workloads and systems without this driver or hardware are less likely exposed. Downstream distro kernels may already carry the stable fixes.

Exploitation context

The provided sources do not state active exploitation, public exploit availability, or a weaponized attack path. CISA KEV status is false in the bundle. Treat this as a kernel maintenance and fleet hygiene issue unless vendor guidance says otherwise.

Researcher notes

The record is sparse: no CVSS, CWE, exploit discussion, or detailed impact statement. Analysis should focus on code provenance, stable branch inclusion, downstream backports, and whether atl1c hardware is actually reachable in the assessed environment.

Mitigation direction

  • Update to a vendor kernel containing the listed stable atl1c fixes.
  • Check distribution advisories for backported fixes before relying on upstream version numbers.
  • Prioritize systems with atl1c-supported Ethernet hardware.
  • Avoid direct wrangler-style assumptions; follow vendor kernel packaging guidance.
  • Schedule reboot or live-patching according to normal kernel update policy.

Validation and detection

  • Inventory systems with the atl1c kernel module or matching Ethernet hardware.
  • Map running kernel builds to vendor advisories and upstream stable commits.
  • Confirm updated systems boot the fixed kernel after patching.
  • Review kernel logs for atl1c receive or DMA error patterns.
  • Document any unsupported legacy systems needing compensating controls.
Prepared
Confidence
medium
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-52834 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux43250ddd75a35d1f7926d989a10fefd30c37eaa7, 43250ddd75a35d1f7926d989a10fefd30c37eaa7, 43250ddd75a35d1f7926d989a10fefd30c37eaa7, 43250ddd75a35d1f7926d989a10fefd30c37eaa7, 43250ddd75a35d1f7926d989a10fefd30c37eaa7unaffected
LinuxLinux2.6.29, 0, 5.15.140, 6.1.64, 6.5.13, 6.6.3, 6.7affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.