Skip to content
Noroxi
CVE.org (no NVD analysis yet)· CNA Linux

CVE-2026-98364: xfrm: hold net_device reference under RCU in bundle creation

HighCVSS 7.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 31/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.12% (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 8d85d6bc9c46dc41cb2be0eac53f8ab068c3a807, 9fa903b24b1f46b4ff5443bcd4aca23e5c57f9c1; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 Release Notes.

Low priority for now. Upgrade to Linux Linux 8d85d6bc9c46dc41cb2be0eac53f8ab068c3a807, 9fa903b24b1f46b4ff5443bcd4aca23e5c57f9c1; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.159.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: xfrm: hold net_device reference under RCU in bundle creation xfrm_bundle_create() and xfrm_create_dummy_bundle() read dst->dev into a local pointer without taking a device reference, then pass it to xfrm_fill_dst(). A concurrent RTM_DELLINK replaces dst->dev via dst_dev_put() and frees the old net_device, causing a use-after-free when xfrm6_fill_dst() later dereferences the stale dev pointer. BUG: KASAN: slab-use-after-free in xfrm6_fill_dst+0x82c/0x860 (net/ipv6/xfrm6_policy.c:86 netdev_hold()) Read of size 8 at addr ffff8880142fe588 by task exploit/153 Call Trace: xfrm6_fill_dst+0x82c/0x860 xfrm_resolve_and_create_bundle+0x21d4/0x2bd0 xfrm_lookup_with_ifid+0x485/0x1640 ip6_dst_lookup_flow+0x19b/0x1e0 udpv6_sendmsg+0x1443/0x2dd0 Fix this by reading dst->dev via dst_dev_rcu() and keeping the RCU read-side critical section active until xfrm_fill_dst() has taken the required device references.

Published
Oct 6, 2026
Updated
Oct 19, 2026
EPSS
0.1% · 1th percentile
CWE
—

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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-98364

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

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
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.

—

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

    • 2.6.25affected
    • 25ee3286dcbc830a833354bb1d15567956844813 and later · before 8d85d6bc9c46dc41cb2be0eac53f8ab068c3a807affected · git
    • 25ee3286dcbc830a833354bb1d15567956844813 and later · before 9fa903b24b1f46b4ff5443bcd4aca23e5c57f9c1affected · git
    • before 2.6.25not affected · semver
    • 7.2.8 and later · up to and including 7.2.*not affected · semver
    • 7.3 and laternot affected · original_commit_for_fix

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-211.72.1.el10_26.12.0-211.72.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.72.1.el10_26.12.0-211.72.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.72.1.el10_26.12.0-211.72.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.72.1.el10_26.12.0-211.72.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.72.1.el10_26.12.0-211.72.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.72.1.el10_26.12.0-211.72.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.72.1.el10_26.12.0-211.72.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.72.1.el10_26.12.0-211.72.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.72.1.el10_26.12.0-211.72.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.72.1.el10_26.12.0-211.72.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.72.1.el10_26.12.0-211.72.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.72.1.el10_26.12.0-211.72.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.72.1.el10_26.12.0-211.72.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.72.1.el10_26.12.0-211.72.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.72.1.el10_26.12.0-211.72.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.72.1.el10_26.12.0-211.72.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.72.1.el10_26.12.0-211.72.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.72.1.el10_26.12.0-211.72.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.72.1.el10_26.12.0-211.72.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.72.1.el10_26.12.0-211.72.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.72.1.el10_26.12.0-211.72.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.72.1.el10_26.12.0-211.72.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.72.1.el10_26.12.0-211.72.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.72.1.el10_26.12.0-211.72.1.el10_2

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-98362Oct 6, 2026 · clk: scpi: bound-check DVFS index in scpi_dvfs_recalc_rate
    0Monitor
  • ← EarlierCVE-2026-98363Oct 6, 2026 · firmware: arm_scpi: reject DVFS OPP count above MAX_DVFS_OPPS
    0Monitor
  • Later →CVE-2026-98365Oct 6, 2026 · RDMA/rxe: Fix integer overflow in mr_check_range() leading to OOB access
    39Monitor

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 Linux8d85d6bc9c46dc41cb2be0eac53f8ab068c3a807Vendor (CNA)
Linux Linux9fa903b24b1f46b4ff5443bcd4aca23e5c57f9c1Vendor (CNA)
azl3 kernel 6.6.157.1-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
azl3 kernel 6.6.159.1-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
azl3 kernel 6.6.161.1-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
almalinux:kernel5.14.0-687.64.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-687.64.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-687.64.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-687.64.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-687.64.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-687.64.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-687.64.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-687.64.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-687.64.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-687.64.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-687.64.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel-matched5.14.0-687.64.1.el9_8 · AlmaLinux:9Package registry (OSV)
debian:linux7.2.8-1 · Debian:14Package registry (OSV)
rocky linux:kernel0:5.14.0-687.64.1.el9_8 · Rocky Linux:9Package 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.

  1. Published
  2. Fix recordedsame day
  3. TodayNov 13, 2026+38 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Not on record for this CVE: 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
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

—

CVSS vector

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

nvd-secondary

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.

Change log

  1. CVSS— → 7.8
  2. Severity— → high
  3. Exploit maturity— → none
  4. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (1 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records