# CVE-2026-98576: nfc: llcp: fix slab-out-of-bounds reads when logging service names

> A local attacker can trigger slab-out-of-bounds reads in the Linux kernel NFC LLCP subsystem, potentially leaking memory or causing a crash.

- **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-109277, BELL-CVE-2026-98576, DEBIAN-CVE-2026-98576, GHSA-4wv6-7jcw-864j, UBUNTU-CVE-2026-98576

## What is CVE-2026-98576?

CVE-2026-98576 is a 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 slab-out-of-bounds reads when logging service names

nfc_llcp_wks_sap() and nfc_llcp_build_sdreq_tlv() pass non-null-
terminated strings to pr_debug() using the %s format specifier.
The buffers are allocated via kmemdup() or come from netlink
attributes and are not guaranteed to be null-terminated, causing
__dynamic_pr_debug() to read beyond the allocated region:

  KASAN: slab-out-of-bounds Read in __dynamic_pr_debug

Fix both call sites by using %.*s with the explicit length to limit
the output to the actual length of the string.

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


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

Apply the vendor's patch.

## Is CVE-2026-98576 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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