Skip to navigation

Threat reportVulnerabilityTL-2026-2570

CVE-2025-39682 — Linux Kernel net/tls rx_list Zero-Length Record Use-After-Free Added to CISA KEV Catalog

criticalACTIVE

CISA added CVE-2025-39682, a use-after-free in the Linux kernel's net/tls receive path (tls_sw_recvmsg) triggered by a zero-length TLS record pulled from rx_list, to its Known Exploited Vulnerabilities catalog on 2026-09-18 based on evidence of active exploitation, with a 2026-09-21 federal remediation deadline. First disclosed .

Key facts

IdentifiersTL-2026-2570, CVE-2025-39682
SeverityCRITICAL
CVSS9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)
First disclosed
Exploitation statusLinked CVE exploited in the wild; Listed in CISA KEV: CVE-2025-39682 (added )
EPSSCVE-2025-39682: 2.8% (86.4th percentile)
Affected productsLinux Linux Kernel; Debian linux-6.1 (Debian 11 bullseye); Canonical linux (Ubuntu, multiple kernel flavors incl. AWS); Red Hat Red Hat Enterprise Linux 9 / 10 kernel; Google Android (Kernel TLS component); Siemens SIMATIC CN 4100
Weaknesses (CWE)CWE-754, CWE-416, CWE-20
ToolsGoogle kernelCTF mitigation-v4-6.6 instance
MITRE ATT&CK techniquesT0814 Denial of Service, T1190 Exploit Public-Facing Application, T1404 Exploitation for Privilege Escalation, T1499.004 Endpoint Denial of Service: Application or System Exploitation, T1546 Event Triggered Execution
MotivationUNKNOWN
Target sectorsgovernment administration, technology, cloud, industrial, criticalinfrastructure, mobile
Target regionsGlobal
Detection rules9 (1 shown free)
Sources15 cited sources

Detection coverage

As of 2026-09-18, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-2570 across Splunk SPL, Microsoft KQL and Sigma, covering 19 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.

Free detection: Linux Kernel net/tls KASAN UAF Signature — CVE-2025-39682 Exploitation Trigger

Detects kernel-log evidence that the CVE-2025-39682 use-after-free in tls_sw_recvmsg()/tls_sw_release_resources_rx() has been triggered: KASAN slab-use-after-free reports, kfree_skb_list_reason UAF crash signatures, or repeated kernel oops mentioning the net/tls receive path. This is the exploit's initial trigger step (crafted Application Data / zero-length Handshake / Application Data TLS 1.2 record sequence over a kTLS zero-copy socket, per STAR Labs' PoC) manifesting in kernel logging before privilege escalation proceeds.

  • Languages: Splunk SPL, Microsoft KQL, Sigma
  • ATT&CK: T1190, T1210, T1068
  • Data sources: linux_kern_log, journald, syslog, linux_secure
  • Severity: critical
  • Confidence: high

Splunk SPL

index=linux (sourcetype="syslog" OR sourcetype="journald" OR sourcetype="linux_secure" OR sourcetype="kern_log")
("BUG: KASAN: slab-use-after-free" OR "kfree_skb_list_reason" OR "tls_sw_release_resources_rx" OR ("tls_sw_recvmsg" AND ("Call Trace" OR "general protection fault" OR "Oops")))
| rex field=_raw "Linux version (?<kernel_version>\d+\.\d+\.\d+)"
| eval cve="CVE-2025-39682"
| stats count min(_time) as first_seen max(_time) as last_seen values(kernel_version) as kernel_version by host
| where count > 0
| eval first_seen=strftime(first_seen,"%Y-%m-%d %H:%M:%S"), last_seen=strftime(last_seen,"%Y-%m-%d %H:%M:%S")
| eval risk_note="Potential CVE-2025-39682 (Linux net/tls rx_list zero-length-record UAF) trigger observed — KASAN/kfree_skb_list_reason/tls_sw_release_resources_rx signature in kernel log"
| table host cve count first_seen last_seen kernel_version risk_note

Microsoft KQL

