# CVE-2026-90142: virtio_net: Fix resize of the RX ring

> A memory corruption vulnerability in the Linux kernel's virtio_net driver allows attackers to write past buffer boundaries when resizing RX rings with AF_XDP sockets.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 21 Oct 2026
- **Also known as:** BELL-CVE-2026-90142, DEBIAN-CVE-2026-90142, GHSA-2rwj-7pmr-4q35, UBUNTU-CVE-2026-90142

## What is CVE-2026-90142?

CVE-2026-90142 is a high-severity memory corruption vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

virtio_net: Fix resize of the RX ring

When a AF_XDP socket is attached, the virtnet_rx_resize
should resize the rq->xsk_buffs XSK buffer array. Otherwise,
when the size grows, the virtnet_rx_resume() causes a write
past the end of the array. This is easily reproducable with

    ethtool -G ens3 rx 32
    ./xdpsock -i eth0 -q 0 -r -z &
    ethtool -G eth0 rx 256

## Which versions are affected by CVE-2026-90142?


## How do I fix CVE-2026-90142?

Apply the vendor's patch.

## Is CVE-2026-90142 being exploited?

There is no known exploitation of CVE-2026-90142 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-90142 and fix it if it is affected.

What it is: CVE-2026-90142 is a high-severity memory corruption vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-90142 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-90142/ (Markdown: https://insights.sbomify.com/CVE-2026-90142/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-90142
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-90142
- OSV: https://osv.dev/vulnerability/CVE-2026-90142

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-90142/
Summaries are generated and may contain mistakes; the official description above is the record.