CVE Intelligence
Unknown

CVE-2026-99057 — xen/netfront: don't leak the skb when xennet_fill_frags() fails

In the Linux kernel, the following vulnerability has been resolved: xen/netfront: don't leak the skb when xennet_fill_frags() fails When a response chain has more slots than fit in the skb's frags, xennet_fill_frags() returns an error and xennet_poll() jumps to its error path. That path moves what's left on tmpq to errq to be freed, but the skb being filled was already dequeued from tmpq, so it's never freed. Each chain that overflows leaks the skb and the pages attached to it as frags, and the backend decides how many slots it sends. Put the skb back on tmpq before taking the error path, like the xennet_set_skb_gso() failure just above it does.

Published Oct 23, 2026 · Updated Oct 30, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: Linux

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.2% (30-day exploitation probability)+1

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.18%
ahead of 7% of scored CVEs · Oct 30, 2026
Affects
Linux
Linux
CVSS base
—
Score not published yet.

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Linux Linux version b73a161e9beff24bf1803ba393dff95a255268f9≥ ad4f15dc2c70b1de5e0a64d27335962fbc9cf71c and < 53a131eb2a998c77e2851401b32b712d6c6e8487≥ ad4f15dc2c70b1de5e0a64d27335962fbc9cf71c and < 0cf0a25a639c535146c5eb4480d256995721aed6≥ ad4f15dc2c70b1de5e0a64d27335962fbc9cf71c and < 6e6bd1051daabc327233c3ca3d00613fc6783c8eversion 4.19≥ 4.18.11 and < 4.19≥ 4.14.73 and < 4.15≥ 4.9.130 and < 4.10
and 9 more ≥ 4.4.159 and < 4.5≥ ad4f15dc2c70b1de5e0a64d27335962fbc9cf71c and < 5051df031144753d3e18862514969146b601d089version 7eced4478f4ec6ff0a603ddfd6e24a5d3831fca7version 29a6193c0d74390c004808441061ac1812cf6f51version bd1468048aa3e2af865da92990539946d4483989≥ ad4f15dc2c70b1de5e0a64d27335962fbc9cf71c and < 93ccaf1c26e2133396173b76a071e59024daa622≥ ad4f15dc2c70b1de5e0a64d27335962fbc9cf71c and < 84e3ea6502b5f14ce8d499d0b6e0e38386274cf0≥ ad4f15dc2c70b1de5e0a64d27335962fbc9cf71c and < 086944c1c2cbb683543bc3ff08637847b03c8009≥ ad4f15dc2c70b1de5e0a64d27335962fbc9cf71c and < 99011a11c97340ef7290df7dc199305c73fab2f2
Vulnerable CVE Program (cve.org) e CISA ADP

EPSS over time FIRST

Oct 24, 2026 → Oct 30, 2026 · 7 reading(s) · max 0.21%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Not enough vector or weakness data: use the affected application’s logs as a starting point.
application logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · linux/linux
    Oct 30, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 23, 2026
  • Affected products added · linux/linux
    Oct 23, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · → Received
    Oct 23, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 23, 2026 · Alertas do Telegram
  • CVE published
    Oct 23, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

  • 3× References added · Oct 23, 2026 – Oct 30, 2026
  • 1× Official description updated · Oct 23, 2026 – Oct 23, 2026

References

10 on the record

Elsewhere on this site

Linux
every CVE for this vendor

Related CVEs (same products)

  • CVE-2026-99216 Drivers: hv: Don't reset VMBus connection state on error/exit paths 2d
  • CVE-2026-99215 power: supply: core: prevent unregistering a power supply while a callback runs 2d
  • CVE-2026-99207 scsi: target: Disable interrupts while holding delayed_cmd_lock 2d
  • CVE-2026-99208 drm/xe/oa: Zero OA buffer at allocation 2d
  • CVE-2026-99209 drm/xe: skip eviction of a BO with no resource 2d
  • CVE-2026-99210 accel/rocket: clear rdev on device init failure 2d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No CVSS score published by NVD, the CNA, CISA or GitHub so far.
  • No fixed version, patch or mitigation documented.
  • No CISA SSVC assessment.
  • No CWE classification.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-99057 is "xen/netfront: don't leak the skb when xennet_fill_frags() fails", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.18% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.