let TargetStrings = dynamic(["BUG: KASAN: slab-use-after-free","kfree_skb_list_reason","tls_sw_release_resources_rx","tls_sw_recvmsg"]);
Syslog
| where TimeGenerated > ago(24h)
| where Facility == "kern" or SyslogMessage has_any (TargetStrings)
| where SyslogMessage has_any (TargetStrings)
| extend Indicator = case(
    SyslogMessage has "slab-use-after-free", "kasan_uaf",
    SyslogMessage has "kfree_skb_list_reason", "kfree_skb_uaf",
    SyslogMessage has "tls_sw_release_resources_rx", "tls_release_uaf",
    "tls_recvmsg_anomaly")
| project TimeGenerated, Computer, ProcessName, SyslogMessage, Indicator
| summarize Count = count(), FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated) by Computer, Indicator
| where Count > 0
| order by LastSeen desc

Sigma

title: Linux Kernel net/tls KASAN Use-After-Free Signature (CVE-2025-39682)
id: 7a1c9e2e-2f3a-4b6a-9d1c-4e8f0a5b6c71
status: experimental
description: Detects KASAN slab-use-after-free and related crash signatures in tls_sw_recvmsg/tls_sw_release_resources_rx indicating exploitation of the Linux kernel net/tls rx_list zero-length-record UAF (CVE-2025-39682), added to the CISA KEV catalog on 2026-09-18.
references:
    - https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-39682
    - https://starlabs.sg/advisories/25/25-39682/
    - https://nvd.nist.gov/vuln/detail/CVE-2025-39682
author: Threadlinqs Team
date: 2026-09-18
tags:
    - attack.privilege-escalation
    - attack.t1068
    - attack.initial-access
    - attack.t1190
    - cve.2025.39682
    - cwe.416
    - cwe.754
logsource:
    product: linux
    category: kernel
detection:
    selection_kasan:
        Message|contains:
            - 'BUG: KASAN: slab-use-after-free'
            - 'kfree_skb_list_reason'
            - 'tls_sw_release_resources_rx'
    selection_recvmsg:
        Message|contains: 'tls_sw_recvmsg'
        Message|contains|any:
            - 'Call Trace'
            - 'general protection fault'
            - 'Oops'
    condition: selection_kasan or selection_recvmsg
falsepositives:
    - Kernel fuzz-testing (syzkaller, KASAN-enabled CI) intentionally triggering unrelated UAF classes
    - Debug kernel builds with verbose net/tls tracing enabled for unrelated diagnostics
level: critical

Known false positives:

  • KASAN-enabled kernel fuzz-testing (syzkaller) or CI environments intentionally exercising net/tls code paths
  • Debug kernels with verbose net/tls tracing enabled for unrelated development diagnostics

Tuning notes: Suppress hosts confirmed on kernel_version >= 6.1.149/6.6.103/6.12.44/6.16.4/6.17-rc3 (patched); scope to hosts still on vulnerable kernel ranges (6.0–6.1.148, 6.2–6.6.102, 6.7–6.12.43, 6.13–6.16.3, 6.17-rc1/rc2) to cut noise from unrelated KASAN findings on hardened/fuzzing hosts.

8 more detection rules (Splunk SPL, Microsoft KQL, Sigma) · unlock with TL Creds. Sign up free to unlock the detection rules or query them with the Threadlinqs MCP server (Purple)
  • Linux Kernel net/tls KASAN UAF Signature — CVE-2025-39682 Exploitation Trigger · unlock with TL Creds
  • core_pattern Sysctl Overwrite + Pipe/Splice Heap-Spray — CVE-2025-39682 Post-Exploitation · unlock with TL Creds
  • Root Process Spawned via Hijacked core_pattern Crash Handler / Fleet-Wide kTLS Crash-Loop — CVE-2025-39682 Impact · unlock with TL Creds
  • Linux Kernel net/tls KASAN UAF Signature — CVE-2025-39682 Exploitation Trigger · unlock with TL Creds
  • core_pattern Sysctl Overwrite + Pipe/Splice Heap-Spray — CVE-2025-39682 Post-Exploitation · unlock with TL Creds
  • Root Process Spawned via Hijacked core_pattern Crash Handler / Fleet-Wide kTLS Crash-Loop — CVE-2025-39682 Impact · unlock with TL Creds
  • core_pattern Sysctl Overwrite + Pipe/Splice Heap-Spray — CVE-2025-39682 Post-Exploitation · unlock with TL Creds
  • Root Process Spawned via Hijacked core_pattern Crash Handler / Fleet-Wide kTLS Crash-Loop — CVE-2025-39682 Impact · unlock with TL Creds

