CVE-2021-47224
published 2024-05-21CVE-2021-47224: In the Linux kernel, the following vulnerability has been resolved: net: ll_temac: Make sure to free skb when it is completely used With the skb pointer…
PriorityP339high7.8CVSS 3.1
AVLACLPRLUINSUCHIHAH
EPSS
0.23%
14.3th percentile
In the Linux kernel, the following vulnerability has been resolved:
net: ll_temac: Make sure to free skb when it is completely used
With the skb pointer piggy-backed on the TX BD, we have a simple and
efficient way to free the skb buffer when the frame has been transmitted.
But in order to avoid freeing the skb while there are still fragments from
the skb in use, we need to piggy-back on the TX BD of the skb, not the
first.
Without this, we are doing use-after-free on the DMA side, when the first
BD of a multi TX BD packet is seen as completed in xmit_done, and the
remaining BDs are still being processed.
Affected
19 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.10.46-1 (bookworm) | linux 5.10.46-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 92744989533cbe85e8057935d230e128810168ce < 6d120ab4dc39a543c6b63361e1d0541c382900a3 | 6d120ab4dc39a543c6b63361e1d0541c382900a3 |
| linux | linux | >= 92744989533cbe85e8057935d230e128810168ce < 019ab7d044d0ebf97e1236bb8935b7809be92358 | 019ab7d044d0ebf97e1236bb8935b7809be92358 |
| linux | linux | >= 92744989533cbe85e8057935d230e128810168ce < e8afe05bd359ebe12a61dbdc94c06c00ea3e8d4b | e8afe05bd359ebe12a61dbdc94c06c00ea3e8d4b |
| linux | linux | >= 92744989533cbe85e8057935d230e128810168ce < 6aa32217a9a446275440ee8724b1ecaf1838df47 | 6aa32217a9a446275440ee8724b1ecaf1838df47 |
| linux | linux_kernel | < 5.4.128 | 5.4.128 |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 5.10.46-1 | 5.10.46-1 |
| linux | linux_kernel | >= 0 < 5.10.46-1 | 5.10.46-1 |
| linux | linux_kernel | >= 0 < 5.10.46-1 | 5.10.46-1 |
| linux | linux_kernel | >= 0 < 5.10.46-1 | 5.10.46-1 |
| linux | linux_kernel | >= 5.11 < 5.12.13 | 5.12.13 |
| linux | linux_kernel | >= 5.5 < 5.10.46 | 5.10.46 |
CVSS provenance
nvdv3.17.8HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
osv6.2MEDIUM
vendor_debian6.2MEDIUM
vendor_redhat6.2MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: net: ll_temac: Make sure to free skb when it is completely used
vendor_redhat·2024-05-21·CVSS 6.2
CVE-2021-47224 [MEDIUM] CWE-416 kernel: net: ll_temac: Make sure to free skb when it is completely used
kernel: net: ll_temac: Make sure to free skb when it is completely used
In the Linux kernel, the following vulnerability has been resolved:
net: ll_temac: Make sure to free skb when it is completely used
With the skb pointer piggy-backed on the TX BD, we have a simple and
efficient way to free the skb buffer when the frame has been transmitted.
But in order to avoid freeing the skb while there are still fragments from
the skb in use, we need to piggy-back on the TX BD of the skb, not the
first.
Without this, we are doing use-after-free on the DMA side, when the first
BD of a multi TX BD packet is seen as completed in xmit_done, and the
remaining BDs are still being processed.
A vulnerability was found in the Linux kernel's ll_temac driver, where the skb (socket buffer) may be improperly
Debian
CVE-2021-47224: linux - In the Linux kernel, the following vulnerability has been resolved: net: ll_tem...
vendor_debian·2021·CVSS 6.2
CVE-2021-47224 [MEDIUM] CVE-2021-47224: linux - In the Linux kernel, the following vulnerability has been resolved: net: ll_tem...
In the Linux kernel, the following vulnerability has been resolved: net: ll_temac: Make sure to free skb when it is completely used With the skb pointer piggy-backed on the TX BD, we have a simple and efficient way to free the skb buffer when the frame has been transmitted. But in order to avoid freeing the skb while there are still fragments from the skb in use, we need to piggy-back on the TX BD of the skb, not the first. Without this, we are doing use-after-free on the DMA side, when the first BD of a multi TX BD packet is seen as completed in xmit_done, and the remaining BDs are still being processed.
Scope: local
bookworm: resolved (fixed in 5.10.46-1)
bullseye: resolved (fixed in 5.10.46-1)
forky: resolved (fixed in 5.10.46-1)
sid: resolved (fixed in 5.10.46-1)
trixie: resolved (fixe
GHSA
GHSA-cqgv-cq5q-68pf: In the Linux kernel, the following vulnerability has been resolved:
net: ll_temac: Make sure to free skb when it is completely used
With the skb poi
ghsa_unreviewed·2024-05-21
CVE-2021-47224 [MEDIUM] CWE-416 GHSA-cqgv-cq5q-68pf: In the Linux kernel, the following vulnerability has been resolved:
net: ll_temac: Make sure to free skb when it is completely used
With the skb poi
In the Linux kernel, the following vulnerability has been resolved:
net: ll_temac: Make sure to free skb when it is completely used
With the skb pointer piggy-backed on the TX BD, we have a simple and
efficient way to free the skb buffer when the frame has been transmitted.
But in order to avoid freeing the skb while there are still fragments from
the skb in use, we need to piggy-back on the TX BD of the skb, not the
first.
Without this, we are doing use-after-free on the DMA side, when the first
BD of a multi TX BD packet is seen as completed in xmit_done, and the
remaining BDs are still being processed.
OSV
CVE-2021-47224: In the Linux kernel, the following vulnerability has been resolved: net: ll_temac: Make sure to free skb when it is completely used With the skb point
osv·2024-05-21·CVSS 6.2
CVE-2021-47224 [MEDIUM] CVE-2021-47224: In the Linux kernel, the following vulnerability has been resolved: net: ll_temac: Make sure to free skb when it is completely used With the skb point
In the Linux kernel, the following vulnerability has been resolved: net: ll_temac: Make sure to free skb when it is completely used With the skb pointer piggy-backed on the TX BD, we have a simple and efficient way to free the skb buffer when the frame has been transmitted. But in order to avoid freeing the skb while there are still fragments from the skb in use, we need to piggy-back on the TX BD of the skb, not the first. Without this, we are doing use-after-free on the DMA side, when the first BD of a multi TX BD packet is seen as completed in xmit_done, and the remaining BDs are still being processed.
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/019ab7d044d0ebf97e1236bb8935b7809be92358https://git.kernel.org/stable/c/6aa32217a9a446275440ee8724b1ecaf1838df47https://git.kernel.org/stable/c/6d120ab4dc39a543c6b63361e1d0541c382900a3https://git.kernel.org/stable/c/e8afe05bd359ebe12a61dbdc94c06c00ea3e8d4bhttps://git.kernel.org/stable/c/019ab7d044d0ebf97e1236bb8935b7809be92358https://git.kernel.org/stable/c/6aa32217a9a446275440ee8724b1ecaf1838df47https://git.kernel.org/stable/c/6d120ab4dc39a543c6b63361e1d0541c382900a3https://git.kernel.org/stable/c/e8afe05bd359ebe12a61dbdc94c06c00ea3e8d4b
2024-05-21
Published