nfc: llcp: fix slab-out-of-bounds reads when logging service names
Summary
| CVE | CVE-2026-98576 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-10-18 16:17:09 UTC |
| Updated | 2026-10-19 10:19:16 UTC |
| 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. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected d9b8d8e19b073096d3609bbd60f82148d128b555 75f7c5a42fa1483f5912279a749417c284ad708f git |
Not specified |
| CNA |
Linux |
Linux |
affected d9b8d8e19b073096d3609bbd60f82148d128b555 6d4ca872830e46fcca9c086bf19fa9bd2faf09d2 git |
Not specified |
| CNA |
Linux |
Linux |
affected d9b8d8e19b073096d3609bbd60f82148d128b555 a143f7835faa4fe0178448289feea4f84eeee8d6 git |
Not specified |
| CNA |
Linux |
Linux |
affected d9b8d8e19b073096d3609bbd60f82148d128b555 75bfd9ef4da2fb49dac1f19880d2ac4ccd07b45b git |
Not specified |
| CNA |
Linux |
Linux |
affected d9b8d8e19b073096d3609bbd60f82148d128b555 8afb6c194f5781798d3ab3edf243cf5a24a9d1f9 git |
Not specified |
| CNA |
Linux |
Linux |
affected d9b8d8e19b073096d3609bbd60f82148d128b555 8978dff632519712d1fa432991e1f2e857f90239 git |
Not specified |
| CNA |
Linux |
Linux |
affected d9b8d8e19b073096d3609bbd60f82148d128b555 4262b12277a3e056c95fc49e9c4d7bd97035d16c git |
Not specified |
| CNA |
Linux |
Linux |
affected d9b8d8e19b073096d3609bbd60f82148d128b555 7dcf371a35632f035baf77bcf2c129165f772ce4 git |
Not specified |
| CNA |
Linux |
Linux |
affected 3.10 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 3.10 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.10.271 5.10.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.15.222 5.15.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.1.189 6.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.158 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.112 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.55 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2.9 7.2.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.3 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/6d4ca872830e46fcca9c086bf19fa9bd2faf09d2 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/a143f7835faa4fe0178448289feea4f84eeee8d6 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/7dcf371a35632f035baf77bcf2c129165f772ce4 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/75bfd9ef4da2fb49dac1f19880d2ac4ccd07b45b |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/75f7c5a42fa1483f5912279a749417c284ad708f |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/4262b12277a3e056c95fc49e9c4d7bd97035d16c |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/8afb6c194f5781798d3ab3edf243cf5a24a9d1f9 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/8978dff632519712d1fa432991e1f2e857f90239 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.