Indicators of compromise

As of 2026-09-18, Threadlinqs Intelligence tracks 19 indicators of compromise for TL-2026-2570.

Sample indicators (3 of 19)

  • File hash: 2902c3ebcca52ca845c03182000e8d71d3a5196f
  • File hash: c09dd3773b5950e9cfb6c9b9a5f6e36d06c62677
  • File hash: 3439c15ae91a517cf3c650ea15a8987699416ad9

Defanged, TLP:CLEAR. Full set of 19 indicators: unlock with TL Creds.

19 indicators of compromise · unlock with TL Creds. Compare plans

Technical analysis

A public, reliable (~79%) root-privilege-escalation exploit chain — heap-spray, cross-cache attack, and a core_pattern kernel-crash-handler hijack — is available on GitHub, and the flaw also affects Android devices via ASB-A-440544511.

CVE-2025-39682 is a flaw in the Linux kernel's net/tls subsystem, in the function tls_sw_recvmsg(), that mishandles a corner case where a zero-length TLS record is retrieved from the kernel's internal rx_list. Because TLS 1.3 record types are only known after decryption, the kernel's receive path queues a record whose type differs from the one currently being processed onto rx_list for the next recvmsg() call to consume. STAR Labs SG's technical analysis (the vulnerability's original reporters) shows that when the record pulled from rx_list is zero-length and kernel TLS zero-copy mode is active, the kernel incorrectly re-queues the anchor sk_buff, corrupting its reference count. On socket teardown this manifests as a use-after-free in tls_sw_release_resources_rx, which STAR Labs demonstrated (KASAN-confirmed, tested on Linux 6.12.41) as a local privilege-escalation primitive usable to gain root: an attacker establishes a TLS socket with TCP_ULP kernel-TLS offload and zero-copy enabled, sends an Application Data (0x17) record, sends a zero-length Handshake (0x16) record, partially reads the first record via read(conn, buf, 0x100) leaving copied==0 so the type commitment is never finalized, sends a second Application Data (0x17) record, calls recvmsg() to trigger the content-type-mismatch path, then closes the socket to trigger the UAF. No special container or namespace context is required — STAR Labs' PoC runs entirely as a standard local unprivileged user.

A public, independently authored exploit (GitHub: khoatran107/cve-2025-39682, described as a variant of CVE-2024-58239) fully weaponizes the primitive into reliable root code execution and reports an ~79/100 success rate against Google's kernelCTF mitigation-v4-6.6 hardened target instance. The exploitation chain: after triggering the UAF, the attacker uses splice() to pull the dangling anchor skb into a pipe, giving the freed page a second (writable) reference; ~128 pipe buffers are then filled with marker bytes as a heap spray so one pipe reclaims the freed page; the attacker forces page-table-entry (PTE) allocation via repeated mmap()/page-fault cycles so the buddy allocator hands the still-pipe-held freed page back out as a kernel page-table page — a classic cross-cache attack. Because a freshly faulted PTE initially points at the fixed kernel symbol empty_zero_page, reading it back through the pipe leaks a kernel pointer; masking flag bits and subtracting a fixed offset yields the runtime kernel base address, defeating KASLR without needing to bypass SMEP/SMAP (the write path goes through the pipe-buffer kernel structure rather than a direct user-controlled pointer dereference). The attacker then overwrites the reclaimed PTE to point at the physical address of the kernel's core_pattern sysctl, and writes a crash-handler string such as "|/proc/%P/fd/666 %P" through the pipe — hijacking the kernel's core-dump handler so that the next process crash on the system executes an attacker-controlled program as root.

The bug was introduced with Linux kernel 6.0 (released 2022-10-02; regression commit 84c61fe1a75b4255df1e1e7c054c9e6d048da417) and fixed upstream on 2025-09-05 across five stable branches: 6.1.149, 6.6.103, 6.12.44, 6.16.4, and 6.17-rc3. Downstream distributions shipped their own backports — Debian 11 (bullseye) linux-6.1 6.1.153-1~deb11u1 (LTS update published 2025-10-13, bundled with 400+ other kernel CVEs), Ubuntu via USN-7833-3 (AWS kernel, 2025-10-24) and the broader USN-7835/7928/7940/8188 series (24.04 LTS 6.8.0-86.87, 25.04 6.14.0-34.34), and Red Hat Enterprise Linux 9/10 via RHSA-2025:16880/16904 plus related EUS/SAP errata. The vulnerable Kernel TLS code is also present in the Android kernel: Google's Android Security Bulletin tracks it as ASB-A-440544511 ("possible use after free due to an incorrect bounds check in tls_sw_recvmsg of tls_sw.c"), rated High severity, local escalation of privilege with no additional execution privileges or user interaction needed, published 2026-03-01 and last modified 2026-09-11, fixed at the 2025-03-05 security patch level or later — meaning unpatched Android devices carry the same root-privesc exposure as desktop/server Linux. Siemens also bundled the fix into SIMATIC CN 4100 firmware V5.0 (advisory SSA-032379, listing CVE-2025-39682 itself at CVSS 3.1 7.0 among 167 CVEs the firmware update addresses in total); SIMATIC CN 4100 is a communication node used to connect third-party systems into process-control (OT) environments, extending exposure — and the standing DoS/crash risk from the underlying use-after-free — into industrial networks running embedded Linux, though Siemens' advisory does not itself narrate a device-specific exploitation scenario beyond "update to V5.0." Siemens' independently-published 7.0 score is a third distinct CVSS 3.1 value for this single CVE, alongside NVD's 7.1 (local) and the CNA's 9.8 (network) — three publishers, three numbers, underscoring how unsettled the scoring is.

STAR Labs' advisory and a follow-on n-day technical analysis (hackmd, unauthenticated author) both narrate the exploit at instruction-level detail. The PoC uses three TLS 1.2 records over a kernel-TLS (`TCP_ULP`) zero-copy socket: record 1 is Application Data (0x17) carrying an encrypted "Hello world" payload; record 2 is a zero-length Handshake (0x16) record; record 3 is a second Application Data (0x17) record. A `read(conn, buf, 0x100)` partially consumes record 1, leaving the internal `copied` counter at 0 so the content-type commitment for the stream is never finalized; the next `recvmsg()` then processes record 2 off `rx_list` and corrupts the anchor `sk_buff`'s reference count. STAR Labs' KASAN build surfaces this as a `slab-use-after-free` in `kfree_skb_list_reason`, reached when `tls_sw_release_resources_rx` walks memory it no longer owns that was originally allocated by `tcp_sendmsg_locked`. The khoatran107 write-up (itself explicitly framed as "a variant of CVE-2024-58239," a related prior kernel UAF/exploit-technique pairing) refines this into full root code execution without any kernel-version fingerprinting step (no `/proc/version`, `/proc/kallsyms`, `uname`, or `dmesg` probing is used) — instead it leaks the KASLR-defeating kernel base purely via the architecturally-fixed `empty_zero_page` symbol reachable through the corrupted page-table entry, and finishes by writing the literal string `|/proc/%P/fd/666 %P` into `core_pattern` through the captured pipe to hijack the next process crash into root code execution. No container, namespace, or cgroup-specific targeting is described; the exploit runs as a standard, unprivileged local process.

CISA added CVE-2025-39682 to its Known Exploited Vulnerabilities catalog on 2026-09-18 'based on evidence of active exploitation,' setting a federal remediation deadline of 2026-09-21 under BOD 26-04. Notably, the two published CVSS 3.1 scores for this CVE diverge sharply: NVD's own primary analysis and Red Hat's independent assessment rate it 7.1/High with a LOCAL attack vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H), consistent with the local-attacker PoC STAR Labs and khoatran107 documented, while a secondary CNA score rates it 9.8/Critical with a NETWORK vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) — plausibly reflecting that the vulnerable net/tls receive-path code is reachable by any remote TLS peer whose ciphertext is decrypted by a kTLS-offloading service (e.g. nginx, HAProxy, Kafka deployments using ktls), since TLS record type/length framing inside the encrypted stream is attacker-controlled by whichever peer is sending data. Both scores are legitimately published; defenders should treat this as capable of both local privilege escalation (now with a public, reliable, root-yielding exploit) and, on ktls-enabled network services, a remotely-influenced trigger, and should not assume the lower/local score bounds real-world exposure. CISA classifies the underlying weakness as CWE-754 (Improper Check for Unusual or Exceptional Conditions); STAR Labs' root-cause finding is CWE-416 (Use-After-Free); Siemens' advisory separately tags it CWE-20 (Improper Input Validation) — three descriptions of the same defect from three vantage points.

