CVE-2021-47587

net: systemport: Add global locking for descriptor lifecycle

State
Published
Severity
9.8 Critical
Published
Jun 19, 2024
Updated
Aug 5, 2026
Reserved
May 24, 2024

Read the record on cve.org

Description

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.

Scores

CVSSScoreVectorSource
3.19.8 CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HLinux

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • 80105befdb4b8cea924711b40b2462b87df65b62 to before 8ed2f5d08d6e59f8c78b2869bfb95d0be32c094cAffected
  • 80105befdb4b8cea924711b40b2462b87df65b62 to before de57f62f76450b934de8203711bdc4f7953c3421Affected
  • 80105befdb4b8cea924711b40b2462b87df65b62 to before f3fde37d3f0d429f0fcce214cb52588a9e21260eAffected
  • 80105befdb4b8cea924711b40b2462b87df65b62 to before 595a684fa6f23b21958379a18cfa83862c73c2e1Affected
  • 80105befdb4b8cea924711b40b2462b87df65b62 to before c675256a7f131f5ba3f331efb715e8f31ea0e392Affected
  • 80105befdb4b8cea924711b40b2462b87df65b62 to before 6e1011cd183faae8daff275c72444edcdfe0d473Affected
  • 80105befdb4b8cea924711b40b2462b87df65b62 to before eb4687c7442942e115420a30185f8d83faf37696Affected
  • 80105befdb4b8cea924711b40b2462b87df65b62 to before 8b8e6e782456f1ce02a7ae914bbd5b1053f0b034Affected
LinuxLinux
  • 3.16Affected
  • before 3.16Not affected
  • 4.4.296 through 4.4.*Not affected
  • 4.9.294 through 4.9.*Not affected
  • 4.14.259 through 4.14.*Not affected
  • 4.19.222 through 4.19.*Not affected
  • 5.4.168 through 5.4.*Not affected
  • 5.10.88 through 5.10.*Not affected
  • 5.15.11 through 5.15.*Not affected
  • 5.16 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.