CVE-2023-52834
Medium
Elevated severity or exploit probability.
CVSS base
7.5
HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS — probability of exploitation (30 days)
0.6%
49.5th percentile
CISA KEV
Not listed
Weakness / dates
—
Published 2024-05-21 · modified 2026-08-04
CVSS breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
| Attack Vector | N | Network |
| Attack Complexity | L | Low |
| Privileges Required | N | None |
| User Interaction | N | None |
| Scope | U | Unchanged |
| Confidentiality | N | None |
| Integrity | N | None |
| Availability | H | High |
Timeline
- 2024-05-21 — Published (NVD)
- 2026-08-04 — Last modified (NVD)
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
References
- https://git.kernel.org/stable/c/32f08b7b430ee01ec47d730f961a3306c1c7b6fb
- https://git.kernel.org/stable/c/54a6152da4993ec8e4b53dc3cf577f5a2c829afa
- https://git.kernel.org/stable/c/57e44ff9c2c9747b2b1a53556810b0e5192655d6
- https://git.kernel.org/stable/c/86565682e9053e5deb128193ea9e88531bbae9cf
- https://git.kernel.org/stable/c/c29a89b23f67ee592f4dee61f9d7efbf86d60315
- https://git.kernel.org/stable/c/32f08b7b430ee01ec47d730f961a3306c1c7b6fb
- https://git.kernel.org/stable/c/54a6152da4993ec8e4b53dc3cf577f5a2c829afa
- https://git.kernel.org/stable/c/57e44ff9c2c9747b2b1a53556810b0e5192655d6
- https://git.kernel.org/stable/c/86565682e9053e5deb128193ea9e88531bbae9cf
- https://git.kernel.org/stable/c/c29a89b23f67ee592f4dee61f9d7efbf86d60315