# CVE-2026-98526: llc: reserve device headroom for allocated frames

> A Linux kernel LLC frame allocation flaw allows attackers to cause headroom underflow, potentially leading to memory corruption or denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-108584, BELL-CVE-2026-98526, DEBIAN-CVE-2026-98526, GHSA-cxpq-4fh3-6276, UBUNTU-CVE-2026-98526

## What is CVE-2026-98526?

CVE-2026-98526 is a memory corruption vulnerability in Linux, published on 18 Oct 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:

llc: reserve device headroom for allocated frames

llc_alloc_frame() reserves link-layer headroom using the device type.
This is insufficient for stacked Ethernet devices such as VLAN devices,
where vlan_dev_hard_header() pushes a VLAN header before the lower
device's Ethernet header. An LLC response on such a device can
therefore underflow skb headroom in eth_header().

Use LL_RESERVED_SPACE() to account for the device's actual required
headroom while preserving the existing LLC device-type check.

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


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

Apply the vendor's patch.

## Is CVE-2026-98526 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98526 is a memory corruption vulnerability in Linux, published on 18 Oct 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-98526 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-98526/ (Markdown: https://insights.sbomify.com/CVE-2026-98526/index.md)
```

## Sources

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

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