net: systemport: Add global locking for descriptor lifecycle
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in Kernel 595a684fa6f23b21958379a18cfa83862c73c2e1, Kernel 6e1011cd183faae8daff275c72444edcdfe0d473, Kernel 8b8e6e782456f1ce02a7ae914bbd5b1053f0b034 and 5 more.
In the Linux kernel, the following vulnerability has been resolved: net: systemport: Add global locking for descriptor lifecycle The descriptor list is a shared resource across all of the transmit queues, and the locking mechanism used today only protects concurrency across a given transmit queue between the transmit and reclaiming. This creates an opportunity for the SYSTEMPORT hardware to work on corrupted descriptors if we have multiple producers at once which is the case when using multiple transmit queues. This was particularly noticeable when using multiple flows/transmit queues and it showed up in interesting ways in that UDP packets would get a correct UDP header checksum being calculated over an incorrect packet length. Similarly TCP packets would get an equally correct checksum computed by the hardware over an incorrect packet length. The SYSTEMPORT hardware maintains an internal descriptor list that it re-arranges when the driver produces a new descriptor anytime it writes to the WRITE_PORT_{HI,LO} registers, there is however some delay in the hardware to re-organize its descriptors and it is possible that concurrent TX queues eventually break this internal allocation scheme to the point where the length/status part of the descriptor gets used for an incorrect data buffer. The fix is to impose a global serialization for all TX queues in the short section where we are writing to the WRITE_PORT_{HI,LO} registers which solves the corruption even with multiple concurrent TX queues being used.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =3.16, >=80105befdb4b8cea924711b40b2462b87df65b62 <595a684fa6f23b21958379a18cfa83862c73c2e1, >=80105befdb4b8cea924711b40b2462b87df65b62 <6e1011cd183faae8daff275c72444edcdfe0d473, >=80105befdb4b8cea924711b40b2462b87df65b62 <8b8e6e782456f1ce02a7ae914bbd5b1053f0b034, >=80105befdb4b8cea924711b40b2462b87df65b62 <8ed2f5d08d6e59f8c78b2869bfb95d0be32c094c, >=80105befdb4b8cea924711b40b2462b87df65b62 <c675256a7f131f5ba3f331efb715e8f31ea0e392, >=80105befdb4b8cea924711b40b2462b87df65b62 <de57f62f76450b934de8203711bdc4f7953c3421, >=80105befdb4b8cea924711b40b2462b87df65b62 <eb4687c7442942e115420a30185f8d83faf37696, >=80105befdb4b8cea924711b40b2462b87df65b62 <f3fde37d3f0d429f0fcce214cb52588a9e21260e | 595a684fa6f23b21958379a18cfa83862c73c2e1, 6e1011cd183faae8daff275c72444edcdfe0d473, 8b8e6e782456f1ce02a7ae914bbd5b1053f0b034, 8ed2f5d08d6e59f8c78b2869bfb95d0be32c094c, c675256a7f131f5ba3f331efb715e8f31ea0e392, de57f62f76450b934de8203711bdc4f7953c3421, eb4687c7442942e115420a30185f8d83faf37696, f3fde37d3f0d429f0fcce214cb52588a9e21260e |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket