CVE-2026-98576: Linux kernel · nfc: llcp: fix slab-out-of-bounds reads when logging service names
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in a143f7835faa4fe0178448289feea4f84eeee8d6 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 14:05 UTC
Rated Low by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in a143f7835faa4fe0178448289feea4f84eeee8d6, 8978dff632519712d1fa432991e1f2e857f90239, 4262b12277a3e056c95fc49e9c4d7bd97035d16c +5
Exploitation evidence
Disclosed: evidence found.
CVE published 18 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix is available and has been applied in multiple Linux kernel commits. Users and administrators should update to a Linux kernel version that includes the fix (commits a143f7835faa4fe0178448289feea4f84eeee8d6 and others). No additional mitigation is required beyond applying the official patch.
Description
A vulnerability in the Linux kernel NFC subsystem (llcp) caused slab-out-of-bounds reads when logging service names. The issue arises because non-null-terminated strings are passed to debug logging functions using the %s format specifier, leading to reads beyond allocated memory buffers. This was fixed by limiting the output length explicitly in the logging calls.
References
- git.kernel.org/stable/c/75f7c5a42fa1483f5912279a749417c284ad708f (opens in a new tab)
- git.kernel.org/stable/c/6d4ca872830e46fcca9c086bf19fa9bd2faf09d2 (opens in a new tab)
- git.kernel.org/stable/c/a143f7835faa4fe0178448289feea4f84eeee8d6 (opens in a new tab)
- git.kernel.org/stable/c/75bfd9ef4da2fb49dac1f19880d2ac4ccd07b45b (opens in a new tab)
- git.kernel.org/stable/c/8afb6c194f5781798d3ab3edf243cf5a24a9d1f9 (opens in a new tab)
- git.kernel.org/stable/c/8978dff632519712d1fa432991e1f2e857f90239 (opens in a new tab)
- git.kernel.org/stable/c/4262b12277a3e056c95fc49e9c4d7bd97035d16c (opens in a new tab)
- git.kernel.org/stable/c/7dcf371a35632f035baf77bcf2c129165f772ce4 (opens in a new tab)