Skip to main content
Mallory
HighVulnerability

CVE-2026-98364: Use-after-free in Linux kernel XFRM bundle creation

Published Oct 6, 2026 · Updated 3 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days15 mentions · peak 4 in a dayToday
CVSS7.8High · v3.1
EPSS0.12%2nd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Linux
IdentifiersCVE-2026-98364CWE-416

CVE-2026-98364 is a use-after-free vulnerability in Linux kernel XFRM IPsec routing. The xfrm_bundle_create() and xfrm_create_dummy_bundle() functions read dst->dev without acquiring a network-device reference before passing the pointer to xfrm_fill_dst(). A concurrent RTM_DELLINK operation can replace dst->dev through dst_dev_put() and free the original net_device. Subsequent access through the stale pointer in xfrm6_fill_dst() causes a use-after-free during device-reference acquisition. The resulting invalid kernel memory access can cause a kernel crash or denial of service.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful triggering causes access to a freed net_device object in kernel context. An eight-byte invalid read during xfrm6_fill_dst() has been demonstrated with KASAN. A kernel crash and consequent system-wide denial of service are possible; arbitrary code execution, privilege escalation, and information disclosure are not established for this vulnerability.

Remediation

Patch, then assume compromise.

Install the applicable distribution kernel security update and reboot into the updated kernel. Relevant updates include RHSA-2026:93412 for RHEL 9, RHSA-2026:93413 for RHEL 10, and corresponding AlmaLinux, Rocky Linux, and Oracle Linux updates. RHEL 9 advisory RHSA-2026:97873 also supplies the fix in kernel 5.14.0-741.20.1.el9_9. Amazon Linux 2023 provides an update through ALAS2023-2026-3251. The code-level fix uses dst_dev_rcu() to read dst->dev and keeps the RCU read-side critical section active until xfrm_fill_dst() acquires the required device references. Fixed versions vary by distribution and support channel.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
LinuxLinux Kerneloperating_system
FAQ

Frequently asked questions

Is CVE-2026-98364 exploited in the wild?
As of Nov 14, 2026, Mallory has no reports of CVE-2026-98364 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-98364?
As of Nov 14, 2026, Mallory has found no public exploit for CVE-2026-98364.
Is there a patch for CVE-2026-98364?
Install the applicable distribution kernel security update and reboot into the updated kernel. Relevant updates include RHSA-2026:93412 for RHEL 9, RHSA-2026:93413 for RHEL 10, and corresponding AlmaLinux, Rocky Linux, and Oracle Linux updates.
What products are affected by CVE-2026-98364?
Linux Kernel.
How severe is CVE-2026-98364?
CVE-2026-98364 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 0.12% (2nd percentile) as of Nov 14, 2026.
Activity feed

Recent activity

18 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+14 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.