Skip to main content
VulnerabilityPublished Updated

CVE-2026-43216: Linux kernel · net: Drop the lock in skb_may_tx_timestamp()

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in f3e4cceafad27c9363c33622732f86722846ec6f : patch Linux kernel soon.

Data as of 6 Nov 2026, 15:50 UTC

Severity
High

Rated High by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in f3e4cceafad27c9363c33622732f86722846ec6f, e4c6efb3b70ff87f1df99efce2f8893717695718, cf7599116c4c0082fd25cb1bf0254631da0ed06e +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ b245be1f4db1a0394e4b6eb66059814b46670ac3, < f3e4cceafad27c9363c33622732f86722846ec6f
Fixed in
  • f3e4cceafad27c9363c33622732f86722846ec6f
LinuxLinuxAffected
  • ≥ b245be1f4db1a0394e4b6eb66059814b46670ac3, < e4c6efb3b70ff87f1df99efce2f8893717695718
Fixed in
  • e4c6efb3b70ff87f1df99efce2f8893717695718
LinuxLinuxAffected
  • ≥ b245be1f4db1a0394e4b6eb66059814b46670ac3, < cf7599116c4c0082fd25cb1bf0254631da0ed06e
Fixed in
  • cf7599116c4c0082fd25cb1bf0254631da0ed06e
LinuxLinuxAffected
  • ≥ b245be1f4db1a0394e4b6eb66059814b46670ac3, < cd2463ec60f0d6e460078037c86f9d0947ee1ff6
Fixed in
  • cd2463ec60f0d6e460078037c86f9d0947ee1ff6
LinuxLinuxAffected
  • ≥ b245be1f4db1a0394e4b6eb66059814b46670ac3, < c770217044d9cbe16a1f7c385cf080ed06a2fc04
Fixed in
  • c770217044d9cbe16a1f7c385cf080ed06a2fc04
LinuxLinuxAffected
  • ≥ b245be1f4db1a0394e4b6eb66059814b46670ac3, < 983512f3a87fd8dc4c94dfa6b596b6e57df5aad7
Fixed in
  • 983512f3a87fd8dc4c94dfa6b596b6e57df5aad7

AI-suggested

A fix is available and has been applied in the Linux kernel source code as indicated by the listed fixed commit versions. Users and administrators should update to a kernel version that includes these fixes to prevent deadlocks caused by this issue.

Description

A deadlock vulnerability in the Linux kernel's skb_may_tx_timestamp() function was resolved by removing a lock that could be taken in an IRQ context, which is unsafe. The issue involved acquiring the sk_callback_lock in contexts where it should not be held, potentially causing deadlocks on the same CPU. The fix involves dropping the lock and using atomic pointer operations to safely access socket pointers without risking deadlocks.

References

Community reviews

Loading reviews…