Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-74742: veth: fix queue index used to wake the peer txq in veth_poll

Noroxi assessment

Priority: Monitor (action score 30/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.46% (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 6.12.105, 60db47f02bfa2aa688938aa199117ec4f8e31d23, 73f8dd22b1e533a99ecc3f9b5de6c6daccaecace.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 6.12.105, 60db47f02bfa2aa688938aa199117ec4f8e31d23, 73f8dd22b1e533a99ecc3f9b5de6c6daccaecace 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: veth: fix queue index used to wake the peer txq in veth_poll veth_poll() derives the index of the peer TX queue to wake from rq->xdp_rxq.queue_index. That field is only initialized by xdp_rxq_info_reg() in veth_enable_xdp_range(), which runs only when an XDP program is attached. On the plain GRO/NAPI path (veth_napi_enable_range()) xdp_rxq_info_reg() is never called, so queue_index stays 0 for every queue, as priv->rq is zero-allocated. So in a multi-queue setup with GRO enabled and no XDP program attached, every NAPI instance looks at the peer's TX queue 0. If veth_xmit() stops peer TX queue 1 because the ptr_ring is full (NETDEV_TX_BUSY), nothing ever wakes it again: the poller draining queue 1 wakes queue 0 instead. veth implements no ndo_tx_timeout, so the netdev watchdog does not kick in either, and the queue stays stopped indefinitely. Derive the index from the position of the rq within priv->rq instead, which is correct regardless of whether XDP was ever enabled. Scripts to reproduce the stall are available at https://github.com/netoptimizer/veth-backpressure-performance-testing

HighCVSS 7.5 · v3.1—No exploit Fix available
Published
Aug 26, 2026
Updated
Aug 27, 2026
EPSS
0.4% · 40th percentile
CWE
—

Report tools

JSON

Action score

30

Monitor

Low priority for now.

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

CNA vs NVD score

NVD
—
CNA · Linux
7.5
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-74742

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

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

    • 6.16affected
    • 9fe31b3f314534e238aa6d0b6fb492134cbcf8be and later · before b662a1fb4f3a5ea19bac24eea8315b1d05be51e7affected · git
    • dc82a33297fc2c58cb0b2b008d728668d45c0f6a and later · before 73f8dd22b1e533a99ecc3f9b5de6c6daccaecaceaffected · git
    • dc82a33297fc2c58cb0b2b008d728668d45c0f6a and later · before 90bb11fb29d3c55a2c46dc7c386d096b286e7fcfaffected · git
    • dc82a33297fc2c58cb0b2b008d728668d45c0f6a and later · before 60db47f02bfa2aa688938aa199117ec4f8e31d23affected · git
    • 6.12.61 and later · before 6.12.105affected · semver
    • before 6.16not affected · semver
    • 6.12.105 and later · up to and including 6.12.*not affected · semver
    • 6.18.46 and later · up to and including 6.18.*not affected · semver
    • 7.1.10 and later · up to and including 7.1.*not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
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.10-17.1.10-1

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-74738Aug 26, 2026 · regmap: sdw-mbq: don't call an unset readable_reg callback
    0Monitor
  • ← EarlierCVE-2026-74741Aug 26, 2026 · net: ngbe: fix NULL pointer dereference in non-MSI-X interrupt enabling
    30Monitor
  • Later →CVE-2026-74749Aug 26, 2026 · rseq: Prevent hard lockup on granted time slice extension
    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 Linux6.12.105Vendor (CNA)
Linux Linux60db47f02bfa2aa688938aa199117ec4f8e31d23Vendor (CNA)
Linux Linux73f8dd22b1e533a99ecc3f9b5de6c6daccaecaceVendor (CNA)
Linux Linux90bb11fb29d3c55a2c46dc7c386d096b286e7fcfVendor (CNA)
Linux Linuxb662a1fb4f3a5ea19bac24eea8315b1d05be51e7Vendor (CNA)
debian:linux6.12.105-1 · Debian:13Package 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.

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.

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

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
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Fix✗ → ✓

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

References

Show all references (3 more)

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

All records