Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-64035: igc: set tx buffer type for SMD frames

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.44% (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.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: Linux Linux 1c8587bd025244aa52061f5ceecbf5e68a1063d9, 1f83545f432d106d5fc71d3997b2d382104ebcc4, 5acc641e590e008caaed480ed9ffae47cf7ecbdf.

Low priority for now. Upgrade to Linux Linux 1c8587bd025244aa52061f5ceecbf5e68a1063d9, 1f83545f432d106d5fc71d3997b2d382104ebcc4, 5acc641e590e008caaed480ed9ffae47cf7ecbdf 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: igc: set tx buffer type for SMD frames Sashiko pointed out that igc_fpe_init_smd_frame() initializes igc_tx_buffer fields for an SMD skb, but does not set the buffer type: https://sashiko.dev/#/patchset/20260415025226.114115-1-kohei%40enjuk.jp Since igc_tx_buffer entries are reused, a stale XDP or XSK type can remain and make TX completion use the wrong cleanup path. Set the buffer type to IGC_TX_BUFFER_TYPE_SKB.

CriticalCVSS 9.8 · v3.1—No exploit Fix available
Published
Jul 19, 2026
Updated
Oct 19, 2026
EPSS
0.4% · 38th 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%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

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

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 instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • 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 (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

Running WordPress? Scan your site free with WP Lens

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

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel6.16 and later · before 6.18.34
  • linux linux kernel6.19 and later · before 7.0.11
  • linux linux kernel7.1

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.16affected
    • 5422570c0010bb968738f9256eb2bf83e79b4d63 and later · before 1f83545f432d106d5fc71d3997b2d382104ebcc4affected · git
    • 5422570c0010bb968738f9256eb2bf83e79b4d63 and later · before 1c8587bd025244aa52061f5ceecbf5e68a1063d9affected · git
    • 5422570c0010bb968738f9256eb2bf83e79b4d63 and later · before 5acc641e590e008caaed480ed9ffae47cf7ecbdfaffected · git
    • before 6.16not 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.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2

+96

Same product

linux: all records

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-64033Jul 19, 2026 · RDMA/rtrs: Fix use-after-free in path file creation cleanup
    39Monitor
  • ← EarlierCVE-2026-64034Jul 19, 2026 · net: mana: Fix TOCTOU double-fetch of hwc_msg_id from DMA buffer
    37Monitor
  • Later →CVE-2026-64036Jul 19, 2026 · cgroup/rstat: validate cpu before css_rstat_cpu() access
    31Monitor

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 Linux1c8587bd025244aa52061f5ceecbf5e68a1063d9Vendor (CNA)
Linux Linux1f83545f432d106d5fc71d3997b2d382104ebcc4Vendor (CNA)
Linux Linux5acc641e590e008caaed480ed9ffae47cf7ecbdfVendor (CNA)
almalinux:kernel5.14.0-687.56.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel6.12.0-211.64.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k5.14.0-687.56.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k6.12.0-211.64.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-core5.14.0-687.56.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core6.12.0-211.64.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-687.56.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug6.12.0-211.64.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-687.56.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core6.12.0-211.64.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-687.56.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel6.12.0-211.64.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-687.56.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched6.12.0-211.64.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-687.56.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules6.12.0-211.64.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-687.56.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core6.12.0-211.64.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-687.56.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra6.12.0-211.64.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-687.56.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel6.12.0-211.64.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel-matched5.14.0-687.56.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel-matched6.12.0-211.64.1.el10_2 · AlmaLinux:10Package registry (OSV)
debian:linux7.0.12-1 · Debian:14Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-687.56.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-687.56.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)

+11

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).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-4304079 days apartnet: ipv6: ndisc: fix ndisc_ra_useropt to initialize nduseropt_padX fields to zero to prevent an info-leak
    28Monitor
  • CVE-2022-50169396 days apartwifi: wil6210: debugfs: fix info leak in wil_write_file_wmi()
    28Monitor
  • CVE-2022-49865444 days apartipv6: addrlabel: fix infoleak when sending struct ifaddrlblmsg to network
    28Monitor
  • CVE-2025-38601334 days apartwifi: ath11k: clear initialized flag for deinit-ed srng lists
    22Monitor
  • CVE-2025-38532337 days apartnet: libwx: properly reset Rx ring descriptor
    22Monitor
  • CVE-2022-49217508 days apartscsi: pm8001: Fix abort all task initialization
    22Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

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-909 · Missing Initialization of Resource

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/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. SSVC exploitation— → none
  2. Fix✗ → ✓

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

References

Show all references (2 more)

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

All records