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.
OS | Version | Architecture | Package | Version | Filename |
---|---|---|---|---|---|
ubuntu | 18.04 | noarch | linux | < any | UNKNOWN |
ubuntu | 20.04 | noarch | linux | < any | UNKNOWN |
ubuntu | 18.04 | noarch | linux-aws | < any | UNKNOWN |
ubuntu | 20.04 | noarch | linux-aws | < any | UNKNOWN |
ubuntu | 18.04 | noarch | linux-aws-5.4 | < any | UNKNOWN |
ubuntu | 16.04 | noarch | linux-aws-hwe | < any | UNKNOWN |
ubuntu | 20.04 | noarch | linux-azure | < any | UNKNOWN |
ubuntu | 14.04 | noarch | linux-azure | < any | UNKNOWN |
ubuntu | 16.04 | noarch | linux-azure | < any | UNKNOWN |
ubuntu | 18.04 | noarch | linux-azure-4.15 | < any | UNKNOWN |
git.kernel.org/linus/8b8e6e782456f1ce02a7ae914bbd5b1053f0b034 (5.16-rc6)
git.kernel.org/stable/c/595a684fa6f23b21958379a18cfa83862c73c2e1
git.kernel.org/stable/c/6e1011cd183faae8daff275c72444edcdfe0d473
git.kernel.org/stable/c/8b8e6e782456f1ce02a7ae914bbd5b1053f0b034
git.kernel.org/stable/c/8ed2f5d08d6e59f8c78b2869bfb95d0be32c094c
git.kernel.org/stable/c/c675256a7f131f5ba3f331efb715e8f31ea0e392
git.kernel.org/stable/c/de57f62f76450b934de8203711bdc4f7953c3421
git.kernel.org/stable/c/eb4687c7442942e115420a30185f8d83faf37696
git.kernel.org/stable/c/f3fde37d3f0d429f0fcce214cb52588a9e21260e
launchpad.net/bugs/cve/CVE-2021-47587
nvd.nist.gov/vuln/detail/CVE-2021-47587
security-tracker.debian.org/tracker/CVE-2021-47587
www.cve.org/CVERecord?id=CVE-2021-47587