Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2020-36789can: 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/[email protected]

Timeline

  1. ID reserved

    By Linux

  2. · 14 months later

    Published

  3. · 13 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2020-36789, by who scored it
Scored byCVSSScoreVector
CISA-ADPADP (enrichment)3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.19% · top 91% of all CVEs (20 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 39549eef3587f1c1e8c65c88a2400d10fd30ea17 – < 248b71ce92d4f3a574b2537f9838f48e892618f4
    • affected 39549eef3587f1c1e8c65c88a2400d10fd30ea17 – < 451187b20431924d13fcfecc500d7cd2d9951bac
    • affected 39549eef3587f1c1e8c65c88a2400d10fd30ea17 – < 3a922a85701939624484e7f2fd07d32beed00d25
    • affected 39549eef3587f1c1e8c65c88a2400d10fd30ea17 – < 7e4cf2ec0ca236c3e5f904239cec6efe1f3baf22
    • affected 39549eef3587f1c1e8c65c88a2400d10fd30ea17 – < ab46748bf98864f9c3f5559060bf8caf9df2b41e
    • affected 39549eef3587f1c1e8c65c88a2400d10fd30ea17 – < 87530b557affe01c764de32dbeb58cdf47234574
    • affected 39549eef3587f1c1e8c65c88a2400d10fd30ea17 – < 2283f79b22684d2812e5c76fc2280aae00390365
  • Linux · Linux

    • affected 2.6.31
    • unaffected < 2.6.31
    • unaffected 4.4.244 – ≤ 4.4.*
    • unaffected 4.9.244 – ≤ 4.9.*
    • unaffected 4.14.207 – ≤ 4.14.*
    • unaffected 4.19.158 – ≤ 4.19.*
    • unaffected 5.4.78 – ≤ 5.4.*
    • unaffected 5.9.9 – ≤ 5.9.*
    • unaffected 5.10 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2020-36789 badge
[![CVE-2020-36789](https://cveledger.app/badge/CVE-2020-36789.svg)](https://cveledger.app/cve/CVE-2020-36789)

Record last updated .