We use these services and cookies to improve your user experience. You may opt out if you wish, however, this may limit some features on this site.

Please see our statement on Data Privacy.

Crisp.chat (Helpdesk and Chat)

Ok

THREATINT
PUBLISHED

CVE-2020-36789

can: dev: can_get_echo_skb(): prevent call to kfree_skb() in hard IRQ context



Description

In the Linux kernel, the following vulnerability has been resolved: can: dev: can_get_echo_skb(): prevent call to kfree_skb() in hard IRQ context If a driver calls can_get_echo_skb() during a hardware IRQ (which is often, but not always, the case), the 'WARN_ON(in_irq)' in net/core/skbuff.c#skb_release_head_state() might be triggered, under network congestion circumstances, together with the potential risk of a NULL pointer dereference. The root cause of this issue is the call to kfree_skb() instead of dev_kfree_skb_irq() in net/core/dev.c#enqueue_to_backlog(). This patch prevents the skb to be freed within the call to netif_rx() by incrementing its reference count with skb_get(). The skb is finally freed by one of the in-irq-context safe functions: dev_consume_skb_any() or dev_kfree_skb_any(). The "any" version is used because some drivers might call can_get_echo_skb() in a normal context. The reason for this issue to occur is that initially, in the core network stack, loopback skb were not supposed to be received in hardware IRQ context. The CAN stack is an exeption. This bug was previously reported back in 2017 in [1] but the proposed patch never got accepted. While [1] directly modifies net/core/dev.c, we try to propose here a smoother modification local to CAN network stack (the assumption behind is that only CAN devices are affected by this issue). [1] http://lore.kernel.org/r/57a3ffb6-3309-3ad5-5a34-e93c3fe3614d@cetitec.com

Reserved 2024-02-26 | Published 2025-04-17 | Updated 2025-05-04 | Assigner Linux

Product status

Default status
unaffected

39549eef3587f1c1e8c65c88a2400d10fd30ea17 before 248b71ce92d4f3a574b2537f9838f48e892618f4
affected

39549eef3587f1c1e8c65c88a2400d10fd30ea17 before 451187b20431924d13fcfecc500d7cd2d9951bac
affected

39549eef3587f1c1e8c65c88a2400d10fd30ea17 before 3a922a85701939624484e7f2fd07d32beed00d25
affected

39549eef3587f1c1e8c65c88a2400d10fd30ea17 before 7e4cf2ec0ca236c3e5f904239cec6efe1f3baf22
affected

39549eef3587f1c1e8c65c88a2400d10fd30ea17 before ab46748bf98864f9c3f5559060bf8caf9df2b41e
affected

39549eef3587f1c1e8c65c88a2400d10fd30ea17 before 87530b557affe01c764de32dbeb58cdf47234574
affected

39549eef3587f1c1e8c65c88a2400d10fd30ea17 before 2283f79b22684d2812e5c76fc2280aae00390365
affected

Default status
affected

2.6.31
affected

Any version before 2.6.31
unaffected

4.4.244
unaffected

4.9.244
unaffected

4.14.207
unaffected

4.19.158
unaffected

5.4.78
unaffected

5.9.9
unaffected

5.10
unaffected

References

git.kernel.org/...c/248b71ce92d4f3a574b2537f9838f48e892618f4

git.kernel.org/...c/451187b20431924d13fcfecc500d7cd2d9951bac

git.kernel.org/...c/3a922a85701939624484e7f2fd07d32beed00d25

git.kernel.org/...c/7e4cf2ec0ca236c3e5f904239cec6efe1f3baf22

git.kernel.org/...c/ab46748bf98864f9c3f5559060bf8caf9df2b41e

git.kernel.org/...c/87530b557affe01c764de32dbeb58cdf47234574

git.kernel.org/...c/2283f79b22684d2812e5c76fc2280aae00390365

cve.org (CVE-2020-36789)

nvd.nist.gov (CVE-2020-36789)

Download JSON

Share this page
https://cve.threatint.eu/CVE/CVE-2020-36789

Support options

Helpdesk Chat, Email, Knowledgebase