LiveActive security incident?Get immediate response
CVE Record

CVE-2026-43084: netfilter: nfnetlink_queue: make hash table per queue

In the Linux kernel, the following vulnerability has been resolved: netfilter: nfnetlink_queue: make hash table per queue Sharing a global hash table among all queues is tempting, but it can cause crash: BUG: KASAN: slab-use-after-free in nfqnl_recv_verdict+0x11ac/0x15e0 [nfnetlink_queue] [..] nfqnl_recv_verdict+0x11ac/0x15e0 [nfnetlink_queue] nfnetlink_rcv_msg+0x46a/0x930 kmem_cache_alloc_node_noprof+0x11e/0x450 struct nf_queue_entry is freed via kfree, but parallel cpu can still encounter such an nf_queue_entry when walking the list. Alternative fix is to free the nf_queue_entry via kfree_rcu() instead, but as we have to alloc/free for each skb this will cause more mem pressure.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A race condition in Linux netfilter queue handling can let one processor access an entry after another processor frees it. This may crash the kernel and, according to the supplied CVSS assessment, could affect confidentiality, integrity, and availability. Exploitation requires local, low-privileged access; no user interaction is required.

Executive priority

Treat as a high-priority kernel maintenance issue on exposed shared hosts and network-security systems. Schedule prompt patching through normal emergency-change processes, while confirming actual nfnetlink_queue use. Immediate crisis response is not supported because active exploitation is not evidenced and remote exploitation is not indicated.

Technical view

The nfnetlink_queue subsystem shared a global hash table across queues. Concurrent verdict processing could traverse an nf_queue_entry after another CPU freed it, causing a slab use-after-free in nfqnl_recv_verdict. The fix makes the hash table queue-specific, preventing unsafe cross-queue access without adding per-packet RCU memory pressure.

Likely exposure

Potential exposure is limited to Linux hosts running an affected kernel and using nfnetlink_queue functionality. The bundle identifies fixed commits and lists 6.12.75, 6.18.14, and 6.19.4 as unaffected, but does not provide complete vulnerable version ranges. Distribution package status must therefore be checked directly.

Exploitation context

The CVSS vector indicates local access, low complexity, low privileges, and no user interaction. The CVE is not listed as KEV, and the supplied sources provide no evidence of active exploitation or a public exploit. Practical exploitability beyond triggering a kernel crash is not established here.

Researcher notes

The source demonstrates a concurrent lifetime-management flaw involving a globally shared hash table. Queue-local tables are the selected remediation; kfree_rcu was considered but rejected because per-packet allocation would increase memory pressure. Exact introduction points and vulnerable release ranges are absent from the bundle, so commit ancestry and distribution backports require verification.

Mitigation direction

  • Update to a vendor-supported kernel containing the applicable upstream stable fix.
  • Confirm distribution advisories or package changelogs map the installed kernel to CVE-2026-43084.
  • Prioritize multi-user, container-hosting, or security-gateway systems that use nfnetlink_queue.
  • If updating is delayed, consult vendor guidance about safely limiting nfnetlink_queue availability.

Validation and detection

  • Inventory running kernel versions, not only installed kernel packages.
  • Determine whether nfnetlink_queue is loaded or required by firewall and packet-inspection workloads.
  • Verify the kernel package includes one of the cited fixes or an equivalent backport.
  • Reboot after updating and confirm the running kernel is the remediated build.
  • Review kernel logs for nfqnl_recv_verdict crashes or use-after-free diagnostics.
Prepared
Confidence
medium
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-43084 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2026-43084Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux371de2bef6582a3f58049b3d18e190924af9c9a0, 870e3e63da8e88daffe9d692a025c711658018a8, 70e2e3ce4f6841e12ec1c104fc76c0e707398ec4, e19079adcd26a25d7d3e586b1837493361fdf8b6unaffected
LinuxLinux6.12.75, 6.18.14, 6.19.4unaffected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.