MITRE ATT&CK techniques by tactic:

inhibit-response-function

T0814 Denial of Service

Initial Access

T1190 Exploit Public-Facing Application

Privilege Escalation

T1404 Exploitation for Privilege Escalation; T1546 Event Triggered Execution

Impact

T1499.004 Endpoint Denial of Service: Application or System Exploitation

Remediation

Patches

  • Upstream stable fixes: 2902c3ebcca52ca845c03182000e8d71d3a5196f (6.1.149), c09dd3773b5950e9cfb6c9b9a5f6e36d06c62677 (6.6.103), 3439c15ae91a517cf3c650ea15a8987699416ad9 (6.12.44), 29c0ce3c8cdb6dc5d61139c937f34cb888a6f42e (6.16.4), 62708b9452f8eb77513115b17c4f8d1a22ebf843 (6.17-rc3)
  • Debian 11 (bullseye): linux-6.1 6.1.153-1~deb11u1 (published 2025-10-13)
  • Ubuntu: USN-7833-3 (AWS kernel, 2025-10-24); linux 6.8.0-86.87 (24.04 LTS noble); linux 6.14.0-34.34 (25.04 plucky)
  • Red Hat: RHSA-2025:16880 (RHEL 9), RHSA-2025:16904 (RHEL 10), RHSA-2025:19104 (RHEL 9.4 EUS), RHSA-2025:19223/19224 (RHEL 9.2 SAP Solutions)
  • Android: security patch level 2025-03-05 or later (ASB-A-440544511)
  • Siemens SIMATIC CN 4100: update to firmware V5.0 or later

