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-2026-43216net: Drop the lock in skb_may_tx_timestamp()

Description

In the Linux kernel, the following vulnerability has been resolved: net: Drop the lock in skb_may_tx_timestamp() skb_may_tx_timestamp() may acquire sock::sk_callback_lock. The lock must not be taken in IRQ context, only softirq is okay. A few drivers receive the timestamp via a dedicated interrupt and complete the TX timestamp from that handler. This will lead to a deadlock if the lock is already write-locked on the same CPU. Taking the lock can be avoided. The socket (pointed by the skb) will remain valid until the skb is released. The ->sk_socket and ->file member will be set to NULL once the user closes the socket which may happen before the timestamp arrives. If we happen to observe the pointer while the socket is closing but before the pointer is set to NULL then we may use it because both pointer (and the file's cred member) are RCU freed. Drop the lock. Use READ_ONCE() to obtain the individual pointer. Add a matching WRITE_ONCE() where the pointer are cleared.

Timeline

  1. ID reserved

    By Linux

  2. · 5 days later

    Published

  3. · 6 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-2026-43216, by who scored it
Scored byCVSSScoreVector
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.14% · top 97% of all CVEs (19 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 b245be1f4db1a0394e4b6eb66059814b46670ac3 – < 4839cbda8f13e99ce2bb3b593f5cc3288415684b
    • affected b245be1f4db1a0394e4b6eb66059814b46670ac3 – < 3709d73ace37e9aaebb688f5a5cf706d74350b64
    • affected b245be1f4db1a0394e4b6eb66059814b46670ac3 – < cf7599116c4c0082fd25cb1bf0254631da0ed06e
    • affected b245be1f4db1a0394e4b6eb66059814b46670ac3 – < cd2463ec60f0d6e460078037c86f9d0947ee1ff6
    • affected b245be1f4db1a0394e4b6eb66059814b46670ac3 – < c770217044d9cbe16a1f7c385cf080ed06a2fc04
    • affected b245be1f4db1a0394e4b6eb66059814b46670ac3 – < f3e4cceafad27c9363c33622732f86722846ec6f
    • affected b245be1f4db1a0394e4b6eb66059814b46670ac3 – < e4c6efb3b70ff87f1df99efce2f8893717695718
    • affected b245be1f4db1a0394e4b6eb66059814b46670ac3 – < 983512f3a87fd8dc4c94dfa6b596b6e57df5aad7
  • Linux · Linux

    • affected 4.0
    • unaffected < 4.0
    • unaffected 5.10.261 – ≤ 5.10.*
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.95 – ≤ 6.12.*
    • unaffected 6.18.16 – ≤ 6.18.*
    • unaffected 6.19.6 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References10

Sources

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

Badge for a README or a ticket

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

Record last updated .