Answer in brief
CVE-2023-52834 records a High severity (CVSS 7.5) vulnerability in atl1c: Work around the DMA RX overflow issue. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=43250ddd75a35d1f7926d989a10fefd30c37eaa7 <c29a89b23f67ee592f4dee61f9d7efbf86d60315 || >=43250ddd75a35d1f7926d989a10fefd30c37eaa7 <57e44ff9c2c9747b2b1a53556810b0e5192655d6 || >=43250ddd75a35d1f7926d989a10fefd30c37eaa7 <54a6152da4993ec8e4b53dc3cf577f5a2c829afa || >=43250ddd75a35d1f7926d989a10fefd30c37eaa7 <32f08b7b430ee01ec47d730f961a3306c1c7b6fb || >=43250ddd75a35d1f7926d989a10fefd30c37eaa7 <86565682e9053e5deb128193ea9e88531bbae9cf | c29a89b23f67ee592f4dee61f9d7efbf86d60315, 57e44ff9c2c9747b2b1a53556810b0e5192655d6, 54a6152da4993ec8e4b53dc3cf577f5a2c829afa, 32f08b7b430ee01ec47d730f961a3306c1c7b6fb, 86565682e9053e5deb128193ea9e88531bbae9cf |
| Linux/Linuxgeneric | 2.6.29 | Not reported |
Published upstream
May 21, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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.
Quoted source text, attributed separately from HOL analysis.