Immediate actions

  • Identify all Linux hosts/images running an affected kernel (6.0–6.1.148, 6.2–6.6.102, 6.7–6.12.43, 6.13–6.16.3, 6.17-rc1/rc2), prioritizing publicly-exposed, ktls-terminating services and multi-tenant hosts per CISA BOD 26-04.
  • Apply the vendor kernel update (Debian linux-6.1 6.1.153-1~deb11u1, Ubuntu 6.8.0-86.87 / 6.14.0-34.34 / USN-7833-3, or the applicable RHSA) or update to upstream 6.1.149/6.6.103/6.12.44/6.16.4/6.17-rc3+ by the CISA KEV due date of 2026-09-21.
  • A working public root-privilege-escalation exploit exists (GitHub khoatran107/cve-2025-39682, ~79% reliability against a hardened kernelCTF target) — treat unpatched local-user access anywhere on affected hosts as an imminent root-compromise path, not a theoretical risk.
  • Patch Android fleets to security patch level 2025-03-05 or later (ASB-A-440544511) — this is the same kernel flaw, not a separate issue.
  • Where kernel TLS (ktls) offload is enabled on network-facing services, review usage and where feasible temporarily disable it until patched.

Workarounds

  • No official workaround beyond patching is documented by upstream or vendors; disabling kernel TLS (ktls) offload on affected services removes the vulnerable code path at a performance cost.

Longer-term hardening

  • Track Linux kernel patch currency against the CISA KEV catalog and vendor stable-kernel releases as a standing vulnerability-management control.
  • Deploy kernel crash/KASAN-style panic monitoring and EDR capable of flagging anomalous recvmsg()/TLS record sequences, unexpected kernel oops on TLS-terminating hosts, or unexpected writes to /proc/sys/kernel/core_pattern.
  • For Siemens SIMATIC CN 4100 and other embedded/OT Linux appliances, maintain a firmware update cadence tied to vendor ProductCERT advisories (e.g. SSA-032379).
  • Include mobile/Android fleet kernel patch levels in the same vulnerability-management tracking used for server/desktop Linux, since shared kernel subsystems like net/tls affect both.

