Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-64132: ipv6: ioam: refresh hdr pointer before ioam6_event()

CriticalCVSS 9.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 39/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.49% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 24de676da63c1122d2c13b0d546238b66d1b4e62, 5af905aa8e91ff8d94572a1e089558f21dcf24ed, 769723124b7c3b2bfea4cf68ad292698b87c8d01.

Low priority for now. Upgrade to Linux Linux 24de676da63c1122d2c13b0d546238b66d1b4e62, 5af905aa8e91ff8d94572a1e089558f21dcf24ed, 769723124b7c3b2bfea4cf68ad292698b87c8d01 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: ipv6: ioam: refresh hdr pointer before ioam6_event() Reported by Sashiko: In ipv6_hop_ioam(), the hdr pointer is initialized to point into the skb's linear data buffer. Later, the code calls skb_ensure_writable(), which might reallocate the buffer: if (skb_ensure_writable(skb, optoff + 2 + hdr->opt_len)) goto drop; /* Trace pointer may have changed */ trace = (struct ioam6_trace_hdr *)(skb_network_header(skb) + optoff + sizeof(*hdr)); ioam6_fill_trace_data(skb, ns, trace, true); ioam6_event(IOAM6_EVENT_TRACE, dev_net(skb->dev), GFP_ATOMIC, (void *)trace, hdr->opt_len - 2); If the skb is cloned or lacks sufficient linear headroom, skb_ensure_writable() will invoke pskb_expand_head(), which reallocates the skb's data buffer and frees the old one, invalidating pointers to it. While the code recalculates the trace pointer immediately after the call to skb_ensure_writable(), it fails to recalculate the hdr pointer. This patch fixes the above by recalculating the hdr pointer before passing hdr->opt_len to ioam6_event(), so that we avoid any UaF.

Published
Jul 19, 2026
Updated
Aug 13, 2026
EPSS
0.4% · 42th percentile

Report tools

JSON

Action score

39

Monitor

Low priority for now.

CVSS
39 / 40 · 9.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.4%

CNA vs NVD score

NVD
—
CNA · Linux
9.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-64132

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

  • Stack 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.

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

    • 6.9affected
    • f655c78d6225f585ef60a9d93ffb79d507ff3ad3 and later · before 769723124b7c3b2bfea4cf68ad292698b87c8d01affected · git
    • f655c78d6225f585ef60a9d93ffb79d507ff3ad3 and later · before 24de676da63c1122d2c13b0d546238b66d1b4e62affected · git
    • f655c78d6225f585ef60a9d93ffb79d507ff3ad3 and later · before 5af905aa8e91ff8d94572a1e089558f21dcf24edaffected · git
    • f655c78d6225f585ef60a9d93ffb79d507ff3ad3 and later · before e46e6bc97fb1f339730ff1ba74267fbf48e7a422affected · git
    • before 6.9not affected · semver
    • 6.12.92 and later · up to and including 6.12.*not affected · semver
    • 6.18.34 and later · up to and including 6.18.*not affected · semver
    • 7.0.11 and later · up to and including 7.0.*not affected · semver
    • 7.1 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.63.1.el10_26.12.0-211.63.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.63.1.el10_26.12.0-211.63.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.63.1.el10_26.12.0-211.63.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.63.1.el10_26.12.0-211.63.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.63.1.el10_26.12.0-211.63.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.63.1.el10_26.12.0-211.63.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.63.1.el10_26.12.0-211.63.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.63.1.el10_26.12.0-211.63.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.63.1.el10_26.12.0-211.63.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.63.1.el10_26.12.0-211.63.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.63.1.el10_26.12.0-211.63.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.63.1.el10_26.12.0-211.63.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.63.1.el10_26.12.0-211.63.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.63.1.el10_26.12.0-211.63.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.63.1.el10_26.12.0-211.63.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.63.1.el10_26.12.0-211.63.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.63.1.el10_26.12.0-211.63.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.63.1.el10_26.12.0-211.63.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.63.1.el10_26.12.0-211.63.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.63.1.el10_26.12.0-211.63.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.63.1.el10_26.12.0-211.63.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.63.1.el10_26.12.0-211.63.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.63.1.el10_26.12.0-211.63.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.63.1.el10_26.12.0-211.63.1.el10_2

+53

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-64129Jul 19, 2026 · mm/migrate_device: fix spinlock leak in migrate_vma_insert_huge_pmd_page
    22Monitor
  • ← EarlierCVE-2026-64130Jul 19, 2026 · mm/page_alloc: fix initialization of tags of the huge zero folio with init_on_free
    22Monitor
  • Later →CVE-2026-64135Jul 19, 2026 · hwmon: (pmbus/adm1266) widen blackbox-info buffer to I2C_SMBUS_BLOCK_MAX
    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 Linux24de676da63c1122d2c13b0d546238b66d1b4e62Vendor (CNA)
Linux Linux5af905aa8e91ff8d94572a1e089558f21dcf24edVendor (CNA)
Linux Linux769723124b7c3b2bfea4cf68ad292698b87c8d01Vendor (CNA)
Linux Linuxe46e6bc97fb1f339730ff1ba74267fbf48e7a422Vendor (CNA)
almalinux:kernel6.12.0-211.63.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k6.12.0-211.63.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-core6.12.0-211.63.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug6.12.0-211.63.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-core6.12.0-211.63.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel6.12.0-211.63.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched6.12.0-211.63.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules6.12.0-211.63.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-core6.12.0-211.63.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra6.12.0-211.63.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel6.12.0-211.63.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel-matched6.12.0-211.63.1.el10_2 · AlmaLinux:10Package registry (OSV)
debian:linux6.12.94-1 · Debian:13Package 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.

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

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • 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
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

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

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

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