Answer in brief
CVE-2026-43216 records a Unknown severity vulnerability in net: Drop the lock in skb_may_tx_timestamp(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (generic), Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (generic), Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=b245be1f4db1a0394e4b6eb66059814b46670ac3 <4839cbda8f13e99ce2bb3b593f5cc3288415684b || >=b245be1f4db1a0394e4b6eb66059814b46670ac3 <3709d73ace37e9aaebb688f5a5cf706d74350b64 || >=b245be1f4db1a0394e4b6eb66059814b46670ac3 <cf7599116c4c0082fd25cb1bf0254631da0ed06e || >=b245be1f4db1a0394e4b6eb66059814b46670ac3 <cd2463ec60f0d6e460078037c86f9d0947ee1ff6 || >=b245be1f4db1a0394e4b6eb66059814b46670ac3 <c770217044d9cbe16a1f7c385cf080ed06a2fc04 || >=b245be1f4db1a0394e4b6eb66059814b46670ac3 <f3e4cceafad27c9363c33622732f86722846ec6f || >=b245be1f4db1a0394e4b6eb66059814b46670ac3 <e4c6efb3b70ff87f1df99efce2f8893717695718 || >=b245be1f4db1a0394e4b6eb66059814b46670ac3 <983512f3a87fd8dc4c94dfa6b596b6e57df5aad7 | 4839cbda8f13e99ce2bb3b593f5cc3288415684b, 3709d73ace37e9aaebb688f5a5cf706d74350b64, cf7599116c4c0082fd25cb1bf0254631da0ed06e, cd2463ec60f0d6e460078037c86f9d0947ee1ff6, c770217044d9cbe16a1f7c385cf080ed06a2fc04, f3e4cceafad27c9363c33622732f86722846ec6f, e4c6efb3b70ff87f1df99efce2f8893717695718, 983512f3a87fd8dc4c94dfa6b596b6e57df5aad7 |
| Linux/Linuxgeneric | 4.0 | Not reported |
| Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFPgeneric | >=V3.1.6 <* | * |
| Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFPgeneric | >=V3.1.6 <* | * |
| Siemens/SIPLUS S7-1500 CPU 1518-4 PN/DP MFPgeneric | >=V3.1.6 <* | * |
Published upstream
May 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 8, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 8, 2026
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.
Quoted source text, attributed separately from HOL analysis.