Affected and fixed versions

  • Linux — Linux Kernel
    Vulnerable versions: 6.0–6.1.148; 6.2–6.6.102; 6.7–6.12.43; 6.13–6.16.3; 6.17-rc1; 6.17-rc2
    Fixed in: 6.1.149; 6.6.103; 6.12.44; 6.16.4; 6.17-rc3
  • Debian — linux-6.1 (Debian 11 bullseye)
    Vulnerable versions: < 6.1.153-1~deb11u1
    Fixed in: 6.1.153-1~deb11u1
  • Canonical — linux (Ubuntu, multiple kernel flavors incl. AWS)
    Vulnerable versions: < 6.8.0-86.87 (24.04 noble); < 6.14.0-34.34 (25.04 plucky); pre-USN-7833-3 (AWS kernel)
    Fixed in: 6.8.0-86.87; 6.14.0-34.34; USN-7833-3 and related USN-7835/7928/7940/8188 series
  • Red Hat — Red Hat Enterprise Linux 9 / 10 kernel
    Vulnerable versions: pre-RHSA-2025:16880/16904/19104/19223/19224
    Fixed in: per RHSA-2025:16880 (RHEL 9), RHSA-2025:16904 (RHEL 10), RHSA-2025:19104/19223/19224 (RHEL 9.x EUS/SAP)
  • Google — Android (Kernel TLS component)
    Vulnerable versions: security patch level < 2025-03-05
    Fixed in: security patch level 2025-03-05+ (ASB-A-440544511)
  • Siemens — SIMATIC CN 4100
    Vulnerable versions: < V5.0
    Fixed in: V5.0

Timeline

  • The vulnerable rx_list handling logic enters the Linux kernel mainline with the 6.0 release (regression commit 84c61fe1a75b4255df1e1e7c054c9e6d048da417).
  • Billy Jheng Bing-Jhong and Muhammad Alifa Ramdhan of STAR Labs SG report the use-after-free to the Linux kernel security team after demonstrating a KASAN-confirmed local privilege-escalation PoC on Linux 6.12.41.
  • STAR Labs SG publishes a full technical advisory with root-cause analysis and working local privilege-escalation PoC for CVE-2025-39682.
  • Upstream fix lands across five stable branches (6.1.149, 6.6.103, 6.12.44, 6.16.4, 6.17-rc3) and CVE-2025-39682 is published; NVD assigns a primary local-vector CVSS 3.1 of 7.1 while a secondary CNA score rates it 9.8 with a network vector.
  • Debian issues an LTS security update for Debian 11 (bullseye), backporting the fix in linux-6.1 6.1.153-1~deb11u1 alongside 400+ other kernel CVEs.
  • Canonical publishes USN-7833-3 for the Ubuntu AWS kernel, part of a broader USN-7835/7928/7940/8188 series backporting the fix across Ubuntu kernel flavors including 24.04 LTS and 25.04.
  • Google publishes Android Security Bulletin entry ASB-A-440544511, confirming the same net/tls use-after-free in the Android Kernel TLS component as a High-severity local privilege-escalation issue fixed at the 2025-03-05 security patch level.
  • Red Hat's public Bugzilla tracker (BZ#2393511) for CVE-2025-39682 is last updated, referencing RHSA-2025:16880/16904 and related RHEL 9.x EUS/SAP errata.
  • Google's Android Security Bulletin entry ASB-A-440544511 for CVE-2025-39682 is last modified, shortly before the CISA KEV addition.
  • CISA adds CVE-2025-39682 to the Known Exploited Vulnerabilities catalog, citing evidence of active exploitation; NVD's record is last-modified the same day.
  • CISA's BOD 26-04 remediation deadline for federal agencies to patch or discontinue use of affected systems.

Sources cited

Other reports on CVE-2025-39682

Previous and next in vulnerability

Drafted by the Threadlinqs research pipeline from 15 sources; published ; last updated —.

Threadlinqs Intelligence — Real-Time Threat Detection Platform

// threat_feed
$ sort --newest
Showing all threats

Live intelligence console

Threat level

Latest Threats