# CVE-2026-98579: nfc: llcp: fix sdreq TLV list leak on parse/alloc/send failure

> A memory leak in the Linux kernel NFC LLCP module allows local attackers to cause denial of service by triggering error paths in SDREQ processing.

- **Severity:** Not scored
- **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:** 18 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-109281, BELL-CVE-2026-98579, DEBIAN-CVE-2026-98579, GHSA-g53r-f4w7-7x66, UBUNTU-CVE-2026-98579

## What is CVE-2026-98579?

CVE-2026-98579 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:

nfc: llcp: fix sdreq TLV list leak on parse/alloc/send failure

nfc_genl_llc_sdreq() builds a list of TLV nodes while walking nested
netlink attrs, but 3 error paths (nested-attr parse failure, TLV alloc
ENOMEM, nfc_llcp_send_snl_sdreq() failure) all skip freeing what was
already queued.

Route them through a new free_list label, mirroring the SDRES path in
the same file which already does this. Harmless on the success path
too -- send_snl_sdreq() drains the list as it moves nodes, so it's
already empty by the time free_list runs.

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


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

Apply the vendor's patch.

## Is CVE-2026-98579 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98579 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-98579 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-98579/ (Markdown: https://insights.sbomify.com/CVE-2026-98579/index.md)
```

## Sources

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

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