Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-74464: net: openvswitch: fix skb leak on flow key update failure during ct

Noroxi assessment

Priority: Monitor (action score 0/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.17% (FIRST EPSS).
  • Fixed version: Linux Linux 22e0ca88090d89c128078062186b03bb5fdc4f98, 393f3c72600ab6721d732a0ab245bc896c5b28fc, 6cc523eaee72c4e91894136cff64946ae9de2cda; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.152.1-1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 22e0ca88090d89c128078062186b03bb5fdc4f98, 393f3c72600ab6721d732a0ab245bc896c5b28fc, 6cc523eaee72c4e91894136cff64946ae9de2cda; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.152.1-1 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: net: openvswitch: fix skb leak on flow key update failure during ct ovs_ct_execute() always steals or frees the skb on failure while ovs_flow_key_update() does not. So, if it fails and we return right away, the skb ends up leaked. Fix that by breaking instead and letting the common error handling code at the bottom of the loop to free the skb properly. This is a very unlikely scenario as it requires the packet to become unparseable by applying a set of actions on a previously parseable skb, but should be fixed nevertheless. Reported by Sashiko.

—No exploit Fix available
Published
Aug 15, 2026
Updated
Aug 19, 2026
EPSS
0.1% · 7th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

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

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.

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.

—

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

    • 4.3affected
    • ec0d043d05e6e3c0c2fac5de922c800c027c6386 and later · before b77126b2915900f69f9fcf5d624a77c8e6d50c31affected · git
    • ec0d043d05e6e3c0c2fac5de922c800c027c6386 and later · before 6cc523eaee72c4e91894136cff64946ae9de2cdaaffected · git
    • ec0d043d05e6e3c0c2fac5de922c800c027c6386 and later · before 22e0ca88090d89c128078062186b03bb5fdc4f98affected · git
    • ec0d043d05e6e3c0c2fac5de922c800c027c6386 and later · before 736e972f3f8a304158345223ac6e816166a467ceaffected · git
    • ec0d043d05e6e3c0c2fac5de922c800c027c6386 and later · before e84dfaac50aab45ad8c670da43e3aa1f97bd2a41affected · git
    • ec0d043d05e6e3c0c2fac5de922c800c027c6386 and later · before e0ba8eaef2a0d02a7a485e6a7157e47272b65ceaaffected · git
    • ec0d043d05e6e3c0c2fac5de922c800c027c6386 and later · before 393f3c72600ab6721d732a0ab245bc896c5b28fcaffected · git
    • ec0d043d05e6e3c0c2fac5de922c800c027c6386 and later · before bc62e843bc48f933da765ce47079fd992e535794affected · git
    • before 4.3not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.187-16.1.187-1
Debian:12linux-6.12before 6.12.107-1~deb12u16.12.107-1~deb12u1
Debian:13linuxbefore 6.12.105-16.12.105-1
Debian:14linuxbefore 7.1.8-17.1.8-1

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-74462Aug 15, 2026 · i2c: imx: mark I2C adapter when hardware is powered down
    0Monitor
  • ← EarlierCVE-2026-74463Aug 15, 2026 · i2c: jz4780: Cache host clock rate at probe to prevent CCF prepare_lock deadlock
    0Monitor
  • Later →CVE-2026-74468Aug 15, 2026 · gpio: pch: use raw_spinlock_t for the register lock
    0Monitor

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 Linux22e0ca88090d89c128078062186b03bb5fdc4f98Vendor (CNA)
Linux Linux393f3c72600ab6721d732a0ab245bc896c5b28fcVendor (CNA)
Linux Linux6cc523eaee72c4e91894136cff64946ae9de2cdaVendor (CNA)
Linux Linux736e972f3f8a304158345223ac6e816166a467ceVendor (CNA)
Linux Linuxb77126b2915900f69f9fcf5d624a77c8e6d50c31Vendor (CNA)
Linux Linuxbc62e843bc48f933da765ce47079fd992e535794Vendor (CNA)
Linux Linuxe0ba8eaef2a0d02a7a485e6a7157e47272b65ceaVendor (CNA)
Linux Linuxe84dfaac50aab45ad8c670da43e3aa1f97bd2a41Vendor (CNA)
azl3 kernel 6.6.150.1-1 on Azure Linux 3.06.6.152.1-1 · Release NotesMicrosoft (MSRC)
debian:linux6.1.187-1 · Debian:12Package registry (OSV)
debian:linux-6.126.12.107-1~deb12u1 · Debian:12Package 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).

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.

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.

No nightly-computed relations.

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

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

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. Fix✗ → ✓

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

References

All records