CVE-2020-36789

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
Configurations

Configuration 1 (hide)

OR cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:5.10:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:5.10:rc2:*:*:*:*:*:*

History

29 Apr 2025, 18:55

Type Values Removed Values Added
Summary
  • (es) En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: can: dev: can_get_echo_skb(): evitar la llamada a kfree_skb() en el contexto de IRQ duro Si un controlador llama a can_get_echo_skb() durante un IRQ de hardware (que es a menudo, pero no siempre, el caso), el 'WARN_ON(in_irq)' en net/core/skbuff.c#skb_release_head_state() podría activarse, en circunstancias de congestión de la red, junto con el riesgo potencial de una desreferencia de puntero NULL. La causa raíz de este problema es la llamada a kfree_skb() en lugar de dev_kfree_skb_irq() en net/core/dev.c#enqueue_to_backlog(). Este parche evita que el skb se libere dentro de la llamada a netif_rx() incrementando su contador de referencias con skb_get(). El skb se libera finalmente mediante una de las funciones seguras en contexto IRQ: dev_consume_skb_any() o dev_kfree_skb_any(). Se utiliza la versión "any" porque algunos controladores podrían llamar a can_get_echo_skb() en un contexto normal. Este problema se debe a que, inicialmente, en la pila de red principal, no se esperaba que los skb de bucle invertido se recibieran en el contexto IRQ de hardware. La pila CAN es una excepción. Este error se reportó previamente en 2017 en [1], pero el parche propuesto nunca fue aceptado. Si bien [1] modifica directamente net/core/dev.c, aquí intentamos proponer una modificación más fluida local en la pila de red CAN (suponiendo que solo los dispositivos CAN se ven afectados por este problema). [1] http://lore.kernel.org/r/57a3ffb6-3309-3ad5-5a34-e93c3fe3614d@cetitec.com
CVSS v2 : unknown
v3 : unknown
v2 : unknown
v3 : 5.5
First Time Linux linux Kernel
Linux
CWE CWE-476
CPE cpe:2.3:o:linux:linux_kernel:5.10:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:5.10:rc2:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
References () https://git.kernel.org/stable/c/2283f79b22684d2812e5c76fc2280aae00390365 - () https://git.kernel.org/stable/c/2283f79b22684d2812e5c76fc2280aae00390365 - Patch
References () https://git.kernel.org/stable/c/248b71ce92d4f3a574b2537f9838f48e892618f4 - () https://git.kernel.org/stable/c/248b71ce92d4f3a574b2537f9838f48e892618f4 - Patch
References () https://git.kernel.org/stable/c/3a922a85701939624484e7f2fd07d32beed00d25 - () https://git.kernel.org/stable/c/3a922a85701939624484e7f2fd07d32beed00d25 - Patch
References () https://git.kernel.org/stable/c/451187b20431924d13fcfecc500d7cd2d9951bac - () https://git.kernel.org/stable/c/451187b20431924d13fcfecc500d7cd2d9951bac - Patch
References () https://git.kernel.org/stable/c/7e4cf2ec0ca236c3e5f904239cec6efe1f3baf22 - () https://git.kernel.org/stable/c/7e4cf2ec0ca236c3e5f904239cec6efe1f3baf22 - Patch
References () https://git.kernel.org/stable/c/87530b557affe01c764de32dbeb58cdf47234574 - () https://git.kernel.org/stable/c/87530b557affe01c764de32dbeb58cdf47234574 - Patch
References () https://git.kernel.org/stable/c/ab46748bf98864f9c3f5559060bf8caf9df2b41e - () https://git.kernel.org/stable/c/ab46748bf98864f9c3f5559060bf8caf9df2b41e - Patch

17 Apr 2025, 18:15

Type Values Removed Values Added
New CVE

Information

Published : 2025-04-17 18:15

Updated : 2025-04-29 18:55


NVD link : CVE-2020-36789

Mitre link : CVE-2020-36789

CVE.ORG link : CVE-2020-36789


JSON object : View

Products Affected

linux

  • linux_kernel
CWE
CWE-476

NULL Pointer Dereference