atl1c: Work around the DMA RX overflow issue
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in Kernel 32f08b7b430ee01ec47d730f961a3306c1c7b6fb, Kernel 54a6152da4993ec8e4b53dc3cf577f5a2c829afa, Kernel 57e44ff9c2c9747b2b1a53556810b0e5192655d6 and 2 more.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =2.6.29, >=43250ddd75a35d1f7926d989a10fefd30c37eaa7 <32f08b7b430ee01ec47d730f961a3306c1c7b6fb, >=43250ddd75a35d1f7926d989a10fefd30c37eaa7 <54a6152da4993ec8e4b53dc3cf577f5a2c829afa, >=43250ddd75a35d1f7926d989a10fefd30c37eaa7 <57e44ff9c2c9747b2b1a53556810b0e5192655d6, >=43250ddd75a35d1f7926d989a10fefd30c37eaa7 <86565682e9053e5deb128193ea9e88531bbae9cf, >=43250ddd75a35d1f7926d989a10fefd30c37eaa7 <c29a89b23f67ee592f4dee61f9d7efbf86d60315 | 32f08b7b430ee01ec47d730f961a3306c1c7b6fb, 54a6152da4993ec8e4b53dc3cf577f5a2c829afa, 57e44ff9c2c9747b2b1a53556810b0e5192655d6, 86565682e9053e5deb128193ea9e88531bbae9cf, c29a89b23f67ee592f4dee61f9d7efbf86d60315 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket