Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

MediumCVSS 5.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.13% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 3709d73ace37e9aaebb688f5a5cf706d74350b64, 4839cbda8f13e99ce2bb3b593f5cc3288415684b, 983512f3a87fd8dc4c94dfa6b596b6e57df5aad7; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 3709d73ace37e9aaebb688f5a5cf706d74350b64, 4839cbda8f13e99ce2bb3b593f5cc3288415684b, 983512f3a87fd8dc4c94dfa6b596b6e57df5aad7; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
May 6, 2026
Updated
Nov 11, 2026
EPSS
0.1% · 3th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-43216

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.0affected
    • b245be1f4db1a0394e4b6eb66059814b46670ac3 and later · before 4839cbda8f13e99ce2bb3b593f5cc3288415684baffected · git
    • b245be1f4db1a0394e4b6eb66059814b46670ac3 and later · before 3709d73ace37e9aaebb688f5a5cf706d74350b64affected · git
    • b245be1f4db1a0394e4b6eb66059814b46670ac3 and later · before cf7599116c4c0082fd25cb1bf0254631da0ed06eaffected · git
    • b245be1f4db1a0394e4b6eb66059814b46670ac3 and later · before cd2463ec60f0d6e460078037c86f9d0947ee1ff6affected · git
    • b245be1f4db1a0394e4b6eb66059814b46670ac3 and later · before c770217044d9cbe16a1f7c385cf080ed06a2fc04affected · git
    • b245be1f4db1a0394e4b6eb66059814b46670ac3 and later · before f3e4cceafad27c9363c33622732f86722846ec6faffected · git
    • b245be1f4db1a0394e4b6eb66059814b46670ac3 and later · before e4c6efb3b70ff87f1df99efce2f8893717695718affected · git
    • b245be1f4db1a0394e4b6eb66059814b46670ac3 and later · before 983512f3a87fd8dc4c94dfa6b596b6e57df5aad7affected · git
    • before 4.0not affected · semver

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel4.0 and later · before 6.18.16
  • linux linux kernel6.19 and later · before 6.19.6
  • linux linux kernel7.0

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.180-16.1.180-1
Debian:13linuxbefore 6.12.95-16.12.95-1
Debian:14linuxbefore 6.19.6-16.19.6-1

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-43214May 6, 2026 · KVM: x86: Add SRCU protection for reading PDPTRs in __get_sregs2()
    31Monitor
  • ← EarlierCVE-2026-43215May 6, 2026 · cifs: Fix locking usage for tcon fields
    35Monitor
  • Later →CVE-2026-43217May 6, 2026 · media: iris: gen2: Add sanity check for session stop
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux3709d73ace37e9aaebb688f5a5cf706d74350b64Vendor (CNA)
Linux Linux4839cbda8f13e99ce2bb3b593f5cc3288415684bVendor (CNA)
Linux Linux983512f3a87fd8dc4c94dfa6b596b6e57df5aad7Vendor (CNA)
Linux Linuxc770217044d9cbe16a1f7c385cf080ed06a2fc04Vendor (CNA)
Linux Linuxcd2463ec60f0d6e460078037c86f9d0947ee1ff6Vendor (CNA)
Linux Linuxcf7599116c4c0082fd25cb1bf0254631da0ed06eVendor (CNA)
Linux Linuxe4c6efb3b70ff87f1df99efce2f8893717695718Vendor (CNA)
Linux Linuxf3e4cceafad27c9363c33622732f86722846ec6fVendor (CNA)
azl3 kernel 6.6.150.1-1 on Azure Linux 3.0—Microsoft (MSRC)
azl3 kernel 6.6.152.1-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
azl3 kernel 6.6.157.1-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
debian:linux6.1.180-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

All records